Exchange Connection Failed
Published Jun 22, 2026 · Updated Oct 16, 2026
Connection test failing, wallet authorization not completing, or a working account now shows an error? Note the exact message in the dialog or on the page, then match it below. Go to Account → Trading account. The full setup flow is in Connect an Exchange.
What do the connection-test messages mean?
After you click Test connection, the result appears in the dialog body.
| Message | Cause | Fix |
|---|---|---|
| Connection test failed. Check the API credentials and permissions, then try again. | The exchange rejected the credentials, or the key lacks trade permission | Re-copy the API key and secret without spaces; confirm read and trade are enabled |
| Exchange credential fields are incomplete. | A required field is empty | OKX and Bitget need the passphrase; Aster needs the wallet address |
| Enter an account name. | The account name is empty | Enter a name |
| Withdraw permission detected. Disable the withdraw permission and run the test again. | The key can withdraw, so the test does not pass | Turn off withdrawals on the exchange, then test again |
| The whitelist IP has not finished loading. Try again shortly. | The whitelist IP has not appeared in the dialog yet | Wait for the IP to show, then test |
| Service temporarily unavailable (gateway error). Please try again shortly. This is usually unrelated to your exchange API keys. | An AlphaFox service is briefly unavailable | Retry later without changing the key |
| Connection test timed out. Please try again shortly. | The exchange or network responded too slowly | Retry later; exchange maintenance also causes timeouts |
| Connection details changed. Test the connection again. | You edited credentials after testing | Click Test connection again |
| Saving is blocked until a successful connection test. | You tried to save before a passing test | Get the test to pass first |
“Withdraw permission detected” is not a warning to dismiss. If the key leaks, withdrawal permission means assets can be moved out. The key cannot be saved until withdrawals are turned off.
What if the exchange returns a specific error?
When the exchange rejects the request, the dialog shows the exchange’s error in plain language. Common ones:
| Message (excerpt) | Fix |
|---|---|
| This IP is not on the … API key allowlist. Add this service egress IP …, then retry. | Copy the whitelist IP from step 2 of the dialog and add it to the key’s IP access restriction |
| Binance API key is invalid, IP is not allowlisted, or permissions are insufficient. Check the key and whitelist, then retry. | Check, in order, that the key is complete, the whitelist IP is added, and read + trade are enabled |
| Binance USD-M trade permission is required | Enable futures trading for this key in Binance API management |
| invalid passphrase | For OKX and Bitget, enter the passphrase you set when creating the key, not your login password |
| OKX signature verification failed. Check the API secret, passphrase, and server time. | Re-copy the secret and check the passphrase |
| This Gate API key is read-only. Use a key with trading permission. | Create a new key with trade permission |
| Bybit API key is invalid. Check the key and that the environment (mainnet/demo) matches. | Use a key created on Bybit mainnet |
| Exchange authentication failed. Check the API key, permissions, and IP allowlist. | Check credentials, permissions, and the whitelist one by one |
Why does Hyperliquid wallet authorization fail?
Hyperliquid authorizes with a browser-wallet signature, so failures usually come from the wallet itself or from a main wallet that has not deposited on Hyperliquid yet.
| Message | Fix |
|---|---|
| No wallet is available. Choose a wallet in the list and connect, then try again. | Install or enable a browser wallet and finish connecting from the wallet list |
| Wallet connection cancelled. | Click Connect wallet & authorize again |
| The wallet did not return an account. Unlock the wallet and try again. | Unlock the wallet and retry |
| The wallet did not return a signature. Confirm the authorization again. | Confirm both signatures: the Agent authorization and the Builder Fee authorization |
| The HyperLiquid authorization response missed a required signing action. Start the binding again. | Close the dialog and start again |
If both signatures were confirmed and it still fails, make sure the main wallet has deposited on Hyperliquid and initialized its account (Open HyperLiquid Portfolio in the dialog lets you check). To use a different wallet, click Choose another wallet.
If Aster authorization says “The connected wallet does not match the wallet address in the API key. Switch wallets and try again.”, switch to the Aster main wallet behind the API key and authorize again.
Why did a working account become unhealthy?
Select the account on the Trading account page. If its status reads “Permission error”, “Sync error”, or “Disconnected”, the cause is usually on the exchange side: the key was deleted or revoked, its permissions changed, or its IP whitelist changed.
Repair or replace the key on the exchange
If you can restore the original key’s permissions and whitelist, do that. If the key is gone, create a new one with read + trade only and the whitelist IP added.
Add the new key as a new connection
Follow Connect an Exchange and get the test to pass. Saved connections cannot have their credentials edited.
Move the strategy to the new connection
Stop the strategy, switch its connection to the new account in the strategy config, then click Start / restart. Switching while it runs shows “Stop the strategy before changing its API connection.”
Delete the old connection
Once no strategy uses it, delete the old connection.
AlphaFox-managed Hyperliquid trading accounts have two more messages:
- “This trading account is funded, but its agent (the connector signer the platform trades with) is not authorized yet. Without it, this account cannot place orders.” Click Retry authorization.
- “The trading account is ready, but its trading connection is missing. This usually happens after deleting the API connection on this page. Reconnect it — no new deposit is needed.” Click Reconnect the trading account.
Why can’t you delete a connection?
| Message | Fix |
|---|---|
| This API connection is used by a Trader. Delete or migrate that Trader first. | In My strategies, stop and delete that strategy, or move it to another connection |
| This trading connection was created by a trading account and cannot be deleted like an ordinary API key. Stop its strategies first. | It belongs to a managed trading account; just stop the strategies that use it |
Still stuck?
Write down the exchange, the exact message, and when it happened, and send them to support@alphafox.app. Never include your full API key, secret, or private key.