Common Errors

Comments Off on How to fix Error connect ECONNREFUSED 138.197.69.201:5000

How to fix Error connect ECONNREFUSED 138.197.69.201:5000

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…) […]

Comments Off on Fix TypeError: Cannot read property ‘time’ of undefined on Gunbot

Fix TypeError: Cannot read property ‘time’ of undefined on Gunbot

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.  

Comments Off on Fix StatusCodeError: 403 – “Forbidden” on Gunbot

Fix StatusCodeError: 403 – “Forbidden” on Gunbot

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

Comments Off on How to fix Cannot read property toLowerCase of undefined

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.

1

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\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) […]

Comments Off on Fix TypeError: Cannot read property ‘type’ of undefined

Fix TypeError: Cannot read property ‘type’ of undefined

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, […]

2

Fix error “Issue checking Gunthy Balance on Etherscan network”

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.

Comments Off on How to fix “EAPI:Invalid nonce” error on Gunbot

How to fix “EAPI:Invalid nonce” error on Gunbot

Are you getting an error message when running Gunbot similar to this?: Loading exchange – kraken Loading data…. { InvalidNonce: kraken {“error”:[“EAPI:Invalid nonce“]} at kraken.handleErrors (C:\snapshot\v18build\node_modules\ccxt.pro\node_modules\ccxt\js\kraken.js:1405:19) at module.exports.handleRestResponse.response.text.then (C:\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: InvalidNonce], name: ‘InvalidNonce’ } Error: Fetching my trades again.{“name”:”InvalidNonce”} at errorHandler (C:\snapshot\v18build\ctx\js\kraken.js:0:0) at <anonymous> at process._tickCallback (internal/process/next_tick.js:188:7) Error: {} at errorHandler (C:\snapshot\v18build\ctx-wrapper.js:0:0) at <anonymous> at process._tickCallback (internal/process/next_tick.js:188:7) Unable to connect to kraken If you […]

Contact us