RPC
Common Error Codes
RPC
Common Error Codes
Understanding RPC error messages and their solutions
When interacting with OrbitFlare RPC endpoints, you may encounter the following standard HTTP error codes. This guide helps you understand what these errors mean and how to resolve them.
HTTP Status Codes
| Error Code | Error Message | Description | Solution |
|---|---|---|---|
| 401 | Unauthorized | Invalid API key or authentication token. | - Verify your API key is correct - Check if your API key has the required permissions - Ensure your API key is properly set in the request headers |
| 403 | Forbidden | Access denied due to insufficient permissions or IP restrictions. | - Verify your IP is whitelisted if IP restrictions are enabled - Check if your subscription plan allows the requested operation |
| 429 | Too Many Requests | You’ve exceeded the rate limits for your subscription tier. | - Implement request rate limiting in your application - Consider upgrading to a higher tier with increased limits - Check your current usage in the dashboard |
| 500 | Internal Server Error | An unexpected error occurred on our servers. | - Retry the request after a short delay - If the issue persists, contact our support team |
| 502 | Bad Gateway | Temporary issue with our upstream services. | - Retry the request after a few moments - If persistent, check our status page for any ongoing incidents |
| 503 | Service Unavailable | Service is temporarily unavailable or under maintenance. | - Retry with exponential backoff - Check our status page for maintenance announcements |
| 504 | Gateway Timeout | Request timed out while waiting for a response. | - Check your network connection - Consider reducing the complexity of your request - Try breaking large requests into smaller chunks |
JSON-RPC Errors
| Error Code | Message | Description | Solution |
|---|---|---|---|
| -32700 | Parse error | Invalid JSON received | Check your request format and ensure it’s valid JSON |
| -32600 | Invalid request | JSON is valid but request format is wrong | Verify your request matches the RPC method specification |
| -32601 | Method not found | The requested method doesn’t exist | Check the method name and our API documentation |
| -32602 | Invalid params | Method parameters are invalid | Review the parameters required for the method |
| -32603 | Internal error | Internal JSON-RPC error | Retry the request; if persistent, contact support |
| -32000 | Server error | Generic server-side error | Retry with exponential backoff |
| -32001 | Transaction simulation failed | Transaction failed during simulation | Check transaction parameters and account states |
| -32002 | Account not found | Requested account doesn’t exist | Verify the account address is correct |
| -32003 | Block not found | Requested block not available | Check if the block is within available history |
| -32004 | Node unhealthy | RPC node is not in a healthy state | Try a different RPC endpoint |
Best Practices
-
Implement Retry Logic
- Use exponential backoff for retries
- Set appropriate timeout values
- Handle rate limits gracefully
-
Error Handling
- Always check error responses
- Log error details for debugging
- Implement proper fallback mechanisms
-
Monitoring
- Monitor error rates in your application
- Set up alerts for unusual error patterns
- Track API usage and rate limit consumption
Support
If you encounter persistent issues or need help understanding specific errors, please:
- Check our status page for system status
- Join our Discord community for quick help
- Contact our support team for detailed assistance
For real-time updates on system status and maintenance, follow us on Twitter.