Quicknode provides Error 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 Error Codes you can encounter, what they mean and what you can do to prevent them.
400Bad Request
Incorrect HTTP Request type (e.g. using GET instead of POST) or Invalid Characters
401Unauthorized
This can happen when one or multiple security requirements are not met such as incorrect Token Auth, IP not in the whitelist, invalid JWT, etc.
403Forbidden
Endpoint Disabled (One of the reasons for this could be a past due payment)
403Forbidden - custom trace not found
Custom trace code not whitelisted (Submit a ticket to go through the approval process)
404Not Found
Incorrect URL or Incorrect method
413Content Too Large
Body of the request is too large
413Request Entity Too Large
eth_getLogs and eth_newFilter are limited to a 10,000 blocks range. We enforce a limit of 10,000 block ranges when requesting logs and events.
429Too Many Requests
The requests per second (RPS) of your requests are higher than your plan allows. Learn more about the 429 errors in our support documentation.
500Internal Server Error
Submit a ticket for the support team to take a look at the errors asap
503Service Unavailable
Submit a ticket for the support team to take a look at the errors asap
HTTP Error Code Example
The code snippet below is an example of Error Code 429.
{
"jsonrpc": "2.0",
"error": {
"code": 429,
"message": "The requests per second (RPS) of your requests are higher than your plan allows."
},
"id": 1
}
JOC RPC Error Codes
Let's look at the common JOC RPC Error Codes you can encounter, what they mean and what you can do to prevent them.
-32000Header not found / Block not found
The requested block doesn't exist on the node. Invalid block number or the node you're hitting is not in sync yet. Use a retry mechanism with an incremental timeout
-32000Stack limit reached
Usually a smart contract error/bug - stack limit reached 1024 (1023)
-32000Method handler crashed
Internal error from the blockchain client, which can be a client bug. Submit a ticket so we can double check the nodes
-32000Execution timeout
Add the timeout param in your request to override the default client timeout.
-32000Nonce too low
The nonce value specified in your transaction is lower than the next valid nonce for the sender account.
-32000Filter not found
Filter exceeded timeout; you'll have to recreate the filter once more.
-32001Resource Not Found
The requested resource does not exist or is unavailable.
-32002Resource Unavailable
The requested resource is temporarily or permanently unavailable.
-32003Transaction Rejected
The transaction could not be created due to validation failure or insufficient resources.
-32004Method Not Supported
The requested method is not implemented or supported by the server.
-32005Limit Exceeded
The request exceeds the allowed limit or quota.
-32006JSON-RPC Version Not Supported
The specified JSON-RPC version is not supported by the server.
-32009Trace requests limited
We have limited the debug and trace method to a specific RPS to prevent the nodes from overloading
-32010Transaction cost exceeds gas limit
Gas limit is set too low
-32011Network error
This error occurs when there is a problem with the connection between the client and server, such as a timeout or a dropped connection
-32015VM execution error
Smart contract execution error
-32600Invalid request
JSON request is malformed or missing required fields. Ensure it follows the expected format
-32601Method not found
Typically a typo in the method name; check for spelling errors
-32601Failed to parse request
Incorrect request body; double check the method params
-32602Invalid params - missing 0x prefix
Incorrect request; the 0x is missing from the address. the hex
-32602Block range limit exceeded
eth_getLogs and eth_newFilter are limited to a 10,000 blocks range. Read an in-depth explanation in our support documentation.
-32603Internal JSON-RPC error
This error is typically due to a bad or invalid payload
-32612Custom traces are blocked
Submit a request to get custom traces enabled.
-32613Custom trace not allowed
Custom trace not found in allowed custom traces. Submit a request to get this trace whitelisted.
-32700Parse error
Invalid JSON received. The server encountered an error while parsing the JSON text
3Execution reverted
The transaction was reverted during execution, likely due to failing conditions, insufficient gas, or a contract error
JOC RPC Error Code Example
The code snippet below is an example of Error Code -32601.
{
"jsonrpc": "2.0",
"id": 1,
"error": {
"code": -32601,
"message": "the method eth_randomMethod does not exist/is not available"
}
}
The RPC errors defined above are a collection of common errors you can encounter while developing on chains like ETH, BSC, Polygon, etc. These chains run on multiple clients with their own error definitions. You can view the errors mentioned in the node client source here as well:
Quicknode provides logs for your RPC endpoints to help you diagnose issues. You can view logs directly in your Quicknode dashboard by navigating to:
Endpoints in the sidebar
Selecting your endpoint
Opening the Logs tab
You can filter logs by time window, response type, method, and network.
What Gets Logged
Endpoint Requests Requests made to your endpoint, including the HTTP status, request method, RPC method or path, and timestamp.
Error Details When available, failed requests include error details such as RPC error codes, request and response bodies, and links to related documentation.
Logging Limitations
Log availability can vary by method, response type, network, and plan. To maintain optimal endpoint performance, logging operates on a best-effort basis. Some logs may be dropped during high-traffic periods to preserve low latency.
Retention and Access
Build and Scale plans include dashboard access with standard log retention. Enterprise plans provide extended retention periods and programmatic API access for log retrieval.
If you're experiencing other error codes, please let us know by submitting a ticket. We're more than happy to assist