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 error codes 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
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.
403
Forbidden
Endpoint Disabled (One of the reasons for this could be a past due payment)
403
Forbidden - custom trace not found
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
413
Request 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.
429
Too 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.
500
Internal Server Error
Submit a ticket for the support team to take a look at the errors asap
503
Service 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
}
Bitcoin RPC Error Codes
Let's look at the common bitcoin rpc error codes you can encounter, what they mean and what you can do to prevent them.
-32700
Parse error
Invalid JSON was received by the server; check JSON syntax and formatting
-32600
Invalid Request
The JSON sent is not a valid Request object; verify the request structure matches JSON-RPC 2.0 specification
-32601
Method not found
The method does not exist or is not available; verify method name spelling or check if the method requires a specific marketplace add-on (e.g., Blockbook methods like bb_gettx require the Blockbook add-on to be enabled)
-32602
Invalid params
Invalid method parameter(s); double check parameter types, values, and order against Bitcoin Core documentation
-32603
Internal error
Internal JSON-RPC error; this typically indicates an issue with the Bitcoin node itself
-1
Miscellaneous error
General error that doesn't fit other categories; check error message for specific details
-2
Forbidden by safe mode
Server is in safe mode, and command is not allowed in safe mode
-3
Type error
Unexpected type was passed as parameter; ensure parameter types match expected values
-4
Wallet error
Unspecified problem with wallet (key not found etc.)
-5
Invalid address or key
Invalid Bitcoin address or key format; verify address/key format and network (mainnet vs testnet)
-6
Insufficient funds
Not enough funds in wallet or account
-7
Out of memory
Ran out of memory during operation
-8
Invalid parameter
Invalid, missing or duplicate parameter
-9
Client not connected
Bitcoin is not connected
-10
Client in initial download
Still downloading initial blocks
-11
Invalid account name
Invalid account name
-12
Keypool ran out
Keypool ran out, call keypoolrefill first
-13
Wallet unlock needed
Enter the wallet passphrase with walletpassphrase first
-14
Wallet passphrase incorrect
The wallet passphrase entered was incorrect
-15
Wrong encryption state
Command given in wrong wallet encryption state (encrypting an encrypted wallet etc.)
-16
Wallet encryption failed
Failed to encrypt the wallet
-17
Wallet already unlocked
Wallet is already unlocked
-18
Wallet not found
Invalid wallet specified
-19
Wallet not specified
No wallet specified (error when there are multiple wallets loaded)
-20
Database error
Database read/write error; this may indicate corruption or disk issues
-22
Deserialization error
Error parsing or validating structure in raw format; verify the raw transaction or block hex is properly formatted
-23
Node already added
Node is already added
-24
Node not added
Node has not been added before
-25
Verify error
General error during transaction or block submission
-26
Verify rejected
Transaction or block was rejected by network rules
-27
Verify already in chain
Transaction already in chain
-28
Client in warmup
Client still warming up
-29
Node not connected
Node to disconnect not found in connected nodes
-30
Invalid IP or subnet
Invalid IP/Subnet
-31
P2P disabled
No valid connection manager instance found
Bitcoin RPC Error Code Example
The code snippet below is an example of Error Code -32601.
QuickNode provides logs for your RPC endpoints to help you diagnose issues and track transaction activity. 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
RPC Errors All failed requests including invalid methods, malformed parameters, execution errors, and network timeouts.
Transaction Submissions Send transaction requests and their success or failure status.
Logging Limitations
Only RPC errors and transaction submissions are logged — successful read operations are not captured. 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