Ga naar de hoofdinhoud

Bitcoin Error Code Reference

Bijgewerkt op
15 april 2026
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
}

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.

-32700Parse errorRPC

Invalid JSON was received by the server; check JSON syntax and formatting

-32600Invalid RequestRPC

The JSON sent is not a valid Request object; verify the request structure matches JSON-RPC 2.0 specification

-32601Method not foundRPC

The method does not exist or is not available; verify method name spelling or check if the method requires a specific add-on (e.g., Blockbook methods like bb_gettx require the Blockbook add-on to be enabled)

-32602Invalid paramsRPC

Invalid method parameter(s); double check parameter types, values, and order against Bitcoin Core documentation

-32603Internal errorRPC

Internal JSON-RPC error; this typically indicates an issue with the Bitcoin node itself

-1Miscellaneous errorRPC

General error that doesn't fit other categories; check error message for specific details

-2Forbidden by safe modeRPC

Server is in safe mode, and command is not allowed in safe mode

-3Type errorRPC

Unexpected type was passed as parameter; ensure parameter types match expected values

-4Wallet errorRPC

Unspecified problem with wallet (key not found etc.)

-5Invalid address or keyRPC

Invalid Bitcoin address or key format; verify address/key format and network (mainnet vs testnet)

-6Insufficient fundsRPC

Not enough funds in wallet or account

-7Out of memoryRPC

Ran out of memory during operation

-8Invalid parameterRPC

Invalid, missing or duplicate parameter

-9Client not connectedRPC

Bitcoin is not connected

-10Client in initial downloadRPC

Still downloading initial blocks

-11Invalid account nameRPC

Invalid account name

-12Keypool ran outRPC

Keypool ran out, call keypoolrefill first

-13Wallet unlock neededRPC

Enter the wallet passphrase with walletpassphrase first

-14Wallet passphrase incorrectRPC

The wallet passphrase entered was incorrect

-15Wrong encryption stateRPC

Command given in wrong wallet encryption state (encrypting an encrypted wallet etc.)

-16Wallet encryption failedRPC

Failed to encrypt the wallet

-17Wallet already unlockedRPC

Wallet is already unlocked

-18Wallet not foundRPC

Invalid wallet specified

-19Wallet not specifiedRPC

No wallet specified (error when there are multiple wallets loaded)

-20Database errorRPC

Database read/write error; this may indicate corruption or disk issues

-22Deserialization errorRPC

Error parsing or validating structure in raw format; verify the raw transaction or block hex is properly formatted

-23Node already addedRPC

Node is already added

-24Node not addedRPC

Node has not been added before

-25Verify errorRPC

General error during transaction or block submission

-26Verify rejectedRPC

Transaction or block was rejected by network rules

-27Verify already in chainRPC

Transaction already in chain

-28Client in warmupRPC

Client still warming up

-29Node not connectedRPC

Node to disconnect not found in connected nodes

-30Invalid IP or subnetRPC

Invalid IP/Subnet

-31P2P disabledRPC

No valid connection manager instance found

-32007Per-second request limit reachedQuicknode

You have exceeded your plan's per-second request limit. Reduce the number of calls per second or upgrade your plan at https://dashboard.quicknode.com/billing/plan.

-32008Per-minute request limit reachedQuicknode

You have exceeded your plan's per-minute request limit. Reduce the number of calls per minute or upgrade your plan at https://dashboard.quicknode.com/billing/plan.

-32011Method rate limit reachedQuicknode

You have exceeded a method-specific rate limit configured for the endpoint. Reduce calls to the method or adjust the method rate-limit rule.

-32604Unsupported request methodQuicknode

The request method is empty, missing, or unsupported. Provide a supported JSON-RPC method name.

-32611Request rejected by filter settingsQuicknode

The request was rejected by an endpoint security filter, such as a method allowlist or blocklist. Review the endpoint's request filter settings.

Bitcoin RPC Error Code Example

The code snippet below is an example of Error Code -32601.

{
  "jsonrpc": "2.0",
  "error": {
    "code": -32601,
    "message": "Method not found"
  },
  "id": 1
}

Endpoint

Quicknode provides logs for your RPC endpoints to help you diagnose issues. You can view logs directly in your Quicknode dashboard by navigating to:


  1. Endpoints in the sidebar
  2. Selecting your endpoint
  3. 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

Laatst bijgewerkt op