ATRADXMARKET SYSTEMS
로그인시작하기

CONNECTION TROUBLESHOOTING

Search the error. Fix the exchange setting.

Paste an error code or search a phrase from the log. The library covers settings you may need to change at the exchange, plus time, network and order-limit checks.

!Search with error messages only. Never paste an API secret, passphrase, login password, private key or seed phrase.

19 solutions

OKXWEEXAll5011140006-1044AuthenticationError

Invalid or expired API key

The client reports Invalid API Key or AuthenticationError when connecting.

View solution

Cause

The key was copied incorrectly, belongs to another exchange environment, expired, or was deleted at the exchange.

What to do

  1. Open API Management at the exchange and confirm the key still exists.
  2. Copy the key again without spaces or line breaks.
  3. Confirm that the selected exchange and live/demo environment match the key.

Verify

Run the connection test again. If it still fails, create a new dedicated key.

OKXBitgetWEEX5011340012-1049API_PASSPHRASE_REQUIRED

Missing or incorrect API passphrase

The signature check fails or the client asks for an API passphrase.

View solution

Cause

The API passphrase is missing or does not match the value set when the key was created. It is not the login or fund password.

What to do

  1. Find the passphrase saved when the API key was created.
  2. Enter it exactly, including letter case and symbols.
  3. If it was lost, delete the key and create a new one; exchanges normally cannot reveal it again.

Verify

A successful connection should load balances without a signature error.

WEEXAll40014-1051-1052PermissionDenied

Trading permission is not enabled

Account data may load, but order placement returns Permission Denied.

View solution

Cause

The key has read access but not the spot or derivatives trading scope required by the instance.

What to do

  1. Edit the key in API Management.
  2. Enable only the required spot or futures trading permission.
  3. Keep withdrawal and unnecessary transfer permissions disabled.

Verify

Reconnect and place a small test order after permissions take effect.

WEEXAll40018-1056IP not whitelisted

Current IP is not on the allowlist

The exchange rejects authentication with an IP or whitelist error.

View solution

Cause

The key is bound to another public IP, or a dynamic network/VPN changed the current IP.

What to do

  1. Check the public IP of the computer running ATRADX.
  2. Update the exchange allowlist to that exact IP.
  3. If the IP changes frequently, use a stable-IP setup before enabling the allowlist.

Verify

Reconnect from the same network after the exchange saves the change.

OKX50101

Live and demo environments do not match

OKX returns 50101 even though the key looks correct.

View solution

Cause

A demo key is being used in live mode, or a live key is being used in demo mode.

What to do

  1. Confirm where the key was created in OKX.
  2. Select the matching environment in ATRADX, or create a key in the intended environment.

Verify

The connection should return account data from the intended environment.

OKX51010acctLv=1

OKX account is in Spot mode

Perpetual orders fail with 51010 or an unsupported account-mode message.

View solution

Cause

The OKX account is configured for Spot mode and cannot place the required perpetual order.

What to do

  1. Open OKX Trading settings.
  2. Change Account mode to a mode that supports perpetual contracts.
  3. Review the margin and risk settings shown by OKX before confirming.

Verify

Reconnect; the detected account level should no longer be Spot-only.

OKXacctLv=4Portfolio margin

Portfolio Margin conflicts with hedge mode

The client detects OKX account level 4 and cannot enable hedge mode.

View solution

Cause

OKX Portfolio Margin supports one-way positions for this workflow, while the strategy instance is configured for hedge mode.

What to do

  1. Use an OKX account mode compatible with hedge positions, or use a dedicated subaccount.
  2. Alternatively configure the ATRADX instance for one-way mode if the strategy setup allows it.

Verify

The account mode and the instance position mode must match before starting.

Bitget40774

Bitget position mode does not match

40774: The order type for unilateral position must also be the unilateral position type.

View solution

Cause

The Bitget account is in one-way mode while the order uses hedge parameters, or the reverse.

What to do

  1. Update ATRADX to the latest build, which synchronizes Bitget position mode.
  2. In Bitget Futures settings, confirm One-way or Hedge mode matches the instance.
  3. If Bitget refuses the switch, close positions and cancel open orders first.

Verify

Restart the instance and confirm that a small opening order no longer returns 40774.

OKXBitgetAll59000Position mode change failed

Existing orders or positions block a mode change

Changing position or margin mode is rejected by the exchange.

View solution

Cause

Most exchanges do not allow these settings to change while related positions or open orders exist.

What to do

  1. Stop the ATRADX instance.
  2. Cancel open orders for the symbol at the exchange.
  3. Close or safely manage existing positions, then change the mode.

Verify

Refresh the exchange page and reconnect only after the new mode is shown.

Bitget40085Unified AccountClassic API

Bitget Unified Account cannot use the Classic API

Bitget says the account is in Unified Account mode and the Classic Account API is not supported.

View solution

Cause

This is an account/API generation mismatch, not a missing option. New Unified Trading Accounts use UTA APIs instead of Classic endpoints.

What to do

  1. Do not repeatedly recreate the same Unified Account key.
  2. Use a Classic Mode subaccount if Bitget still offers it for the account.
  3. Otherwise contact ATRADX support for a UTA-compatible build before using that account.

Verify

The account must either expose Classic endpoints or connect through a confirmed UTA-compatible build.

Official reference · Bitget UTA upgrade notice ↗
OKXWEEXAll5112143006ORDER_AMOUNT_TOO_SMALL

Order amount is below the exchange minimum

The exchange rejects the order because its size or step is too small.

View solution

Cause

The configured per-order amount becomes smaller than the symbol minimum after contract-size and precision conversion.

What to do

  1. Check the symbol's minimum order size at the exchange.
  2. Increase the fixed margin or per-order amount conservatively.
  3. Do not raise leverage only to bypass the minimum without reviewing liquidation risk.

Verify

The calculated quantity must meet both the minimum and quantity step.

WEEX43007

Order amount exceeds the exchange maximum

WEEX rejects an order with code 43007.

View solution

Cause

The order quantity is above the symbol or account limit.

What to do

  1. Check the symbol limit in WEEX.
  2. Reduce fixed margin, leverage, or per-order amount.

Verify

Retry with a quantity inside the exchange range.

OKXWEEXAll5100842002InsufficientFunds

Insufficient available margin or order capacity

The exchange refuses a new order even though the account still has a balance.

View solution

Cause

Open orders, positions, fees, or the configured order size consume the currently available margin.

What to do

  1. Review open orders and positions at the exchange.
  2. Cancel unnecessary orders or reduce the configured order amount.
  3. Add margin only after reviewing the strategy's total exposure.

Verify

Use the exchange's available balance—not total equity—to confirm capacity.

WEEX-3313

Configured leverage exceeds the allowed maximum

WEEX returns -3313 when applying leverage or placing an order.

View solution

Cause

The selected leverage is above the current symbol, position-size, or account limit.

What to do

  1. Check the maximum leverage shown for the symbol.
  2. Lower the ATRADX leverage setting to an allowed value.

Verify

Reconnect and confirm the exchange accepts the leverage setting.

AllSPOT_BALANCE_INSUFFICIENT

Spot base asset or quote balance is insufficient

Spot buy or sell orders fail because an available asset balance is too low.

View solution

Cause

A buy needs available quote currency such as USDT; a sell needs available base asset such as BTC. Funds locked in orders are not available.

What to do

  1. Check available—not total—spot balances.
  2. Cancel unnecessary open orders or transfer the required asset into the spot account.
  3. Reduce the order amount if appropriate.

Verify

Confirm the correct asset is available on the same account used by the API key.

Binance-4411TradFi Perps

Binance TradFi Perpetual agreement is not signed

Binance returns -4411 and asks the user to complete the TradFi Perpetuals questionnaire or agreement.

View solution

Cause

The selected product requires an agreement that has not been completed, or the product is unavailable for the account/region.

What to do

  1. Sign in to Binance web or app and open the TradFi Perpetuals entry.
  2. Complete the required questionnaire and agreement if the entry is available.
  3. If no entry is shown, use an ordinary crypto perpetual symbol or contact Binance.

Verify

Retry only after Binance shows the product as enabled for the account.

Official reference · Binance TradFi Perpetuals FAQ ↗
OKXWEEXAll501024000540008Timestamp error

Computer time is out of sync

Authentication fails with a timestamp, expiry, or request-time error.

View solution

Cause

The computer clock differs too much from the exchange server time.

What to do

  1. Enable automatic date and time in the operating system.
  2. Confirm the timezone is correct, then force a time sync.
  3. Restart ATRADX after synchronization.

Verify

The system clock should match an internet time source to within a few seconds.

BinanceOKXWEEX-100350011-1059Rate limit

Rate limit or temporary IP ban

Requests are rejected as too frequent; Binance -1003 may include an IP-ban reset time.

View solution

Cause

Too many requests were sent in the exchange's limit window, sometimes after repeated restarts.

What to do

  1. Stop repeatedly restarting or reconnecting the instance.
  2. Wait until the exchange's stated reset time.
  3. During a ban, check and manage open orders directly at the exchange.

Verify

Restart once after the reset window and monitor for recurring bursts.

AllNETWORK_ERRORConnection timeout

Exchange API cannot be reached

Connection times out, DNS fails, or the client repeatedly reports NETWORK_ERROR.

View solution

Cause

The local network, firewall, proxy, VPN route, or regional availability prevents access to the exchange API.

What to do

  1. Confirm the exchange website and API are available in the user's region.
  2. Check firewall, proxy and VPN settings; use a stable route permitted by the exchange.
  3. Do not bypass laws or exchange regional restrictions.

Verify

Run the connection test again on the same stable network.

Still need help? Contact support ↗