Exchange Issues
Troubleshooting guide for exchange-specific connection and trading problems.
Binance Issues
Connection Problems
"API Key Does Not Exist"
Causes:
- Key was deleted on Binance
- Using wrong account (main vs sub-account)
- Key not yet active (wait 24h for new keys)
Solution:
- Log into Binance
- Go to API Management
- Verify key exists
- If using sub-account, use correct API keys
- Create new key if needed
"IP Banned" / "WAF Limit"
Error:
Request failed: IP has been banned
Causes:
- Too many failed requests
- Rate limit violations
- Suspicious activity detection
Solutions:
- Wait 15-30 minutes (auto-unban)
- If persistent, contact Binance support
- Verify API credentials are correct
"Timestamp Error"
Error:
Timestamp for this request is outside of the recvWindow
Causes:
- System clock out of sync
- Network latency issues
Solutions:
- Sync your computer's clock
- Usually resolves automatically
- Try again after a few minutes
Trading Problems
"Futures Account Not Enabled"
Error:
Futures trading is not enabled for this account
Solution:
- Log into Binance
- Go to Derivatives → USD-M Futures
- Complete futures activation
- Accept terms and conditions
- Reconnect exchange in TradeStaq
"Margin Insufficient"
Solutions:
- Transfer funds to Futures wallet
- Reduce position size
- Close existing positions
- Reduce leverage
"Order Would Trigger Liquidation"
Cause: Position size too large for available margin.
Solutions:
- Reduce position size
- Add more margin
- Lower leverage setting
ByBit Issues
Connection Problems
"Invalid API Key"
Common Causes:
- Using Spot API key for Futures (or vice versa)
- Key permissions not set correctly
- Sub-account key used on main account
Solutions:
- Verify key type matches exchange type
- Create new key with correct permissions
- Use correct account's keys
"Unified Account Required"
Error:
This operation requires a Unified Trading Account
Solution:
- Log into ByBit
- Go to Assets
- Upgrade to Unified Trading Account
- Follow ByBit's upgrade process
- Reconnect in TradeStaq
Trading Problems
"Position Mode Mismatch"
Error:
Position mode mismatch
Causes:
- ByBit set to hedge mode, TradeStaq expects one-way
- Existing positions in wrong mode
Solutions:
- Close all ByBit positions
- Go to ByBit → Settings → Position Mode
- Set to "One-Way Mode"
- Retry trade
"Reduce Only Order Rejected"
Error:
Reduce-only order would increase position
Cause: Trying to close position that doesn't exist or wrong direction.
Solutions:
- Verify position exists
- Check position direction (long vs short)
- Refresh positions in TradeStaq
OKX Issues
Connection Problems
"Passphrase Required"
Error:
Missing or invalid passphrase
Note: OKX requires a passphrase in addition to API key and secret.
Solution:
- When creating OKX API key, set a passphrase
- Enter passphrase in TradeStaq connection wizard
- Keep passphrase secure
"Permission Denied"
Required Permissions:
- Read (for balance)
- Trade (for orders)
- Do NOT enable Withdraw
Solution:
- Edit API key on OKX
- Enable required permissions
- Reconnect in TradeStaq
Trading Problems
"Instrument Not Found"
Causes:
- Wrong symbol format
- Trading pair delisted
- Wrong market type
Solutions:
- Verify symbol exists on OKX
- Check if using correct market (Spot/Futures)
- Update bot configuration
Bitget Issues
Connection Problems
"API Key Expired"
Bitget API keys expire after 90 days by default.
Solution:
- Create new API key on Bitget
- Set longer expiration if available
- Update credentials in TradeStaq
Trading Problems
"Product Type Mismatch"
Cause: Using spot key for futures or vice versa.
Solution:
- Create API key for correct product
- USDT-M Futures requires specific permissions
- Update TradeStaq connection
General Exchange Issues
Sync Failures
Symptoms:
- Balance not updating
- Positions not showing
- Stale data displayed
Diagnostic Steps:
| Check | Expected |
|---|---|
| Exchange status | Online |
| API key valid | Active |
| Permissions | Read enabled |
| Rate limits | Not exceeded |
Solutions:
- Click "Sync Now" button
- Wait 30 seconds, refresh page
- Verify exchange is operational
- Check API permissions
Orders Not Executing
Diagnostic Checklist:
- Exchange connected and active?
- Sufficient balance?
- Market open?
- Valid symbol?
- Bot active (not paused)?
- Within rate limits?
Balance Discrepancy
Symptoms: TradeStaq shows different balance than exchange.
Causes:
| Cause | Solution |
|---|---|
| Sync delay | Wait/manual sync |
| Pending orders | Check open orders |
| Different wallet | Verify correct wallet |
| Exchange maintenance | Wait for completion |
Position Sync Issues
Symptoms: Position exists on exchange but not in TradeStaq.
Causes:
- Position opened directly on exchange
- Sync error occurred
- Different sub-account
Solutions:
- Manual sync
- Positions opened outside TradeStaq may not track
- Close and reopen via TradeStaq
Exchange Status Pages
Check exchange status when experiencing issues:
| Exchange | Status Page |
|---|---|
| Binance | status.binance.com |
| ByBit | status.bybit.com |
| OKX | status.okx.com |
| Bitget | status.bitget.com |
When to Contact Support
Contact TradeStaq support if:
- All troubleshooting steps tried
- Exchange working normally
- Error persists for >1 hour
- Multiple users affected (check Discord)
Include in support ticket:
- Exchange name and type
- Error message (exact text)
- Timestamp of error
- Steps already tried
- Screenshots if possible
Next Steps
- Common Errors - General error guide
- Bot Issues - Bot troubleshooting
- API Permissions - Permission guide