Skip to main content

Frequently Asked Questions

Here you can find answers to common questions and issues you may encounter.

Invalid License for XYZ​

Case​

Loading config..
  (Telegram) Starting bot as Gunbot
  GUI Server Deployed: http://localhost:5000
  
  Your Gunthy token balance is: 24000 in wallet: ******
  Your license type is: V12 - ULTIMATE
  Tradingview Plugin Access: true
  Market Maker Plugin Access: false
  
  Your user rank: 10
  
  You can have up to 9999 exchanges to run simultaneously
  
  Your registered exchanges:
  KUCOIN: ******
  BINANCE: ******
  
  INVALID LICENSE FOR BINANCE!!! Please contact Support!

Solution​

This error usually appears if you have configured a key in Gunbot which differs from the key linked to your license. In the above case, Gunbot is loading 'Binance' and then throws the error.

Verify that your key configured in Gunbot is exactly the one linked to your license

This can be verified on this page (http://localhost:5000/setup) in your Gunbot GUI:

If the key linked to your license differs from the key you have configured in your Gunbot you can change the key yourself by following the Edit License procedure, or in case you have only one key configured, by contacting us mentioning your Gunthy Wallet address and your new API Key. We will change the key for you then.

Invalid signature​

Case​

AuthenticationError: bittrex {"code" : "INVALID_SIGNATURE"}
  at bittrex.throwExactlyMatchedException(/snapshot/enricoranucci/Documents/GitHub/Mio/node_modules
/ccxt.prows/node_modules/ccxt/js/base/Exchange.js:532:19)
  at bittrex.hand leErrors (/snapshot/enricoranucci/Documents/GitHub/Mio/node_modules/ccxt.proWs/node_modules/
ccxt/js/bittrex.js: 1311:26)
  at /snapshot/enricoranucci/Documents/GitHub/Mio/node_modules/cct.proWs/node_modules/cc×t/js/base/Exchange.js
:600:18 at processTicksAndRejections (internal/process/task_queues. js: 97:5)
  at async timeout (/snapshot/enricoranucci/Documents/GitHub/Mio/node_modules/ccxt.prows/node_modules/ccxt/js
/base/functions/time. js)
  at async bittrex. fetchMyTrades (/snapshot/enricoranucci/Documents/GitHub/Mio/node_modules/ccxt.proWs/
node_modules/cct/js/bittrex.js: 1165:26) {
  constructor: Function: AuthenticationError]
  }

Solution​

Your API Secret is wrong. Please verify that you've entered your Secret Key correctly here (http://localhost:5000/setup):

If you don't know the Secret Key anymore for the exchange you've configured, you can change you'll have to create a new API Key on the exchange and switch the key tied to your Gunbot by following the Edit License procedure, or in case you have only one key configured, by contacting us mentioning your Gunthy Wallet address and your new API Key. We will change the key for you then.

Timestamp for this request is outside of the recvWindow​

Case​

binanceus {"code":-1021,"msg":"Timestamp for this request is outside of the recvWindow."}
  at binanceus.throwExactlyMatchedException (C:snapshotgbparis
ode_modulesccxtjsaseExchange.js:515:19)
  at binanceus.handleErrors (C:snapshotgbparis
ode_modulesccxtjsinance.js:1706:26)
  at module.exports.handleRestResponse.response.text.then (C:snapshotgbparis
ode_modulesccxtjsaseExchange.js:610:18)
  at <anonymous>
  at process._tickCallback (internal/process/next_tick.js:188:7) constructor: [Function: InvalidNonce], 
name: 'InvalidNonce' }
Fetching my trades again.{"name":"InvalidNonce"}
Error: Fetching my trades again.{"name":"InvalidNonce"}
  at errorHandler (C:snapshotgbparisctxjsexchanges.js:0:0)
  at <anonymous>
  at process._tickCallback (internal/process/next_tick.js:188:7)
Error: {}
  at errorHandler (C:snapshotgbparisctx-wrapper.js:0:0)
  at <anonymous>
  at process._tickCallback (internal/process/next_tick.js:188:7)
Unable to connect to binanceus
Please if this error persists, stop Gunbot, wait a few minutes and then start it again...

Solution​

This error means that your time is out of sync with the API servers from the exchange you're using.

You can solve this issue by downloading a tool to keep your time synced from here.

On Windows you can also do the following:

  1. Press the Windows Button + R
  2. Type in the searchbar services.msc
  3. Search for "Windows Time"
  4. Check if the service is running, if not start it and restart your Computer
  5. If the service is already running and you're still encountering the same issue, restart the service

EADDRINUSE​

Case​

Loading config...
  uncaughtException Error: bind EADDRINUSE null:5000
      at listenOnMasterHandle (net.js:1380:18)
      at rr (internal/cluster/child.js:132:12)
      at Worker.<anonymous> (internal/cluster/child.js:99:7)
      at process.onInternalMessage (internal/cluster/utils.js:47:8)
      at process.emit (events.js:327:22)
      at emit (internal/child_process.js:906:12)
      at processTicksAndRejections (internal/process/task_queues.js:85:21) {
    errno: -48,
    code: 'EADDRINUSE',
    syscall: 'bind',
    address: null,
    port: 5000
  }

Solution​

This error means that the port Gunbot is attemting to bind the GUI to, is already in use by a service on your computer.

Navigate into your Gunbot folder and look for a file called 'config.js'

Right click on it and open it with any Text Editor you have installed.

Once opened, search for:

"port": 5000,

Then change it to:

"port": 5001,

Then save the file.

Then simply start Gunbot again and the GUI should now be reachable on the new port http://localhost:5001

EVP DecryptFinal​

Case​

This error means that your Secret key has been double encrypted and cannot be decrypted correctly anymore.

Error error: 0606506D :digital envelope routines:EVP_DecryptFinal_ex:wrong final block length at Decipher.final 
(internal/crypto/cipher.js: 174:29
	at Object.decrypt (C:snapshotenricoranucciDesktopMiohelper.js)
	at new ctxwrapper (C:snapshotenricoranucciDesktopMioctx-wrapper.js)
	at C:snapshotenricoranucciDesktopMioot • gunbot.js 
	at C:snapshotenricoranucciDesktopMioctx-wrapper.js 
	at processticksAndRejections (internal/process/task_queues.js :97:5)
library: "digital envelope routines", 
function: "EVP DecryptFinal ex",
reason: "wrong final block length",
code: "ERR_OSSL_EVP_WRONG_FINAL_BLOCK_LENGTH"
}

Solution​

  1. Open the folder where you've installed Gunbot and locate a file called config.js

  1. Open the file with a text editor (Ideally a code editor like Notepad++, Atom, VScode, etc)
  2. Search for:
"start": true,
  1. Change it to:
"start": false,
  1. Then save the file and access the GUI again

Then once inside of the GUI, Click on your Profile

And then re-enter your API Secret key

Then apply the changes and press Start Trading.

Cannot convert undefined or null to object​

Case​

Loading config...
  GUI Server Deployed: http://localhost:5000
  TypeError: Cannot convert undefined or null to object
      at Function.keys (<anonymous>)
      at isEqualTwoData (/snapshot/enricoranucci/Desktop/STABLE/gui/classes/common.js)
      at isEqualTwoData (/snapshot/enricoranucci/Desktop/STABLE/gui/classes/common.js)
      at isEqualTwoData (/snapshot/enricoranucci/Desktop/STABLE/gui/classes/common.js)
      at isEqualTwoData (/snapshot/enricoranucci/Desktop/STABLE/gui/classes/common.js)
      at isEqualTwoData (/snapshot/enricoranucci/Desktop/STABLE/gui/classes/common.js)
      at isEqualTwoData (/snapshot/enricoranucci/Desktop/STABLE/gui/classes/common.js)
      at Timeout._onTimeout (/snapshot/enricoranucci/Desktop/STABLE/gui/sockets/coremem.js)
      at listOnTimeout (internal/timers.js:549:17)
      at processTimers (internal/timers.js:492:7) Uncaught Exception thrown

Solution​

Open your config.js file with an editor.

Search for anything null and replace it with an appropriate value (numerical, alphabetical, true/false, depending on the case)

Then save the file and start Gunbot again.

Warning: Buy order from more than 30 days ago​

Case​

GB_25.0.8 USDT-BTC binance Round #23 2023/02/15 16:32:18

  WARNING: BUY order from more than 30 days ago, for USDT-BTC. 
 This might be a temporary issue, wait next cycle and if this error persists, please override
 BOUGHT_PRICE or raise your MVTS

Solution​

This 'issue' is not actually an issue, but more of a safety mechanism in Gunbot.

The problem here is that Gunbot detects that there's BTC in Quote (in this case BTC, as the pair is USDT-BTC) for which Gunbot cannot determine an entry price (bought price) as the trading history for from which price BTC come from is missing. The exchanges usually do not provide any trading history older than 30 days through their API and thus Gunbot cannot see any trades which happened before those 30 days.

The above issue can also be caused if you have USDT-BTC configured and you would deposit BTC straight into the exchange. Technically those BTC do not have a bought price in this case.

There are many ways to resolve this issue:

  • First, make sure if you didn't intend to trade Quote as Base. For example you've just deposited BTC and want to accumulate BTC. In this case, switch your pair from USDT-BTC to BTC- pairs.
  • You've just started trading with Gunbot and before Gunbot you manually traded USDT-BTC. In this case, login to the exchange and calculate the average entry price yourself from the trades you did in the past. Note this value down and enter it as BOUGHT_PRICE in Gunbot. Gunbot will pick up from there on and sell your Quote to Base profitabily.
  • You do not want to accumulate the Quote you have. In this case you can manually sell on the exchange the entire Quote back to Base (in this case this would be sell BTC to USDT). You would start Gunbot with only USDT and no BTC in this case.
  • The amount in Quote you're having is very, very small, sometimes also referred to as 'dust'. In this case slightly raise your MIN_VOLUME_TO_SELL value and Gunbot will 'ignore' the dust and sell it during the next sell cycle.

Where to set the BOUGHT_PRICE?​

Open the overview sidebar on the chart page in the GUI, by clicking on the arrow at the bottom.

Then expand the 'Pair settings tab'

In the parameter field, enter 'Bought price' and click the result

Then enter the value, which should represent the average bought price you've bought these coins from, or a value you would be comfortable selling at, then apply.

Then press Save Changes at the top of the GUI.

Reset the GUI Password/2FA​

Case​

You cannot access the GUI anymore and/or want to reset your access password/2FA.

Solution​

  1. Stop Gunbot entirely
  2. Open the folder where you've installed Gunbot and locate a file called gunbotgui.db

  1. Delete the file
  2. Restart Gunbot
  3. Open the GUI in your Browser and you can set a new password then

Can't access the GUI anymore​

Case​

You cannot access the GUI anymore due to a critical error in Gunbot core.

Solution​

  1. Open the folder where you've installed Gunbot and locate a file called config.js

  1. Open the file with a text editor (Ideally a code editor like Notepad++, Atom, VScode, etc)
  2. Search for:
"start": true,
  1. Change it to:
"start": false,
  1. Then save the file and access the GUI again