跳至主要內容

Solana Error Code Reference

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

HTTP 錯誤代碼​

Let's look at the common HTTP errors you can encounter, what they mean and what you can do to prevent them.

400請求錯誤

Incorrect HTTP request type (e.g. using GET instead of POST) or invalid characters

401未經授權

One or more security requirements not met such as incorrect token auth, IP not in whitelist, invalid JWT, etc

403存取遭拒

Endpoint disabled (one reason could be a past due payment)

403Forbidden — custom trace not found in allowed custom traces

Custom trace code not whitelisted; submit a ticket to go through the approval process

404未找到

Incorrect URL or incorrect method

413內容過大

請求正文過大

429請求過多

The requests per second (RPS) of your requests are higher than your plan allows; see support docs for details

500內部伺服器錯誤

Submit a ticket for the support team to investigate as soon as possible

503服務無法使用

Submit a ticket for the support team to investigate as soon as possible

HTTP 錯誤代碼範例​

{
  "jsonrpc": "2.0",
  "error": {
    "code": 429,
    "message": "The requests per second (RPS) of your requests are higher than your plan allows."
  },
  "id": 1
}

Solana RPC Error Codes​

When working with Solana, understanding its API error codes is essential for effective troubleshooting and smooth application operation.

-32002Transaction simulation failed / preflight check errorRPC

The transaction being sent has errors; double check params, signatures, and message

-32002Blockhash not foundRPC

The blockhash sent is not known by the validator yet; implement a retry mechanism

-32003Transaction signature verification failureRPC

One or more signatures are invalid; verify private/public keys and signatures

-32004Block not available for slotRPC

Timeout or block not retrievable; use a retry mechanism

-32005Node is unhealthy / behind by slotsRPC

Node is behind the tip; retry with backoff or try another endpoint

-32007Slot was skipped or missing due to snapshot jumpRPC

Requested block does not exist; verify the slot in a block explorer

-32009Slot was skipped or missing in long-term storageRPC

The requested slot is missing from long-term storage; see support FAQ for details

-32010Key excluded from account secondary indexesRPC

Unexpected payload or incorrect data for the method; ensure request body matches validator expectations

-32013Transaction signature length mismatchRPC

Signature length is not as expected; re-encode or rebuild the transaction

-32014Block status not yet availableRPC

Block is pending or not yet synced; retry later

-32015Transaction version not supportedRPC

Use "maxSupportedTransactionVersion": 0 or upgrade client to support versioned transactions

-32016Minimum context slot not reachedRPC

The required context slot is too far in the future; lower the minimum context slot or retry later

-32602Invalid paramsRPC

Flags/params are invalid; double check method parameters against Solana docs

-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.

Solana RPC Error Code Example​

{
  "jsonrpc": "2.0",
  "error": {
    "code": -32602,
    "message": "Invalid param: Invalid"
  },
  "id": 1
}

Endpoint

Quicknode 為您的 RPC 端點Quicknode 日誌，以協助您診斷問題。您可透過導航至以下位置，直接在Quicknode 查看日誌：


  1. 側邊欄中的終點
  2. 選擇您的endpoint
  3. 開啟「日誌」分頁

您可以根據時間區間、回應類型、方法及網路來篩選日誌。

哪些內容會被記錄

Endpoint
發送至您endpoint請求，包括 HTTP 狀態碼、請求方法、RPC 方法或路徑，以及時間戳記。

錯誤詳細資訊
若有提供，失敗的請求將包含錯誤詳細資訊，例如 RPC 錯誤代碼、請求與回應正文，以及相關文件連結。

記錄限制

日誌的可用性可能因方法、回應類型、網路及方案而異。為維持最佳endpoint ，日誌記錄功能採「盡力而為」原則運作。在流量高峰期間，為維持低延遲，部分日誌可能會被捨棄。

保存與存取

「建置」與「擴展」方案包含儀表板存取權限，並提供標準的日誌保留期限。 「企業」方案則提供更長的保留期限，以及透過程式化 API 存取日誌的功能。

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

最後更新時間 於