Troubleshooting

troubleshooting-gunbot

Troubleshooting

When there is a problem that might need attention, Gunbot usually shows an error notification in the GUI. Some errors are only visible in the console window running Gunbot.

For troubleshooting purposes, recent logs are stored in the /logs folder. After Gunbot is closed, logfiles can be read with a text editor like Notepad++.

This page describes common problems and their possible solutions.

Tips for troubleshooting: always completely close Gunbot before trying to resolve a critical issue. Reboot your computer when you are unsure if you’ve completely closed Gunbot. When resolving an isse that might be related to API rate limiting, stop running Gunbot for at least 10 minutes before trying to solve the problem.

Contents:

  1. Errors when starting Gunbot or Gunbot core
  2. Errors after successfully starting Gunbot

Errors when starting Gunbot or Gunbot core

The following errors are critical and will prevent trading, they indicate Gunbot could not properly start or connect to an exchange.


INVALID LICENSE FOR (exchange) Please contact your reseller!

Reason: master key is not registered

Possible solutions:

  • Double check if your master key and secret are correct and do not start or end with a blank space
  • Verify that you are running the correct edition of Gunbot (Lite or regular)
  • If the problem persists: contact your reseller

Cannot access GUI anymore after an error keeps occuring in the console log

Reason: Config error preventing core to properly load

Solution:

  • Set start false in the GUI section of config.js, with a text editor like Notepad++. Save the file and you should be able to connect to the GUI again.

“Object object”

Reason: various

Possible solutions:

  • Upgrade to the latest available release.
  • Make sure all pairs on the exchange showing the error are correct. Try testing with just a single BTC-LTC pair.
  • Make sure that both MIN_VOLUME_TO_SELL and MIN_VOLUME_TO_BUY are set to at least the minimum allowed trade size at your exchange.
  • When trading fiat pairs like USDT-x, make sure that MIN_VOLUME_TO_SELLMIN_VOLUME_TO_BUYand TRADING_LIMIT are set to round number without decimals.

INVALID RESPONSE FROM LICENSE SERVER

Reason: Usually a network issue

Possible solutions:

  • Try a wired internet connection
  • Restart your router and/or flush your DNS cache

Error: bind EADDRINUSE null:5000

Reason: Other process is already using the specified port number

Possible solutions:

  • Restart your computer
  • When other software requires using any of the ports needed for Gunbot, change the ports Gunbot uses in the config.js file

Unable to connect to (exchange)

Reason: Various

Possible solutions:

  • Double check if your master key and secret are correct and do not start or end with a blank space
  • Check if your system clock is synced with an internet time server. Tool for Windows / Info for Linux
  • Increase the exchange delay
  • Make sure both a valid master key and key are present in your config
  • Make sure your pairs actually exist on the exchange and conform to Gunbot pair syntax
  • Make sure all Gunbot files were correctly unzipped
  • Make sure the IMAP listener is disabled (when not using the TradingView add-on)
  • Try a wired internet connection
  • Restart your router and/or flush your DNS cache

SSL_ERROR_RX_RECORD_TOO_LONG

Reason: https not enabled

Possible solutions:

  • Enable https in the config.js file
  • Visit Gunbot via http, instead of https

Repeated messages about loading exchanges and config

Reason: Problem with one or your pairs

Possible solutions:

  • Check the syntax of your trading pairs. Pair syntax is case sensitive
  • Verify that the trading pairs actually exist on the exchange

toLowerCase of undefined

Reason: API issue

Possible solutions:

  • Verify you downloaded the correct Gunbot edition (Lite or RT)
  • Make sure your API key is activated on CEX
  • Make sure you filled in your CEX ClientID

error: Invalid signature

Reason: API issue

Possible solutions:

  • Make sure your API key is activated on CEX
  • Make sure you filled in your CEX ClientID

Please add the exchange credentials for (exchange) under Exchanges

Reason: API details missing

Possible solutions:

  • Make sure that you have entered all required API details for every connected exchange

Error: Cannot find module ‘…Gunbot-master\gui\node_modules\sqlite3\lib\binding…\node_sqlite3.node’

Reason: Essential files not found

Possible solutions:

  • Make sure that you have unzipped all files from the Gunbot release package before starting Gunbot

Errors after successfully starting Gunbot

The following orders can prevent trading when occuring very often. When any of these errors only occur intermittently, there is usually no issue that needs solving.


Received broken open orders info: retrying again

Reason: Exchange did not send requested order data

Possible solutions:

  • Ensure proper internet connectivity
  • Increase exchange delay

Received empty balance: retrying again

Reason: Exchange did not send requested balance data

Possible solutions:

  • Ensure proper internet connectivity
  • Increase exchange delay
  • Wait until the exchange finishes maintenance

Fetching OHLC again

Reason: There is not enough trading volume to receive the number of requested candles

Possible solutions:

  • Try a different setting for PERIOD
  • Try other trading pairs with more volume

Received empty order book: retrying again

Reason: Exchange did not send requested order book data

Possible solutions:

  • Ensure proper internet connectivity
  • Increase exchange delay
  • Wait until the exchange finishes maintenance

Portfolio value chart shows strange peaks

Reason: Known issue

Possible solutions:

  • None. Expect better portfolio value calculation in v11.

WARNING: BUY order from more than 30 days ago.

Reason: Bought price for asset is unknown

Possible solutions:

  • Add BOUGHT_PRICE as an override for your pair. Remove after the following sell order.

TypeError: Cannot read property askprice of undefined

Reason: Problem with one or your pairs

Possible solutions:

  • Check if all of the pairs in your setup actually exist on your exchange and conform to Gunbot pair syntax (BASE-QUOTE)
  • Wait until the exchange finishes maintenance

Poloniex: 422

Reason: Exceeding API rate limit

Possible solution:

  • Increase the exchange delay for Poloniex.

Bitfinex: nonce is too small

Reason: Exceeding API rate limit

Possible solution:

  • Increase the exchange delay for Bitfinex.

 

Show Buttons
Hide Buttons