Exchange Connection Failed
Published Jun 22, 2026 · Updated Aug 12, 2026
Connection test failing, or an existing connection turned unhealthy? Check in order. For the happy path, see Connect an Exchange.
Why does the connection test fail?
Almost every failed test comes down to one of four things: a credential that was copied incompletely, a key missing trade permission, a whitelist IP that was never added at the exchange, or the wrong passphrase on OKX and Bitget. Check them in that order.
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.
Why does Hyperliquid binding fail?
Hyperliquid authorizes through wallet signatures rather than an API key, so failures come from the browser wallet or from an unfunded main wallet rather than from permissions.
| 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) |
Why did a working connection turn unhealthy?
A connection that used to work usually broke at the exchange side, not in AlphaFox. Open the health panel and read the last failure reason—typically a revoked key, changed permissions, or whitelist drift. Fix it there, then Retry sync.
Why can’t I delete a connection?
“Occupied by a strategy” means a Trader is still bound to it. Free or migrate that strategy in My strategies first, then delete the connection.
What if none of this fixes it?
Email support@alphafox.app with the exchange, the exact error text, and the time it happened. Never include the full Key or Secret in a report.