RPC Error Reference

When users encounter RPC Errors, they often come from three different domains:

1. Network errors - These are unrelated to the RPC service itself, but rather caused by network connectivity issues between the user and the CDN service provider. The error messages are typically traditional network errors, which we will not list here.

2. Errors from the node itself - We will try to list these as comprehensively as possible to help users troubleshoot.

3. Service restrictions triggered due to the user's account level - We will list these in a separate table.

This page is still under continuous improvement. If you encounter an error that is not listed here, please contact us on Discord or open a support ticket.

Node Error Message

RPC Error Message	Causes	Suggestions
404 Client Error: Not Found for url: <endpoint>	Beacon chain data pruned.	Activate Archive Mode for the RPC endpoint
missing trie node	Missing historical data	Activate Archive Mode for the RPC endpoint
required historical state unavailable	Missing historical data	Activate Archive Mode for the RPC endpoint
missing revert data in call exception	Missing historical data	Activate Archive Mode for the RPC endpoint

BlockPI Error Message

RPC Error Message	Causes	Suggestions
ErrorWsDisabledOnPublicEndpoints	Websocket is not supported on public endpoints	Create a private endpoint at https://dashboard.blockpi.io
ErrorInvalidRequest	Invalid request	Double check your request format
ErrorMaxMessagesExceed	Batch number exceed the limit	Decrease the number of payload in one request
ErrorMaxWsBatchSizeExceed	Batch number exceed the limit for WSS	Decrease the number of payload in one request
ErrorTicketRateLimitExceed	apikey rate limit exceed	Decrease the QPS
ErrorMethodDisabled	RPC method is disabled
ErrorRateLimitExceed	apikey rate limit exceed	Decrease the QPS
ErrMethodLogsArgvLimit1024	The method is limited to 1024 block range.	Decrease the number of blocks in one request
ErrMethodTraceFilterLimit1024	The method is limited to 1024 block range.	Decrease the number of blocks in one request
ErrMethodNewFilterLimit1024	The method is limited to 1024 block range.	Decrease the number of blocks in one request
ErrMethodLogsArgvLimit5000	The method is limited to 5000 block range with 'address' param.	Decrease the number of blocks in one request
ErrMethodNewFilterLimit5000	The method is limited to 5000 block range with 'address' param.	Decrease the number of blocks in one request
ErrMethodTraceFilterLimit5000	The method is limited to 5000 block range with 'address' param.	Decrease the number of blocks in one request
ErrMaxResponseMessageSizeExceed	max message response size exceed.	Buy a more advanced RU package
ErrInvalidTracer	Invalid tracer.
ErrApikeyNotFound	Apikey not found	Check the API key status at BlockPI dashboard
ErrApikeyIsExpired	Apikey is expired	Check the API key status at BlockPI dashboard
ErrUserBalanceIsNotEnough	Insufficient RU balance	Buy a RU packag

Restrictions for Different Endpoint Types

In order to better serve different types of users and ensure the healthy and efficient operation of BlockPI RPC service network, we have implemented different restrictions on various types of endpoints. If a user triggers any of these restrictions, the system will return an error. The following table outlines these limitations:

Endpoint Type	Restrictions	Error Code
Public	Not support WS/WSS	N/A
Public	Not support Debug_* and Trace_*	-32000
Public	Maximum request rate: 10 qps	429
Public	Maximum response body size: 3 MB	-32000
Public	Maximum block range: 1024	-32602
Public	Maximum batch size: 10	-32000
Private	Maximum block range: 5000 with address input	-32602
Private	Only support “callTracer” and ”prestateTracer” for debug method	-32000
Private HTTPS	Maximum batch size: 1000	-32000
Private WSS	Do not support batch call	-32000
All HTTPS	Do not support subscribe and filter rpc method	-32000