-
Notifications
You must be signed in to change notification settings - Fork 2k
ggetBalance error (4.04) #193
Comments
Did you retry? Are you able to connect to Poloniex (or any internet site) from the box that is running your bot? |
I wasn't running Zenbot in a docker container, and not sure the API being down is even related. The provided 'nonce' is incorrect |
Having the same issue here. Nonce must be greater than xxx or the time out error bellow. ggetBalance error: It seens like it does not work only some times. I put a console.log in the end of getBalance function and most of the time it passes. Could it be the number of request per second/minute Poloniex accepts? |
Also getting this same error:
If you look at the time stamps, they are off by a few orders of 10 Example: |
Having same issue. Reference: knowm/XChange#1193 getBalance error: Poloniex API is down! unable to call getBalance, retrying in 10s getBalance error: Poloniex API is down! unable to call getBalance, retrying in 10s getBalance error: Poloniex API is down! unable to call getBalance, retrying in 10s getBalance error: Poloniex API is down! unable to call getBalance, retrying in 10s |
AnnihilaT , it didnt help. I have full default settings. Im trying work with polo in the docker zenbot. ---------------------------- STARTING LIVE TRADING ---------------------------- Poloniex API is down! unable to call getBalance, retrying in 10s Poloniex API is down! unable to call getBalance, retrying in 10s Poloniex API is down! unable to call getBalance, retrying in 10s Poloniex API is down! unable to call getBalance, retrying in 10s Poloniex API is down! unable to call getBalance, retrying in 10s Poloniex API is down! unable to call getBalance, retrying in 10s Poloniex API is down! unable to call getBalance, retrying in 10s Poloniex API is down! unable to call getBalance, retrying in 10s Poloniex API is down! unable to call getBalance, retrying in 10s Poloniex API is down! unable to call getBalance, retrying in 10s Poloniex API is down! unable to call getBalance, retrying in 10s Poloniex API is down! unable to call getBalance, retrying in 10s Poloniex API is down! unable to call getBalance, retrying in 10s Poloniex API is down! unable to call getBalance, retrying in 10s Poloniex API is down! unable to call getBalance, retrying in 10s Poloniex API is down! unable to call getBalance, retrying in 10s Poloniex API is down! unable to call getBalance, retrying in 10s Poloniex API is down! unable to call getBalance, retrying in 10s Poloniex API is down! unable to call getBalance, retrying in 10s Poloniex API is down! unable to call getBalance, retrying in 10s Poloniex API is down! unable to call getBalance, retrying in 10s Poloniex API is down! unable to call getBalance, retrying in 10s Poloniex API is down! unable to call getBalance, retrying in 10s Poloniex API is down! unable to call getBalance, retrying in 10s Poloniex API is down! unable to call getBalance, retrying in 10s #bug #help wanted |
try new generated api key. https://github.com/codiwest/zenbot/blob/master/docs/FAQ.md#error-1 |
nao0811ta, thanks! All work fine! |
ggetBalance error: Poloniex API is down! unable to call getBalance, retrying in 10s To combat these errors I have followed steps other users have taken across the web but no success!
None of the above have worked, it's providing the wrong times to Poloniex (and i assume as it's a nonce issue this is not exchange specific). Any new suggestions, did anyone else find something different that worked here? |
@CreativeBacon I think the reason is exchange.js's two poloniex instance. |
Thank you for the speedy reply, super appreciated! I have made the edits as specified and the following error is now presented: TypeError: Cannot set property '_getPrivateHeaders' of undefined |
update, the line wrap on your post made me think line 13 was now to be separated. I'll update with progress, thanks again. :) |
Period is so short and different line of source with mine. |
@CreativeBacon |
My logs tracked well. |
How about retrying modified logic with your new key. |
Still a lot of nonce errors, debugging at present! How does the bot calculate the nonce? |
@CreativeBacon The nonce generation is not done by the bot. It is done in the API functions from exchange API which is pulled in when you do an "npm install" |
@CreativeBacon
|
found getBalance and getTrades are send sometimes at the same time.
|
interesting, I have also added a second set of API keys and will test once they unban me in two minutes! Nice suggestion.. 👍 |
@CreativeBacon |
@nao0811ta This would be easier messaging back and forth on a skype chat, feel free to add me - my Skype ID is freshlondon.biz |
like that
|
again :( `ggetBalance error: Poloniex API is down! unable to call getBalance, retrying in 10s Poloniex API is down! unable to call getBalance, retrying in 10s { Error: unable to sell ggetBalance error: Poloniex API is down! unable to call getBalance, retrying in 10s |
@crack00r docker-compose build, docker-compose up and after all works fine |
i use ubuntu |
@crack00r i see it errors too:( Our patch don't work. |
someone fix it here |
sorry too late
|
no rly bug, only api down Poloniex API is down! unable to call getBalance, retrying in 10s Poloniex API is down! unable to call getBalance, retrying in 10s |
and again |
Api down is not bug. |
My code is not occured since few days before. |
and it didnt cancel the orders so right now, but is useless |
Are you play with the date of you pc? I do a few days ago and make the bot crazy with nonce error! The solution was make a new poloniex key. |
works, i set my server time 2min. above the real time... |
@crack00r Other reasons:
|
I made some test... that is the problem... the program make 2 even 3 calls to poloniex whitout wait for the first to be resolved. |
Fixed by adding --lock and installing NTP on centos and set to sync every minute with --period=1m THE EDIT in exchange.js:
|
You also need to do this instead of running docker, use separate configs for each instance for different coins and API keys. I run 5.
|
Had following problem with kraken: Kraken API warning - unable to call trade (Error: Kraken API returned error: API:Invalid nonce), retrying in 0.15s Increased the nonce window at Kraken API key settings to 360. No problems right now. I think the request takes to long to process and run into this timeout. With Kraken - check status page https://status.kraken.com/ 👎 Update: |
Looks like a Kraken issue, closing this side of the equation. |
While making its 1st purchase on poloniex.BCN-BTC
The text was updated successfully, but these errors were encountered: