Skip to main content

Troubleshooting 'Invalid License' Message

Encountering an "INVALID LICENSE FOR BINANCE" (or any another exchange) message in Gunbot can be a hurdle. Especially occuring after manual config edits in older Gunbot versions. This guide aims to help you resolve this issue, allowing you to continue with your trading activities.

Preparatory Step: disable trading​

Before delving into the resolution paths, it's crucial to set your bot in a safe mode. This mode enables access to the Gunbot interface without connecting to the exchanges, preventing the same error from occurring. Here's how to do it:

  1. Open the config.js file using a text editor like Notepad.
  2. Search for the line "start": true, (in the GUI section, near the bottom of the file)
  3. Change it to "start": false,

This adjustment will put Gunbot in a non-operational state, where it's safe to make necessary changes.

Resolution Path 1: Removing Trading Pairs​

If you want to discontinue trading on the exchange that caused the error, follow these steps:

  1. Navigate to the trading settings page in Gunbot.
  2. Remove every trading pair for the exchange that appeared in the license error message.

This action will prevent Gunbot from attempting to access the problematic exchange.

Resolution Path 2: Registering a New API Key​

When you want to continue trading on the exchange involved in the error, registering the API key is essential. Since Gunbot release v28, the process of managing API credentials has been significantly streamlined. Follow these steps:

  1. Ensure you are using the latest Gunbot release (v28 or later).
  2. Go to the Manage API Slots page in Gunbot.
  3. Register a new API key for the desired exchange. You will also be prompted to enter your API secret to establish a connection to the exchange.

Once completed, Gunbot should be able to interact with the exchange without encountering the license error.

Troubleshooting: When You Can't Resolve​

In some instances, you might find yourself unable to register a new API key, perhaps due to the lack of working keys in your license to authenticate the change. In such cases, it's advisable to reach out to Gunbot support for further assistance.