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/ at module.exports.handleRestResponse.response.text.then (/snapshot/v18build/node_modules/ 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 Error connect ECONNREFUSED

How to fix the error message: ‘Error: connect ECONNREFUSED‘, The full error message looks something like this: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1195:14) errno: ‘ECONNREFUSED’, code: ‘ECONNREFUSED’, syscall: ‘connect’, address: ‘’, port: 5000 }, error: { Error: connect ECONNREFUSED 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…) […]


Fix StatusCodeError: 403 – “Forbidden” on Gunbot

Are you getting ‘StatusCodeError: 403 – “Forbidden”‘ error when running Gunbot? This error looks like this: Loading config…    info  – 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 (/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)   […]


Supported periods for Gunbot v16 and higher

A common mistake is to try to run Gunbot with periods that are not supported by the bot, and this could lead to some errors. The pic below shows all the supported periods for Gunbot v16, v18, v19 and higher. Click on the image to see full size:


How to fix Cannot read property toLowerCase of undefined

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.


How to fix “Timestamp for this request error” on Gunbot

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\\node_modules\ccxt\js\base\Exchange.js:523:19) at binance.handleErrors (C:\snapshot\v18build\node_modules\\node_modules\ccxt\js\binance.js:1906:26) at module.exports.handleRestResponse.response.text.then (C:\snapshot\v18build\node_modules\\node_modules\ccxt\js\base\Exchange.js:618:18) […]


Gunbot permanent tournament May 2020

As you most likely know, Gunbot have been reaching agreements with the most popular crypto exchanges and it’s sharing juicy prices between Gunbot traders. What we plan is to keep going and keep running tournaments in the exchanges we have partnerships with. Next tournament will take place on Binance futures. So, what’s the deal? First of all, the tournament starts at 00:00 UTC 16 of May 2020 and ends at […]

Contact us