cryptoeax / arbbot

Arbitrator, a bitcoin/altcoin arbitrage trading bot
https://gitter.im/cryptoeax-arbbot/Lobby
GNU General Public License v3.0
198 stars 78 forks source link

"Timestamp for this request is outside of the recvWindow" #150

Closed ericfraselle closed 6 years ago

ericfraselle commented 6 years ago

I received this error several time, even after restart and/or update time with ntp.

OlegVic commented 6 years ago

have same error on BINANCE

jjc6676 commented 6 years ago

same

ericfraselle commented 6 years ago

There is the same kind of bug on ccxt. I found a lot of reference with this error, ccxt and binance. But I didn't find the solution.

OlegVic commented 6 years ago

have 2 variants then create object ( $this->exchange = new $ccxtName( array( 'enableRateLimit' => true, ) ); ): need add options:

  1. 'recvWindow' => 5 * 1000, // 5 sec, binance default - better
  2. 'adjustForTimeDifference' => false, // controls the adjustment logic upon instantiation - not safe

i made changes in CCXT file binance.php 'recvWindow' => 15 * 1000, // 5 sec, binance default Set 15 seconds! and now works for me!

jjc6676 commented 6 years ago

Are you guys getting this one Deposit Address: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, Memo: [BITTREX] API error response: PAYMENTID_NOT_SUPPORTED

The xx's are my deposit address replaced

cryptoeax commented 6 years ago

Are you guys getting this one Deposit Address: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, Memo: [BITTREX] API error response: PAYMENTID_NOT_SUPPORTED

The xx's are my deposit address replaced

That one was fixed by e53c15c154cd80b8d30096f4cfac51fe04d9792a, it was a recent regression.

About the other errors, I would appreciate if someone can provide some more detailed log. A one line error message is hardly helpful. For example, I am not sure which API call is throwing this error at the moment. :-)

cryptoeax commented 6 years ago

https://github.com/ccxt/ccxt/issues/936 explains the causes of this error. This can be caused by time drifts between the machine arbbot is running on and the Binance servers. In order to improve the situation it is recommended: