Gunbot blog


How to know if my Api Key is broken

Sometimes Api keys can stop working and we need to create a new one, but in what situations an Api key can get broken? Mainly there are 4 causes: 1- You did too many request / second and the exchange removed your api key. 2- You disabled 2FA at Bittrex and when you do it, all api keys are removed. 3- You connected to the api key from 2 different […]


Error: Cannot read property charCodeAt of undefined

If you get “Cannot read property charCodeAt of undefined” error when running Gunbot is because you are using an outdated version. Note that some version are being removed and you need to download the latest stable version:


Invalid credentials – Authentificationfailed error on Gunbot

This is one of the most clear errors when running Gunbot. If you are running Gunbot with TradingView Addon, maybe you have seen this message: Loading config… Loading exchange bittrex { Error: Invalid credentials (Failure) at Connection._resTagged (C:\snapshot\Gunbot-master\node_modules\imap\lib\Connection.js:1502:11) at Parser. (C:\snapshot\Gunbot-master\node_modules\imap\lib\Connection.js:194:10) at emitOne (events.js:115:13) at Parser.emit (events.js:210:7) at Parser._resTagged (C:\snapshot\Gunbot-master\node_modules\imap\lib\Parser.js:175:10) at Parser._parse (C:\snapshot\Gunbot-master\node_modules\imap\lib\Parser.js:139:16) at Parser._tryread (C:\snapshot\Gunbot-master\node_modules\imap\lib\Parser.js:82:15) at TLSSocket.__dirname.Parser.debug._cbReadable (C:\snapshot\Gunbot-master\node_modules\imap\lib\Parser.js:53:12) at emitNone (events.js:105:13) at TLSSocket.emit (events.js:207:7) at emitReadable_ (_stream_readable.js:500:10) at emitReadable […]


Empty logs message when running Gunbot

In some cases, when running Gunbot from GUI, logs are not shown and we get this message: “Empty logs”. In order to fix it, stop the bot, remove the files err.log and out.log, located in bot directory, and run the bot again. If it didn’t help, be sure you are following the Mac installation guide. Finally be sure that all the files have writing permissions and you have set writing […]


Fix Error: Can not read property indicators of undefined

If you are running Gunbot on Mac, maybe you have seen this error message: “Can not read property indicators of undefined“. This error can be caused mainly by 2 reasons: 1- There are missing files in your Gunbot directory. Be sure all the files are there, same as “Tulind” directory. 2- Be sure the files are executable (using command “chmod +x”). Just follow the installation steps on Mac: If […]


Run multiple instances of Gunbot and change ports

UPDATED 17-5-2020 With latest Gunbot versions is no longer required to start separate instances in order to run multiple instances, as you can just add different instances from the GUI. In the case you want to run multiple instances for some reason, you have to change ports on both “ws” and “GUI” sections of your config file (each instance would have different ports):   OLD METHOD (RUN MULTIPLE GUNBOT INSTANTES […]


Gunbot doesn’t make trades – How to fix it

One of the most common things we hear from new comers is “My Gunbot is not making trades“. Let’s see how to fix it. 1- First of all: Be Patient. Gunbot is not a drunken teenager with a credit card, it won’t buy anything under any circumstances. Gunbot will execute professional trading strategies and it will only buy or sell when some conditions are meet. Don’t expect trades after 5 […]


Gunbot XT Edition + Gunthy GUI v6.0.2 Final

Core changes BTC pump protection: automatically prevent buy orders from being placed when BTC price and volume are under high pressure. This is configurable per strategy or pair using OKKIES_MODE and BTC_MONEY_FLOW. Order recalculation: Gunbot now automatically cancels unfulfilled orders when the current price moved away. This also affects manually placed orders – when you run the bot on the same pair. Configurable cache cleaner: some users reported cache issues […]

Contact us