Submit a ticket for the support team to take a look at the errors asap
503服务不可用
Submit a ticket for the support team to take a look at the errors asap
HTTP 错误代码示例
下面的代码片段是一个错误代码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.