Are you getting an error like the following one when running Gunbot?
the following exception
{ RequestTimeout: binance GET https://api.binance.com/api/v3/ticker/24hr request timed out (10000 ms)
at module.exports.initRestRateLimiter.executeRestRequest.timeout.catch (/snapshot/test/Desktop/dsg/node_modules/ ccxt.pro/node_modules/ccxt/js/base/Exchange.js:397:27)
at <anonymous>
constructor: [Function: RequestTimeout],
name: ‘RequestTimeout’ } ‘Unhandled Rejection at Promise’ Promise {
<rejected> { RequestTimeout: binance GET https://api.binance.com/api/v3/ticker/24hr request timed out (10000 ms)
at module.exports.initRestRateLimiter.executeRestRequest.timeout.catch (/snapshot/test/Desktop/dsg/node_modules/ ccxt.pro/node_modules/ccxt/js/base/Exchange.js:397:27)
at <anonymous>
constructor: [Function: RequestTimeout],
name: ‘RequestTimeout’ } }
This error happens when a connection between your computer and the exchange times out. If it happens one time and it doesn’t appear again, there is nothing to worry about. In the case we notice this error happens often, then we have to take measures.
– The first thing we should try is to stop the bot, wait for some minutes and start it again setting a higher delay, so we don’t flood the exchange with so many requests.
– If we still keep getting this error, in the case we are running autoconfig, and you have jobs that use tickers, run them less often.
– Maybe the problem is being caused by our computer. If you are running programs that make a lot of connections or use bandwidth, try closing them.
– Do you keep your Gunbot GUI opened even when you are not checking it? Note that Gunbot GUI is highly resource demanding and the longer it stays opened, the more resources it demands. If you don’t close it, eventually it will end slowing down your computer. It can even reach to a point that it can make your system to be frozen for several seconds, making some connections to timeout.
– Try to sync the time of your computer.
– If everything else fails, change your Api key for a new one.