Chainstack plans to deprecate Trader Nodes on December 1, 2026. We recommend moving your workloads to Global Nodes before then, as described in Trader Node deprecation.
HTTP status codes
| Code | Message | Solution |
|---|---|---|
| 400 | Bad Request | Your request is invalid. Make sure your request is properly formatted and this is a valid request. |
| 401 | Authorization Required | The credentials you provide to access your node endpoint are absent or incorrect. See how to know your node credentials. |
| 404 | Not Found | Contact support to check if you are accessing the correct node and if the node is healthy. |
| 404 | DEPTH_ZERO_SELF_SIGNED_CERT | Contact support to check if the gateway is healthy. |
| 413 | Request Entity Too Large | The default limit of the request body size is 1 MB. Reduce the request body size. |
| 429 | Too Many Requests | You hit the default node HTTP connections limit. Reduce the number of requests. |
| 429 | You’ve exceeded the RPS limit available on the current plan | You hit the rate limit on your plan. Reduce the request rate or upgrade to a higher plan. See also RPS plan limits. |
| 429 | You’ve reached your monthly quota of Request Units (RUs) | You exhausted the monthly RU quota on your plan. Enable extra usage to continue beyond the quota or upgrade for more RUs. See also Quotas. |
| 499 | No Response From Node | Increase the client-side time-out. Contact support if the issue persists. |
| 500 | Internal Server Error | Contact support to check if you are accessing the correct node and if the gateway is healthy. |
| 500 | ECONNREFUSED | Contact support. |
| 502 | Bad Gateway | Contact support to check if your node is experiencing resource constraints or if the node is healthy. |
| 503 | Service Temporarily Unavailable | Contact support to check if your node is experiencing resource constraints. |
| 504 | Gateway Time-Out | Contact support to check if your node is experiencing resource constraints. Or consider getting a dedicated gateway. |
WebSocket status codes
| Code | Message | Solution |
|---|---|---|
| 1006 | Socket Error: read ECONNRESET | Implement a reconnect in your code or get a dedicated gateway. |
| 1009 | MESSAGE_TOO_BIG | The incoming WebSocket message exceeded the maximum allowed size. Increase or disable max_size in your WebSocket client configuration. |
JSON-RPC status codes
| Code | Message | Solution |
|---|---|---|
| -32700 | Parse Error | Your JSON cannot be parsed on the server side. Make sure your JSON is properly formatted. |
| -32600 | Invalid Request | Your JSON-RPC request is not properly formed. See node API reference. |
| -32601 | Method Not Found | The method you are trying to call is not available on the node. See also API namespaces. |
| -32602 | Invalid Params | Your request has invalid parameters. See node API reference. |
| -32603 | Internal Error | A JSON-RPC error that means your request cannot be processed and usually has a -32000 error with details on why the request cannot be processed. |
| -32005 | Rate Limit Exceeded | You exceeded the RPS limit or monthly RU quota on your plan. The message field contains details on which limit was hit. The response may include a data.try_again_in field indicating when to retry. See RPS plan limits and Quotas. |
| -32000 | Server Error | The implementation-defined error on the server. The node implementation shows why it cannot process the request. For example, see EIP-1474. |