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) […]
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:
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) […]
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 […]
Are you getting an error like this one? TypeError: Cannot read property ‘type’ of undefined at module.(anonymous function).a8Q.process.q9Q.(anonymous function).q9Q.(anonymous function).(anonymous function).(anonymous function).(anonymous function).E00 (C:\snapshot\v18build\gain.js:0:0) at module.(anonymous function).Market.returnTradeHistory.Promise.(anonymous function).L0.(anonymous function).(anonymous function).y0 (C:\snapshot\v18build\ctx-wrapper.js:0:0) at <anonymous> at process._tickCallback (internal/process/next_tick.js:188:7) (Code 16189)Requesting data…please wait… If so, try this: Check the pair that is making the error to appear, then make a manual buy and sell it again. A small buy and sell is enough, […]
At the moment of writing this article (21th April 2020), there are 4 Gunbot Editions: – Gunbot Starter: This is an starter version of Gunbot. It’s the cheapest version (0.02 btc) but it’s only able to execute 3 trading strategies: Emotionless, GAIN and BBTA. – Gunbot Standard: It costs 0.05 btc. Gunbot Standard allows to execute all the trading strategies and it has all the features. It includes license for […]
Are you getting a message like “Fix error “Issue checking Gunthy Balance on Etherscan network” when running Gunbot? Most of the times this error is fixed itself, just waiting. If Etherscan network is facing temporary issues, it makes Gunbot unable to read the info it needs, so we just need to wait until Ethercan issues are fixed. It also could be caused if we put an invalid Gunthy wallet.