Errors are mainly shown in the order log or the system log. Find the matching error code and check it yourself!
(0)-0 Service temporarily unavailable. You can try changing the IP or try again later (this is an issue with Binance itself)
(1)-1002 No request permission. Check whether the API Key has USDT-M futures permission. If the key pair was generated before the deposit, the API will have no permission no matter how it is configured, so the key pair must be regenerated
(2)-1003 Request overload. This is mainly because requests from the same IP exceed the Binance API limit; change the IP proxy
(3)-1007 Server connection timed out; change to a faster IP proxy
(4)-1008 Server overloaded. Please try again later; this is an official Binance issue and cannot be resolved
(5)-1014 Order parameters not supported. Check whether One-way Mode or Isolated Margin mode is enabled, and change to Cross Margin mode and Multi-Assets Margin
(6)-1015 New order limit exceeded
(7)-1016 Service currently unavailable
(8)-1020 Unsupported operation
(9)-1021 Invalid request time. Please sync your computer time with the Hong Kong time service center
(10)-1022 Invalid signature. Log in to the client again and retry. If it still fails, check whether the key pair is correct; regenerating the key pair is recommended
(11)-1109 Invalid account
(12)-2010 New order rejected
(13)-2011 Cancel order rejected
(14)-2013 Order does not exist
(15)-2015 Invalid API Key or the IP has no permission. This is usually an IP permission issue, so change the IP; if the proxy is fine, then it is an API Key issue
(16)-2017 API Key is locked; regenerate the KEY
(16)-2019 Insufficient margin
(17)-2025 The number of open orders has reached the limit
(18)-4027 Incorrect account type
(19)-4045 Stop-loss order limit reached
(19)-4061 Binance USDT-M futures settings are incorrect; Cross Margin mode and Multi-Assets Margin are required
(20)-2019 Insufficient margin
(20) Account information was retrieved successfully, but a pop-up says the data check failed. This mainly means you need to check whether margin has been transferred to the USDT-M futures account; this prompt appears when the margin is 0
(21) When there is no data response at all and no error code: time not synchronized / IP restricted
(22) The client freezes and does not respond: network reasons, computer sleep, antivirus software, etc.
Other errors and solutions
(1) - When logging in to the client, the prompt "Device machine code mismatch, please unlock and try again" appears. Go to the official website - User Center - Device Management - Unlock Device
(2) - When logging in to the client, the prompt "Client authorization has expired, please renew and try again" appears. If the client has expired, go to the official website - User Center - Device Management - Renew (if you have no balance, contact customer service / your agent to top up and then renew)
(3) - When checking the client status, the prompt "Invalid TOKEN" appears. Log in to the client again
(3) The order log window shows an all-in short, but the order was not placed successfully. This mainly means the corresponding position has entered the liquidation protection zone
(4) Clicking the client login button shows a blank pop-up, which means the authorization server cannot be connected; consider changing [Proxy] to TUN mode