Skip to main content

Solana Error Code Reference

Updated on
Aug 25, 2025
QuickNode now provides Logs for your RPC endpoints. Easily identify and resolve issues by viewing detailed error information directly from your dashboard.

HTTP Error Codes

Let's look at the common HTTP errors you can encounter, what they mean and what you can do to prevent them.

400
Bad Request
Incorrect HTTP request type (e.g. using GET instead of POST) or invalid characters
401
Unauthorized
One or more security requirements not met such as incorrect token auth, IP not in whitelist, invalid JWT, etc
403
Forbidden
Endpoint disabled (one reason could be a past due payment)
403
Forbidden — custom trace not found in allowed custom traces
Custom trace code not whitelisted; submit a ticket to go through the approval process
404
Not Found
Incorrect URL or incorrect method
413
Content Too Large
Body of the request is too large
429
Too Many Requests
The requests per second (RPS) of your requests are higher than your plan allows; see support docs for details
500
Internal Server Error
Submit a ticket for the support team to investigate as soon as possible
503
Service Unavailable
Submit a ticket for the support team to investigate as soon as possible

HTTP Error Code Example

{
"jsonrpc": "2.0",
"error": {
"code": 429,
"message": "The requests per second (RPS) of your requests are higher than your plan allows."
},
"id": 1
}

Solana RPC Error Codes

When working with Solana, understanding its API error codes is essential for effective troubleshooting and smooth application operation.

-32002
Transaction simulation failed / preflight check error
The transaction being sent has errors; double check params, signatures, and message
-32002
Blockhash not found
The blockhash sent is not known by the validator yet; implement a retry mechanism
-32003
Transaction signature verification failure
One or more signatures are invalid; verify private/public keys and signatures
-32004
Block not available for slot
Timeout or block not retrievable; use a retry mechanism
-32005
Node is unhealthy / behind by slots
Node is behind the tip; retry with backoff or try another endpoint
-32007
Slot was skipped or missing due to snapshot jump
Requested block does not exist; verify the slot in a block explorer
-32009
Slot was skipped or missing in long-term storage
The requested slot is missing from long-term storage; see support FAQ for details
-32010
Key excluded from account secondary indexes
Unexpected payload or incorrect data for the method; ensure request body matches validator expectations
-32013
Transaction signature length mismatch
Signature length is not as expected; re-encode or rebuild the transaction
-32014
Block status not yet available
Block is pending or not yet synced; retry later
-32015
Transaction version not supported
Use "maxSupportedTransactionVersion": 0 or upgrade client to support versioned transactions
-32016
Minimum context slot not reached
The required context slot is too far in the future; lower the minimum context slot or retry later
-32602
Invalid params
Flags/params are invalid; double check method parameters against Solana docs

Solana RPC Error Code Example

{
"jsonrpc": "2.0",
"error": {
"code": -32602,
"message": "Invalid param: Invalid"
},
"id": 1
}

If you're experiencing other error codes, please submit a ticket — we're happy to help 🚀

Share this doc