Exchange Connection Failed
Published Jun 22, 2026 · Updated Jul 25, 2026
Connection test failing, or an existing connection turned unhealthy? Check in order. For the happy path, see Connect an Exchange.
Test fails
The credential itself
Key and Secret complete, no stray spaces. OKX / Bitget: the right Passphrase (the one you set at creation).
Permissions
Read and trade are both required. Read-only keys report insufficient permissions.
Whitelist IP
If the exchange enforces one, the dialog’s whitelist IP must be in the exchange’s API settings. Missing it shows up as permission or signature errors.
Try later
Exchanges reject during maintenance or risk-control windows.
“Withdrawal permission detected” is not a warning to skip—disable withdrawal on the key at the exchange before continuing.
Hyperliquid binding fails
| Message | Fix |
|---|---|
| No browser wallet detected | Install/enable MetaMask or Rabby |
| No account returned | Unlock the wallet, retry |
| No signature returned | Confirm both prompts (Agent + Builder Fee) |
| Still failing | Main wallet must be funded on Hyperliquid (USDC) |
Existing connection unhealthy
Open the health panel and read the last failure reason—usually a revoked key, changed permissions, or whitelist drift. Fix and Retry sync.
Deletion blocked
“Occupied by a strategy”: free or migrate the strategy in Live Management first.
Still stuck
Report the exchange, exact error, and time. Never include the full Key or Secret.