跳转至主要内容

Bitcoin Error Code Reference

更新于
2026年4月15日
Quicknode 为您的 RPC 端点提供错误日志。您可直接在仪表盘中查看详细的错误信息,从而轻松识别并解决问题。

HTTP 错误代码

下面我们来看看您可能会遇到的常见 HTTP 错误代码、它们的含义以及如何预防这些错误。

400请求错误

HTTP 请求类型不正确(例如,使用 GET 而不是 POST)或包含无效字符

401未授权

当一项或多项安全要求未得到满足时,可能会发生这种情况,例如令牌认证错误、IP 地址不在白名单中、JWT 无效等。

403访问被禁止

终端已停用(原因之一可能是逾期未付款)

403访问被禁止 - 未找到自定义跟踪

自定义跟踪代码未被列入白名单(请提交工单以完成审批流程)

404未找到

URL 错误或方法错误

413内容过大

请求正文过大

413请求实体过大

eth_getLogs 和 eth_newFilter 仅支持 10,000 个区块的范围。在请求日志和事件时,我们强制执行 10,000 个区块范围的限制。

429请求过多

您的每秒请求数(RPS)超出了套餐允许的范围。请查阅我们的支持文档,了解有关 429 错误的更多信息。

500服务器内部错误

请提交工单,以便支持团队尽快检查这些错误

503服务不可用

请提交工单,以便支持团队尽快检查这些错误

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.

-32700解析错误

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

-32600Invalid Request

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

-32601方法未找到

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)

-32602Invalid params

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

-32603Internal error

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

-1Miscellaneous error

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

-2Forbidden by safe mode

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

-3Type error

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

-4Wallet error

Unspecified problem with wallet (key not found etc.)

-5Invalid address or key

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

-6Insufficient funds

Not enough funds in wallet or account

-7Out of memory

Ran out of memory during operation

-8Invalid parameter

Invalid, missing or duplicate parameter

-9Client not connected

Bitcoin is not connected

-10Client in initial download

Still downloading initial blocks

-11Invalid account name

Invalid account name

-12Keypool ran out

Keypool ran out, call keypoolrefill first

-13Wallet unlock needed

Enter the wallet passphrase with walletpassphrase first

-14Wallet passphrase incorrect

The wallet passphrase entered was incorrect

-15Wrong encryption state

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

-16Wallet encryption failed

Failed to encrypt the wallet

-17Wallet already unlocked

Wallet is already unlocked

-18Wallet not found

Invalid wallet specified

-19Wallet not specified

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

-20Database error

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

-22Deserialization error

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

-23Node already added

Node is already added

-24Node not added

Node has not been added before

-25Verify error

General error during transaction or block submission

-26Verify rejected

Transaction or block was rejected by network rules

-27Verify already in chain

Transaction already in chain

-28Client in warmup

Client still warming up

-29Node not connected

Node to disconnect not found in connected nodes

-30Invalid IP or subnet

Invalid IP/Subnet

-31P2P disabled

No valid connection manager instance found

Bitcoin RPC Error Code Example

下面的代码片段是错误代码-32601 的示例。

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

端点日志

Quicknode 会为您的 RPC 端点提供日志,以帮助您排查问题。您可以在Quicknode 控制台中直接查看日志,方法是导航至:


  1. 侧边栏中的端点
  2. 选择您的终端
  3. 打开“日志”选项卡

您可以按时间范围、响应类型、方法和网络对日志进行筛选。

记录的内容

端点请求
发送到您端点的请求,包括 HTTP 状态、请求方法、RPC 方法或路径以及时间戳。

错误详细信息
如有提供,失败的请求将包含错误详细信息,例如 RPC 错误代码、请求和响应正文,以及相关文档的链接。

日志记录限制

日志的可用性可能因方法、响应类型、网络和套餐而异。为保持端点性能最佳,日志记录采用“尽力而为”的原则。在流量高峰期间,为保持低延迟,部分日志可能会被丢弃。

保留与访问

“构建”和“扩展”套餐包含仪表盘访问权限,并提供标准日志保留服务。 “企业”套餐则提供更长的日志保留期限,以及用于检索日志的程序化 API 访问权限。

如果您遇到其他错误代码,请通过提交工单告知我们。我们非常乐意为您提供帮助。

分享此文档