Aster Errors
Aster errors in LootX: two key types, three connection fields, "No aster user found", "Signature check failed", device time, IP ban, and order codes.
Aster is a decentralized exchange with a Binance-style API, so its error codes are the same as Binance’s: a negative number in the code field and an explanation in msg, for example {"code":-2010,"msg":"Account has insufficient balance for requested action"}. Aster differs in how you connect: keys come in two kinds — the old API key with a secret, and the new API wallet key with a main wallet address. Most connection errors come from filling fields for the wrong key type.
If the terminal doesn’t recognize an order rejection, the pop-up message after “Order:” will contain Aster’s response as is. The terminal shows connection failures in the tooltip for the connection in Settings → Connections and in the log — the same place where the disconnect reason is visible. For general troubleshooting, see Error messages: how to read them; for key setup, see Connecting exchanges and API keys.
What the terminal explains itself
| Situation | Exchange codes and response | What you see |
|---|---|---|
| Exchange rejected the key | -2014, -2015 |
Card “…: exchange rejected the API key or secret — check them in the connection settings”, and a tooltip on the connection: “Exchange rejected the API key or secret” |
| Signature mismatch | -1022, “Signature check failed” |
On connection — the same card, and in the log an English tooltip: “Aster: signature rejected…”; on an order — “Order rejected: invalid API key or secret” |
| Main wallet not found | “No aster user found” | In the connection tooltip and in the log: “Aster: ‘No aster user found’ — fill the "Account Id" field…” or “…the address in "Account Id" isn’t recognised…”. Details — below |
| Clock out of sync with the exchange | -1021, “Your device time must match the actual time” |
The terminal checks the time with Aster itself before the first signed request. If the rejection still comes — in the connection tooltip: “Aster: timestamp out of recvWindow — adjust your system clock or check NTP.” |
| IP address banned | HTTP 418 | Card “Too many requests to the exchange, IP address banned until … UTC”. Until that time, the terminal sends no requests to Aster from this address |
| Too many requests | HTTP 429 | Card “Rate limit (429), pause ~… s — until … UTC”. The terminal holds the pause on its own |
| Order no longer exists | -2011 |
Nothing: the terminal itself asks the exchange for the final order status |
| Not enough coins to close a spot position | -2010 |
The terminal retries the sale with a slightly smaller amount — within the fee. If that doesn’t help, it shows the exchange text |
| Nothing to close on spot | — | “Aster …: nothing to sell — balance … = 0, position already closed” with the pair and coin names. No order is sent to the exchange |
Common codes
| Code | What it looks like | Reason | What to do |
|---|---|---|---|
-2014, -2015 |
Card “exchange rejected the API key or secret” | Key is wrong, deleted, or of the wrong type | Check the fields — see Two key types |
-1022 |
Card or “Order rejected: invalid API key or secret” | Signature mismatch: the secret or private key doesn’t match | Re-enter the secret or private key |
| “Signature check failed” | Card “exchange rejected the API key or secret”, log tooltip | Private key and Account Id are not from the same pair | See Signature check failed |
| “No aster user found” | Connection tooltip | Account Id is not a main wallet address, or it is empty | See No aster user found |
-1021 |
Usually nothing; on a sudden clock jump — tooltip “timestamp out of recvWindow” | Computer clock has drifted from the exchange | Enable time sync in Windows |
-2010 |
Exchange text in the order message: “Account has insufficient balance for requested action” | Not enough free funds | Reduce the size or cancel extra orders |
-2019 |
Exchange text in the order message about insufficient margin | Not enough margin on futures given the leverage | Reduce size or leverage, or top up the account |
-1013 |
Exchange text in the order message: “Filter failure: …” | Size or price failed the pair’s filter: below the minimum, or not following the size or price step | Fix the size or price. Reducing size does not fix this rejection, so the terminal does not retry it |
-2011 |
Nothing | The order being cancelled no longer exists: it was filled or already cancelled | Nothing to do |
| HTTP 418 | “Too many requests to the exchange, IP address banned until … UTC” | Too many requests from one IP | See IP ban |
How to fix common problems
Two key types
An Aster connection has three fields: API key / API wallet address, API secret / Private key, and Account Id. The terminal figures out your key type on its own — from what is in the second field: a 0x… private key or a seed phrase means the new wallet-signing type, anything else is the old API key.
This is how Aster issues keys now: the Generate API Key button on the exchange website creates a separate API wallet that signs orders on behalf of the main one.
- API secret / Private key — the API wallet’s private key (
0xplus 64 characters) or its seed phrase. - Account Id — the address of the main wallet, the one connected on the Aster website and holding your funds. Not the API wallet address.
- API key / API wallet address — the API wallet address.
Fill in all three fields. If you pasted the main wallet’s own private key instead of the API wallet key, put that same wallet’s address in Account Id.
A key and secret, like on Binance. Aster issued these keys before March 25, 2026; it no longer issues new ones, but old ones still work.
- API key / API wallet address — the API key.
- API secret / Private key — the secret.
- Account Id — not used for this key type.
With a main wallet key, the terminal can approve the LootX builder fee on its own; with an API wallet it cannot, and orders go out without it. Trading is not affected.
No aster user found
Aster did not find the main account for the address that signed the request. Almost always the reason is: only the API wallet private key was pasted, and Account Id is empty. The terminal then treats the API wallet itself as the main wallet — and it has no account.
Find your main wallet address
This is the wallet you use to log into the Aster website and that holds your funds.
Paste it into Account Id
Open the Aster connection in Settings → Connections and paste the 0x… address into Account Id.
Check that the address matches
If the field is already filled and the error persists, the address doesn’t match the wallet on the Aster website. Copy it again.
Signature check failed
Aster recovered an address from the signature that is not registered as an API wallet for this account. This means the private key and Account Id are not from the same pair: for example, the key is from one API wallet and the address from another account, or the API wallet was deleted on the Aster website.
Paste the private key of the API wallet created with the Generate API Key button for your main wallet, and put that main wallet’s address in Account Id. If the API wallet was deleted, create a new one.
IP ban
Like Binance, Aster responds with 418 and bans the IP when there are too many requests. The terminal reads the ban end time from the exchange’s response and sends no requests to Aster from that address until then — otherwise the ban extends.
Wait until the stated time. If you need to trade sooner, switch the connection to another proxy (the Proxy section in the connection card). The limit is per address: Aster connections to the same market through one IP or proxy share the same quota, so if it repeats, spread them across different proxies. Details in Terminal messages.
Spot with an API wallet key
The terminal signs spot requests with the same key type as futures. The new signature for the spot API appeared later on Aster than for futures. If futures connect with an API wallet key but spot does not, read the reason in the connection tooltip: it is the exchange’s response.