Gunthy
GUNBOT: The automatic profit generator => Technical Support & Development => Topic started by: ajamant on January 14, 2021, 02:13:46 PM
-
Had gunbot working. Tried changing fee's in gunbot exchange setting and now getting "Invalid Signature" and won't allow me to access Localhost5000. I deleted , reinstalled, gained access to GUI and input my API and key. Same error. Invalid Signature.
Please help.
-
Had gunbot working. Tried changing fee's in gunbot exchange setting and now getting "Invalid Signature" and won't allow me to access Localhost5000. I deleted , reinstalled, gained access to GUI and input my API and key. Same error. Invalid Signature.
Please help.
Hi, check this please:
https://gunbot.shop/how-to-fix-the-error-api-invalid-signature/
-
Yup, I tried editing the file, negative. Thats when I deleted and did a clean install. Had access to GUI, entered all my exchange info and same error.
-
Yup, I tried editing the file, negative. Thats when I deleted and did a clean install. Had access to GUI, entered all my exchange info and same error.
In this case I would try changing your api key for a new one.
-
Ok how about a solution that doesn't cost 0.01 BTC???
Getting very frustrated with this product: LIFETIME license, had to fight for 2 weeks to get you to honor that. Now it works for 1 week, and it won't recognize my API.
No current thread ANYWHERE solves the problem.
I'd like a functioning GUNBOT.
-
OKAY.....3rd time is a charm. Downloaded latest version, clean install, access GUI, input exchange codes, added a pair. No more invalid signature.
Now I get this error code:
(Code 15902)Requesting data...please wait...
[]
Error: "403 - \"error code: 1020\""
at errorHandler (/snapshot/test/Desktop/node14/ctx/js/bittrex.js)
Error: {}
at errorHandler (/snapshot/test/Desktop/node14/ctx-wrapper.js)
-
Problem solved, got a new API key over telegram at no cost. THANK YOU JAVIER!!!!
-
Problem solved, got a new API key over telegram at no cost. THANK YOU JAVIER!!!!
Hi, changing api keys no longer costs 0.01
Glad to hear the issue is fixed now ;)