Common Questions & Issues
When using nuxBot, you might face some issues or have questions. This guide provides easy solutions to common problems and questions you might encounter.
License Not Verified
If your nuxBot seems stuck in a loop displaying License not verified. Verifying now…
, it’s likely due to your network sending too many requests.
Solution:
- Close nuxBot for 5 minutes and restart it.
- If you have too many nuxBot instances running simultaneously, reduce the number of open instances.
Invalid Signature
If you encounter an Invalid Signature
message, it means there’s an issue with the API Secret or API password (if required).
Solution:
- Double-check that your API Secret Key and API passphrase (if needed) are accurately entered in nuxBot’s exchange settings page.
- If lost, generate a new API Key on the exchange and update it in nuxBot.
Timestamp Request
Errors like Timestamp for this request is outside of the recvWindow
indicate that the time on your device isn’t set correctly.
Solution:
- Synchronize your device’s clock.
- Example for Windows: Navigate to
Settings
→Time & Language
→Date & Time
→Sync Now
.
- Example for Windows: Navigate to
Web Interface Crashed
If you get the error webinterface crashed -> The port 5000 is already in use.
, it means that another application is currently using port 5000. This conflict prevents nuxBot from starting the web interface.
Solution:
- Open the
config.ini
file in the nuxBot installation folder. - Change the port number under the
[webinterface]
section.
License Key Issues
Errors like license: type' or 'license: string indices must be integers
indicate no license key has been entered or the key isn’t valid.
Solution:
- Ensure a valid license key is entered in the Webinterface under Settings → Bot Settings → nuxBot Product Key.
- If the error persists, stop nuxBot for 5 minutes and then restart it.
Incorrect Candlestick Type
This error indicates the timeframe for one of your pairs is not supported by the exchange.
Solution:
- Check the nuxBot console for the pair causing the error.
- Enter a valid timeframe in the
Webinterface
underSettings
→Trading Settings
. Choose your pair, then click onIndicators & ATR Trailing
and underTimeframe
, enter a valid timeframe.