Binance Error Messages¶
Common errors found in logs when running Hummingbot on Binance connector.
Hummingbot should run normally regardless of these errors. If the bot fails to perform or behave as expected (e.g. placing and cancelling orders, performing trades, stuck orders, orders not showing in exchange, etc.) you can get help through our support channels.
These are known issues from the Binance API and Hummingbot will attempt to reconnect afterwards.
1 2 3 4 5 6 7 8 9 10
hummingbot.market.binance.binance_market - NETWORK - Unexpected error while fetching account updates. AttributeError: 'ConnectionError' object has no attribute 'code' AttributeError: 'TimeoutError' object has no attribute 'code' hummingbot.core.utils.async_call_scheduler - WARNING - API call error: ('Connection aborted.', OSError("(104, 'ECONNRESET')",)) hummingbot.market.binance.binance_market - NETWORK - Error fetching trades update for the order [BASE][QUOTE]: ('Connection aborted.', OSError("(104, 'ECONNRESET')",)).
Timestap errors in logs happen when the Binance clock gets de-synced from time to time as they can drift apart for a number of reasons. Hummingbot should safely recover from this and continue running normally.
binance.exceptions.BinanceAPIException: APIError(code=-1021): Timestamp for this request is outside of the recvWindow.