Getting Started
Error handling
When using the Geonode Proxy API, you may encounter various HTTP status codes. Understanding these codes helps you handle errors gracefully and implement robust error handling in your applications.
HTTP Status Codes
| Status Code | Description | Expanded Description |
|---|---|---|
| 403 | Invalid request configuration. . | This error occurs when the request contains invalid or improperly formatted parameters. The placeholder will include details about which field caused the issue. Common causes include incorrect formatting or unsupported values for fields like country, city, state, or ISP. Please verify that all parameters follow the expected structure and use values listed in the API documentation or supported geo-targeting options. |
| 407 | Authentication error. Please check your authentication settings. | This error indicates that authentication with the proxy server failed. Authentication is required, but the credentials provided were missing, invalid, or insufficient. Common causes include incorrect or missing proxy username/password, misconfigured authentication headers, or using an IP address that hasn’t been whitelisted. Please verify that your credentials are correct and that your IP address is authorized to access the proxy if applicable. Refer to the authentication section of the API documentation for setup instructions and troubleshooting tips. |
| 411 | Your account has been blocked. If you think it is a mistake, please contact customer support. | This error means that the user’s account has been manually blocked by the system or an administrator. This action is typically taken due to violations of the terms of service, suspicious activity, billing issues, or abuse prevention measures. If you believe this is an error, please contact customer support to review your account status and resolve the issue. |
| 464 | Connection to the specified target is not permitted due to security policies. | This error occurs when the requested connection to a specific host, IP address, or port is blocked due to security or access control policies. Common reasons include attempting to connect to restricted destinations, using unsupported ports, or using protocols that are not allowed (e.g., FTP or SMTP). Ensure that the target address, port, and protocol are supported and comply with the platform’s usage policies. If you’re unsure or believe the restriction is incorrect, please contact support for clarification. |
| 465 | No proxies available in the selected location. Please choose a different targeting configuration or try again later. | This error indicates that the proxy server was unable to find any available IP addresses that meet the specific geo-targeting requirements (e.g., country, city, ISP) specified in the request. This can occur when demand exceeds supply in a particular region or when targeting criteria are too narrow. To resolve this issue, try adjusting your targeting configuration to be less restrictive or retry your request later. If consistent access to specific regions is critical, please contact support to explore custom proxy allocations or availability options. |
| 466 | You’ve reached your bandwidth limit. Buy more data or upgrade your plan to continue. | This error indicates that the user has consumed all of the bandwidth allocated in their current plan. When the bandwidth limit is reached, no further requests can be processed until more data is added. To resume usage, you can upgrade your plan or purchase an add-on directly in the user dashboard. |
| 467 | You have reached your session bandwidth limit. | Specified bandwidth limit for this session has been reached. Limit is defined by -limit- parameter of the first session request and can not be changed until session is expired or released. |
| 500 | Internal error. Please try again. | This error indicates that something went wrong on the server while processing the request. It is not caused by user input or configuration. Please try again. If the issue persists, contact support with your request details so we can investigate. |
| 517 | Internal error. Please try again. | This error indicates that something went wrong on the server while processing the request. It is not caused by user input or configuration. Please try again. If the issue persists, contact support with your request details so we can investigate. |
| 518 | Internal error. Please try again. | This error indicates that something went wrong on the server while processing the request. It is not caused by user input or configuration. Please try again. If the issue persists, contact support with your request details so we can investigate. |
| 560 | Internal error. Please try again. | This error indicates that something went wrong on the server while processing the request. It is not caused by user input or configuration. Please try again. If the issue persists, contact support with your request details so we can investigate. |
| 561 | Internal error. Please try again. | This error indicates that something went wrong on the server while processing the request. It is not caused by user input or configuration. Please try again. If the issue persists, contact support with your request details so we can investigate. |
| 562 | Internal error. Please try again. | This error indicates that something went wrong on the server while processing the request. It is not caused by user input or configuration. Please try again. If the issue persists, contact support with your request details so we can investigate. |
| 563 | Internal error. Please try again. | This error indicates that something went wrong on the server while processing the request. It is not caused by user input or configuration. Please try again. If the issue persists, contact support with your request details so we can investigate. |
| 564 | Internal error. Please try again. | This error indicates that something went wrong on the server while processing the request. It is not caused by user input or configuration. Please try again. If the issue persists, contact support with your request details so we can investigate. |
| 565 | Internal error. Please try again. | This error indicates that something went wrong on the server while processing the request. It is not caused by user input or configuration. Please try again. If the issue persists, contact support with your request details so we can investigate. |
| 566 | Internal error. Please try again. | This error indicates that something went wrong on the server while processing the request. It is not caused by user input or configuration. Please try again. If the issue persists, contact support with your request details so we can investigate. |
| 567 | Internal error. Please try again. | This error indicates that something went wrong on the server while processing the request. It is not caused by user input or configuration. Please try again. If the issue persists, contact support with your request details so we can investigate. |
| 569 | Internal error. Please try again. | This error indicates that something went wrong on the server while processing the request. It is not caused by user input or configuration. Please try again. If the issue persists, contact support with your request details so we can investigate. |
Best Practices
-
Always Implement Error Handling
- Never assume requests will succeed
- Handle both expected and unexpected errors
-
Use Retry Logic
- Implement exponential backoff for 5xx errors
- Respect rate limits and Retry-After headers
-
Log Errors Appropriately
- Include relevant request details
- Don’t log sensitive information
-
User Feedback
- Provide clear error messages to end users
- Include actionable steps for resolution
Support
If you encounter persistent errors or need assistance, contact our support team at Support.