Common connection errors
The messages SmartDOM shows when adding or editing a connection, and what to do about them.
Terminal messages
Section titled “Terminal messages”| Message | Cause | What to do |
|---|---|---|
| Select an exchange / Enter a connection name / Enter API Key and Secret Key / Enter Passphrase | A required field is empty. | Fill it in and retry. |
| Invalid API keys | The exchange rejected the key: a typo, the key was deleted, created for another account or for the exchange’s demo mode. For OKX and Bitget a wrong passphrase also ends up here. | Create a new key on the exchange and paste it again, checking all fields. |
| Invalid passphrase | Bitget reported that the phrase does not match. | A passphrase cannot be viewed on the exchange. Create a new key with a new phrase. |
| Local clock is out of sync with the exchange (>30 s). Check the system time. | The computer’s time differs from the exchange’s by more than 30 seconds. | Windows → Settings → Time & language → enable automatic time and click “Sync now”. |
| IP address is not in the API key whitelist | The key has an IP restriction on the exchange and your address is not on the list. | Add the address to the list on the exchange or remove the restriction. |
| The API key has insufficient permissions. Enable Read and Trade. | The key was created without read or trade permission. | Change the key’s permissions on the exchange or create a new one. |
| Network error. Check the connection | The exchange is unreachable: no internet, blocking, VPN. | Check access to the exchange website from a browser. |
| Save error. Try again. | The connection could not be written to disk. | Retry. If it repeats, check that the %LOCALAPPDATA%\TradeSystem folder is writable. |
Exchange codes you may see in a message
Section titled “Exchange codes you may see in a message”- Bitget: 40001 invalid key, 40002 invalid signature (secret does not match), 40003 time, 40004 passphrase, 40005 IP, 40006 and 40014 insufficient permissions, 40012 key, secret or passphrase is wrong, 40037 key does not exist.
- MEXC: 401 unauthorised, 402 key expired, 406 IP not whitelisted, 701–704 no read or trade permission.
- Binance: -1021 time difference. The terminal resynchronises the clock itself and retries.
- OKX: 50113 signature error, usually due to extra characters in the copied key.
- Gate: the exchange replies with labels rather than codes, they appear in order error messages: INVALID_KEY and INVALID_SIGNATURE wrong key or secret, IP_FORBIDDEN IP not whitelisted, READ_ONLY read-only key, REQUEST_EXPIRED time mismatch, USER_NOT_FOUND futures wallet not created.
- KuCoin: 400003 and 400005 wrong key or secret, 400004 wrong passphrase, 400006 IP not whitelisted, 400007 the key lacks permissions (enable Spot Trading and Futures Trading), 400002 time mismatch. On a futures order 330008 means there is no free margin in the Futures account: transfer funds from Funding or spot on the exchange website.
The connection worked and then stopped
Section titled “The connection worked and then stopped”- The key was deleted or expired on the exchange. Symptom: orders are not placed, authorisation errors in the logs. Create a new key and change the connection with the Edit button.
- The IP address changed while the IP restriction is enabled.
- The computer clock drifted.