Quicknode 为您的 RPC 端点提供错误日志。您可直接在仪表盘中查看详细的错误信息，从而轻松识别并解决问题。

HTTP 错误代码

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

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 error

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

-32002Blockhash not found

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

-32003Transaction signature verification failure

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

-32004Block not available for slot

Timeout or block not retrievable; use a retry mechanism

-32005Node is unhealthy / behind by slots

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

-32007Slot was skipped or missing due to snapshot jump

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

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

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

-32010Key excluded from account secondary indexes

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

-32013Transaction signature length mismatch

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

-32014Block status not yet available

Block is pending or not yet synced; retry later

-32015Transaction version not supported

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

-32016Minimum context slot not reached

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

-32602Invalid params

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

Solana RPC Error Code Example

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

端点日志

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

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

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

记录的内容

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

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

日志记录限制

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

保留与访问

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

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