跳至主要內容

Bitcoin Error Code Reference

更新於
2026年4月15日
Quicknode 為您的 RPC 端點提供錯誤日誌。您可直接從儀表板查看詳細的錯誤資訊,輕鬆識別並解決問題。

HTTP 錯誤代碼

讓我們來看看您可能會遇到的常見 HTTP 錯誤代碼、它們的含義,以及該如何預防這些錯誤。

400請求錯誤

HTTP 請求類型不正確(例如:使用 GET 而非 POST)或包含無效字元

401未經授權

當一項或多項安全性要求未獲滿足時,便可能發生此情況,例如:令牌驗證錯誤、IP 位址未在白名單中、JWT 無效等。

403存取遭拒

終端裝置已停用(其中一個原因可能是款項逾期未付)

403禁止存取 - 未找到自訂追蹤

自訂追蹤代碼未列入白名單(請提交服務單以進行審核流程)

404未找到

網址不正確或方法不正確

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 存取日誌的功能。

如果您遇到其他錯誤代碼,請透過提交服務單告知我們。我們非常樂意為您提供協助

分享這份文件