Gunbot Error Codes

[Kuriso]

Error!!! statusCode 422
!!! Cycle  failed. Will repeat in 3000s
If it is repeatedly and blocking the first start of the bot, make a new api key and send it to me. If it is occasionally or mixed with good cycles, it is just errors coming and the bot handling them in the correct way in the following cycles.

=== ERROR ===statusCode 403
The bot is not connecting to the server.  There are a couple potential issues. 

• API keys are wrong or missing.
• After adjusting your config settings, you did not save those settings.
• IP restriction set but you did not actually save your IP to the list

=== ERROR ===statusCode 429
Temporary Ban from Exchange, because of too much API Requests by Bot.

• Reduce the Bot Wait Time and Error Wait Time in config file if you use many coins to trade
• Open less coin-pairs

Please post other errors so I can include them above.

[Gunthar]

Error!!! statusCode 422
!!! Cycle  failed. Will repeat in 3000s
Not sure.  Need Gunthar's  input

If it is repeteadly and blocking the first start of the bot, make a new api key and send it to me. If it is occasionally or mixed with good cycles, it is just errors coming and the bot handling them in the correct way in the following cycles.

In general all those errors are http statuscodes which you can find a complete list here:

https://en.wikipedia.org/wiki/List_of_HTTP_status_codes

[Pro]

=== ERROR ===statusCode 429


Temporary Ban from Exchange, because of too much API Requests by Bot.

- Reduce the Bot Wait Time and Error Wait Time in config File if you use many Coins to trade
- Open Less Coin-Pairs

[Sweeet]

Added to GUNBOT Wiki: https://github.com/TheSweeet/GUNBOT/wiki/Issues-Fixes

[Gunthar]

=== ERROR ===statusCode 429


Temporary Ban from Exchange, because of too much API Requests by Bot.

- Reduce the Bot Wait Time and Error Wait Time in config File if you use many Coins to trade
- Open Less Coin-Pairs

There is not any temp ban anywhere. It is a too many requests warn on client side.
Suggestion to raise bot sleep time is correct. You can also raise the bot on fail time by opening the BTC_XXX-config.js file: it is actualy 3 seconds.

[litbit]

I'm getting a lot of Error Code 429 today

it seems that running even 1 pair is giving issues...
I've the following in the config file:

Code: [Select]

BOT_ON_FAIL_DELAY:(1000)*30,
...
BOT_SLEEP_DELAY: (1000)*120,

"node 1000trades" it does not seem to listen : it is not waiting 120 seconds
(I tried with 60 first, when that didn't work, increased to 120)

Code: [Select]

=== PRICE INFORMATION UPDATE PAIR BTC_LTC at 2017/05/10 00:20:32 ===  last price: 0.01845428
price target to buy: 0.01623060
price target to sell: waiting for buy order to calculate sell price
***GUNBOT is calculating pumps and dumps...please wait
*** POLONIEX CALLBACK | returnCompleteBalances *** Poloniex is busy now, retrying in a few seconds...
***We have enough balance, proceeding with orders...
=== PRICE INFORMATION UPDATE PAIR BTC_LTC at 2017/05/10 00:20:33 ===  last price: 0.01855009
price target to buy: 0.01623060
price target to sell: waiting for buy order to calculate sell price
***GUNBOT is calculating pumps and dumps...please wait
*** POLONIEX CALLBACK | returnCompleteBalances *** Poloniex is busy now, retrying in a few seconds...
***We have enough balance, proceeding with orders...
=== PRICE INFORMATION UPDATE PAIR BTC_LTC at 2017/05/10 00:20:33 ===  last price: 0.01845428
price target to buy: 0.01623060
price target to sell: waiting for buy order to calculate sell price
*** POLONIEX CALLBACK | returnCompleteBalances *** Poloniex is busy now, retrying in a few seconds...
***GUNBOT is calculating pumps and dumps...please wait
***We have enough balance, proceeding with orders...
=== PRICE INFORMATION UPDATE PAIR BTC_LTC at 2017/05/10 00:20:34 ===  last price: 0.01877000
price target to buy: 0.01623060
price target to sell: waiting for buy order to calculate sell price
***GUNBOT is calculating pumps and dumps...please wait
*** POLONIEX CALLBACK | returnCompleteBalances *** Poloniex is busy now, retrying in a few seconds...
***We have enough balance, proceeding with orders...
=== PRICE INFORMATION UPDATE PAIR BTC_LTC at 2017/05/10 00:20:35 ===  last price: 0.01872001
price target to buy: 0.01623060
price target to sell: waiting for buy order to calculate sell price
***GUNBOT is calculating pumps and dumps...please wait
*** POLONIEX CALLBACK | returnCompleteBalances *** Poloniex is busy now, retrying in a few seconds...
***We have enough balance, proceeding with orders...
=== PRICE INFORMATION UPDATE PAIR BTC_LTC at 2017/05/10 00:20:36 ===  last price: 0.01872001
price target to buy: 0.01623060
price target to sell: waiting for buy order to calculate sell price
*** POLONIEX CALLBACK | returnCompleteBalances *** Poloniex is busy now, retrying in a few seconds...
***GUNBOT is calculating pumps and dumps...please wait
***We have enough balance, proceeding with orders...
=== PRICE INFORMATION UPDATE PAIR BTC_LTC at 2017/05/10 00:20:36 ===  last price: 0.01872000
price target to buy: 0.01623060
price target to sell: waiting for buy order to calculate sell price
*** POLONIEX CALLBACK | returnCompleteBalances *** Poloniex is busy now, retrying in a few seconds...
***GUNBOT is calculating pumps and dumps...please wait
***We have enough balance, proceeding with orders...
=== PRICE INFORMATION UPDATE PAIR BTC_LTC at 2017/05/10 00:20:37 ===  last price: 0.01851000
price target to buy: 0.01623060
price target to sell: waiting for buy order to calculate sell price
***GUNBOT is calculating pumps and dumps...please wait
*** POLONIEX CALLBACK | returnCompleteBalances *** Poloniex is busy now, retrying in a few seconds...

[criptonauta]

I'm getting a lot of Error Code 429 today

it seems that running even 1 pair is giving issues...
I've the following in the config file:

Code: [Select]

BOT_ON_FAIL_DELAY:(1000)*30,
...
BOT_SLEEP_DELAY: (1000)*120,

"node 1000trades" it does not seem to listen : it is not waiting 120 seconds
(I tried with 60 first, when that didn't work, increased to 120)

Hi

It's not only you. Polo has been DDOSed and took it's countermeasures, being one of the the limitation of API requests.

Regarding 1000 Trades, it's dynamic is to place different orders up or down, following the trend. Mess with its timing also might mess the whole technique. In cases like today, use a longer delay strategy.

[Clannad]

=== ERROR ===statusCode 429


Temporary Ban from Exchange, because of too much API Requests by Bot.

- Reduce the Bot Wait Time and Error Wait Time in config File if you use many Coins to trade
- Open Less Coin-Pairs

I would rather increase those timings

[ARosie]

Error 422?

Some googling suggests one might need to create a new API?