0

Troubleshooting

You are here:
< Back

When you run Gunbot using the official GUI, the logs are saved as out.log in the Gunbot folder, error messages are saved in err.log. Always use these when evaluating your issues.

For all common solutions it is strongly recommended to stop running your bot first!

Contents:

Bot issues

INVALID LICENSE (…) Please contact Gunthar!

Cause Solutions
Master key is wrong or not registered
  • Double check if your API key and secret are correct and do not start or end with a blank space
  • If the problem persists: contact @Narkotix@Exquitas or Gunthar

Unable to check master key

Cause Common solution
Malformed request
  • Check if your system clock is synced with an internet time server, preferably time.nist.gov
    Tool for Windows / Info for Linux
  • Make sure both a valid master key and key are present in your config
  • Make sure your pairs actually exist on Binance

Continuous messages about loading exchanges and configs

Cause Common solution
Problem with one or your pairs
  • Check the syntax of your trading pairs. Pair syntax is case sensitive
  • Verify that the trading pairs actually exist on the exchange
  • Check if your system clock is synced with an internet time server, preferably time.nist.gov
    Tool for Windows / Info for Linux

toLowerCase of undefined

Cause Common solution
API key issue
  • 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

…Safety Switch is on…

Cause Explanation
Bot is not allowed to trade
  • TRADES_TIMEOUT is active due to a recent (re)start of the bot or a recent trade
  • OKKIES_MODE prevents an order because of high pressure on BTC-USD
  • WATCH_MODE is enabled

Continuous heartbeat messages

Cause Common solutions
Can’t retrieve indicator data
  • Make sure you run the latest stable release, including the latest config.js or GUI
  • Check your API key and secret, especially for blank spaces
  • Verify your internet connectivity
  • Change PERIOD to a supported period that’s available on the charts of your exchange
  • Check for abnormalities in your config.js file (when not using the GUI). Even a missing comma can cause errors

Binance: error 1021

Cause Common solution
Time sync issue Check if your systems clock is correct and synced, preferably with time.nist.gov or another proper time server.

Binance: error 400 / 401

Cause Common solutions
Malformed request
  • Check if your systems clock is correct and synced with time.nist.gov or another proper time server.
  • Make sure your pairs actually exist on Binance
  • Try to remove the trading permission for your api key repeatedly at binance, then enable it back again
  • If all else fails: restart your router and/or flush your DNS cache

Binance: error 418 / 429

Cause Solution
API rate limits
  • Stop using the bot for a little while
  • Increase BOT_DELAY

Poloniex: error 422

Cause Solution
API rate limits or nonce
  • Stop using the bot for a little while
  • Increase BOT_DELAY
  • If the problem persists, ask your reseller to register a new API key for Poloniex and use that key on a single device only

TypeError: Cannot read property askprice of undefined

Cause Solution
Problem with one or your pairs Check if all of the pairs in your setup actually exist on your exchange, and that you’ve properly entered them to Gunbot

WARNING: we couldnt get a BOUGHT PRICE

Cause Solution
Bought price unknown Add BOUGHT_PRICE as an override for your pair. Can be done over the GUI on the edit setup page, or manually in config.js when you don’t use the GUI

GUI issues

Please reboot your computer first when troubleshooting any of the problems below.

Console screen flashes repeatedly after starting a setup

Cause Solution
Firewall issue Add rules to your local firewall to accept incoming and outgoing traffic on port 5000

Error: bind EADDRINUSE null:5000

Cause Solution
Port in use Another process blocks port 5000. Force close all running gunthy processes, or reboot your computer

events.js:183 – Error: read ECONNRESET

Cause Explanation
GUI can’t retrieve data from bot The GUI temporarily can’t connect to Gunbot to retrieve pair statistics. This does not affect trading.

“Empty logs” message

Cause Explanation
Logfile can’t be read
  • Delete or rename the out.log file, it might a filesize to large to process.
  • On Mac systems: make sure the GUI process is started correctly from a terminal window, instead of opening it by double clicking the file.

Setups won’t start. No error message is registered

Cause Common solutions
Gunbot can’t be started
  • For Mac: make sure that you’ve started gunthy-gui-macos from a terminal window, and not by double clicking the file
  • Verify that both the gunthy and gunthy-gui executables are allowed to be executed by your current user
  • Remove or rename err.log and out.log
  • Share post