An exchange account won’t save or shows Not connected
When you save an account, Trade verifies the API key with the exchange. If verification fails, it names the kind of problem.
Follow the message
| Trade says | What to do |
|---|---|
| The API key is wrong | Copy the key, secret and passphrase from the same key again. Check for missing or extra characters |
| The API permissions are insufficient | On the exchange, turn on the permissions listed under Enable in the API key section of the add-account window, named as on the exchange. Exchanges that don’t report permissions aren’t checked when you save, so check them against that list yourself |
| The IP allowlist doesn’t include the server | Add the Server egress IPs listed in the add-account window to the API key’s IP allowlist |
| The account mode doesn’t meet the requirements | Switch the account mode on the exchange to the mode named in the message, then save |
| The server clock doesn’t match the exchange | Sync the server clock, for example with timedatectl set-ntp true |
| Can’t reach the exchange | Try again in a moment. If it keeps failing, check the server network |
| The exchange has temporarily locked or restricted API requests | Save again in a little while. Every retry is rejected during the restriction |
If the exchange refuses to set the position mode because positions or orders are open, close them and save again.
Saved, but it shows Not connected
Choose Retry connection. If the exchange later rejects the key, for example because it expired or was deleted, Trade doesn’t send a notification. The account shows that it can’t connect on the Accounts page; replace the key there. Connect an exchange has the full steps.