-
Notifications
You must be signed in to change notification settings - Fork 3.9k
invalid api key error #870
Comments
Create the file in root. |
The ui feature is in progress and not stable. That branch is on github so other developers can work on the code and everyone can see progress. I would advise against running it and cannot offer any support for it. |
@thegamecat ok, but in windows you need read write permission to create files in root, I looked into it and seems microsoft limited access to root so virus dont get into the OS. |
@askmike ok, I just want to test it to provide feedback of any bugs or improvements that it could use |
@ak9250 I just merged #737 into develop and fixed this bug. Now you can test, and if you run into anything please create an issue :) Note that there might be bugs and I cannot guarantee there won't be issues. |
@askmike thanks I tried the develop branch and I still get the same error, note I am using the public.sandbox.gdax.com site and generate api key secret from there. Could that be the cause of the error? I understand there will be bugs that is why I am using the developers sandbox to test things and make this better, thanks :) |
@ak9250 can you provide a screenshot of copy some logs of the error? I thought you were talking about something else. |
@askmike sorry screenshot attached now to previous post, let me know if you need anything else |
So gekko normally connects to the real GDAX, not the sandbox. So you see this error because sandbox keys don't work on the real GDAX. Two things:
|
@askmike ok thanks I will try this out, gdax really should improve their sandbox site for developers to test out on but until then I might just move to testing on the real site if this doesn't work out. thats another reason I like whaleclub because their demo and live platforms are identical and great for testing. |
error shows when i run gekko through the ui feature trader and on gdax
it says invalid api key and I generating it through the sandbox website
is there a way to fix this?
The text was updated successfully, but these errors were encountered: