Gunthy

GUNBOT: The automatic profit generator => Technical Support & Development => Topic started by: Puddleduck on February 06, 2018, 04:31:10 PM

Title: Unable to check masterkey
Post by: Puddleduck on February 06, 2018, 04:31:10 PM: Hi guys,

I purchased gunbot a few days ago and made a new installation yesterday. I followed the instructions to the letter. Gunbot worked fine for an hour or two until suddenly I got "unable to check masterkey" error.

I believe there is a flaw in the API key management because when I delete the API key and try to reset it I receive an error message: cannot read property status of undefined.

It is all very confusing.

I tried version 7.0.2 and here too I get a fetchmytrade error in combination with error 400.

Does anybody have a clue what is going on?

Cheers

(A very frustrated) Puddleduck
Title: Re: Unable to check masterkey
Post by: tblim on February 06, 2018, 05:17:05 PM: Unfortunately this is an existing problem which is indeed frustrating.

See here
https://gunthy.org/forum/index.php/topic,2814.0.html

and here:
https://github.com/GuntharDeNiro/BTCT/issues/470

The developers haven't yet acknowledged the problem, so we will have to wait.
Title: Re: Unable to check masterkey
Post by: Puddleduck on February 06, 2018, 08:37:07 PM: Thanks for the info!

This is truly frustrating because I expect the market to go back up soon. An ideal time for trading...

Best regards,

PD
Title: Re: Unable to check masterkey
Post by: sloaleks on February 09, 2018, 02:58:10 PM: see if it helps to set your API as your master and secondary (use the same API).
Title: Re: Unable to check masterkey
Post by: chad.mercer on February 09, 2018, 04:25:40 PM: I'm having the same problem with Binance. I thought it wasn't working just because Binance was down, but Binance is up and I'm getting that 'issue with product details' and 'master key' errors.

My Poloniex bot is working fine (completely different account).

Very frustrated.
Title: Re: Unable to check masterkey
Post by: ggromak on February 09, 2018, 04:35:32 PM: Same problem with Binace
Title: Re: Unable to check masterkey
Post by: SirBonus on February 09, 2018, 05:58:28 PM: Yeah... Bot is broken on Binance after they released some "tweaks" with 26hours shutdown...
Title: Re: Unable to check masterkey
Post by: Blianga on February 09, 2018, 08:11:58 PM: I am also getting this from Binance after the update and unable to trade/connect. www.binance.com is still down for me as well, although the app works. Anyone know if this is an issue on Binance's side, or did they change something that broke gunbot? Waiting for binance.com to come back up to log into check my API key, etc to see if it is still configured correctly.
Title: Re: Unable to check masterkey
Post by: tblim on February 16, 2018, 01:45:15 PM: Is there any update on this bug?

This still happens every time I run gunbot.
Title: Re: Unable to check masterkey
Post by: mrmyrtle on February 17, 2018, 11:04:56 PM: Same problem:
I've just updated from 7.0.2 to 8.0.3 and I've re-added my API keys for Bittrex, Poloniex and Binance.
Binance is causes an error saying it can't read the "masterkey", it did work fine on 7.0.2.
I've double checked and it is the same values... any ideas on the fix... would resubmitting the License key to Gunther be an option?
Title: Re: Unable to check masterkey
Post by: sloaleks on February 18, 2018, 07:18:57 PM: see if it helps to set your API as your master and secondary (use the same API).
Title: Re: Unable to check masterkey
Post by: tblim on February 18, 2018, 09:17:46 PM: Quote from: sloaleks on February 18, 2018, 07:18:57 PM
see if it helps to set your API as your master and secondary (use the same API).
The API key is set as master. The issues still occurs. I am not sure what you mean with "secondary".
Title: Re: Unable to check masterkey
Post by: sloaleks on February 19, 2018, 07:31:25 AM: Ins eries 8xx you have to set two keys. One is the master, then there is the secondary (although in the bot settings referred to just as "key").
Title: Re: Unable to check masterkey
Post by: jimbogbt on February 19, 2018, 08:15:46 PM: I had this error this morning.
Couldnt be arsed trying to fix it so ended up creating a new instance of gunbot.
(I think this could have been done by just deleting the db.sqlite file but just started afresh.)
Thankfully I have only 2 setups which are pretty easy to recreate but it's always handy to save a log of your strategy settings and setups incase you ever need to start from scratch.