Gunbot blog

Are you getting an error looking like this when running Gunbot? 2020/06/19 09:02:48: Kicking bittrex, receiving new tickers… { ExchangeError: bittrex {“success”:false,”message”:”TICK_INTERVAL_NOT_PROVIDED“,”result”:null,”explanation”:null} at bittrex.handleErrors (/snapshot/v18build/node_modules/ccxt.pro/node_modules/ccxt/js/bittrex.js:1431:23) at module.exports.handleRestResponse.response.text.then (/snapshot/v18build/node_modules/ccxt.pro/node_modules/ccxt/js/base/Exchange.js:618:18) at <anonymous> at process._tickCallback (internal/process/next_tick.js:188:7) constructor: [Function: ExchangeError], name: ‘ExchangeError’ } Error: Fetching OHLCV again.{“name”:”ExchangeError”} at errorHandler (/snapshot/v18build/ctx/js/bittrex.js:0:0) at <anonymous> at process._tickCallback (internal/process/next_tick.js:188:7) Error: {} at errorHandler (/snapshot/v18build/ctx-wrapper.js:0:0) at <anonymous> at process._tickCallback (internal/process/next_tick.js:188:7) (Code 15902)Requesting data…please wait… Today is your lucky day, […]

How to fix the error message: ‘Error: connect ECONNREFUSED 138.197.69.201:5000‘, The full error message looks something like this: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1195:14) errno: ‘ECONNREFUSED’, code: ‘ECONNREFUSED’, syscall: ‘connect’, address: ‘138.197.69.201’, port: 5000 }, error: { Error: connect ECONNREFUSED 138.197.69.201:5000 This error can be caused by 2 things: 1- Something is blocking your connection. Make sure your Internet connection is up and there isn’t anything blocking your connection (firewall etc…) […]

Are you getting “TypeError: Cannot read property ‘time’ of undefined” error when running Gunbot? Ok, don’t panic, there is an easy way to fix it. Stop Gunbot. Now go to Gunbot directory and remove all .Json files. Start the bot again. Fixed.  

Are you getting ‘StatusCodeError: 403 – “Forbidden”‘ error when running Gunbot? This error looks like this: Loading config…    info  – socket.io started GUI Server Deployed: http://localhost:5000 { StatusCodeError: 403 – “Forbidden”     at new StatusCodeError (/snapshot/v18build/node_modules/request-promise-core/lib/errors.js:32:15)     at Request.module.exports.plumbing.callback (/snapshot/v18build/node_modules/request-promise-core/lib/plumbing.js:104:33)     at Request.RP$callback [as _callback] (/snapshot/v18build/node_modules/request-promise-core/lib/plumbing.js:46:31)     at Request.init.self.callback (/snapshot/v18build/node_modules/request/request.js:185:22)     at Request.emit (events.js:159:13)     at Request.<anonymous> (/snapshot/v18build/node_modules/request/request.js:1161:10)     at Request.emit (events.js:159:13)   […]

Are you getting the error message “Cannot read property toLowerCase of undefined” when running Gunbot? This error appears when we got a temporary / soft ban for making too many requests per second. In order to fix it, close the bot for 5 or 10 minutes, increase the delay, and run the bot again.

There are several similar errors related with the same issue: some computers lose the time sync after some days. One of the most common errors is: Error: binance {“code”:-1021,”msg”:”Timestamp for this request was 1000ms ahead of the server’s time.“} This is a similar error caused by the same issue: { InvalidNonce: binance {“code”:-1021,”msg”:”Timestamp for this request is outside of the recvWindow.“} at binance.throwExactlyMatchedException (C:\snapshot\v18build\node_modules\ccxt.pro\node_modules\ccxt\js\base\Exchange.js:523:19) at binance.handleErrors (C:\snapshot\v18build\node_modules\ccxt.pro\node_modules\ccxt\js\binance.js:1906:26) at module.exports.handleRestResponse.response.text.then (C:\snapshot\v18build\node_modules\ccxt.pro\node_modules\ccxt\js\base\Exchange.js:618:18) […]