HTTP status codes
Code | Message | Solution |
400 | Bad Request | Your request 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 incorrect. See docs. |
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. |
429 | Too Many Requests |
You hit the default node HTTP connections limit. You hit one of our limits, please read our documentation on limits. |
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 | |
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. Also, 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. |
JSON-RPC error 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. |
-32000 | Server error | The implementation-defined error on the server. This is basically the node implementation telling you why it cannot process the request. For example, see EIP-1474. |
If you still have questions or issues, feel free to reach out to our Support team by emailing support@chainstack.com or submitting this form.
Comments
0 comments
Article is closed for comments.