Understanding Response Codes for Residential Proxies

When using our residential proxies, you may encounter various response codes that indicate different issues or errors. Here is a list of common response codes and their meanings:

407 Authentication error

Please check your authentication settings. You can authenticate either by IP white listing or by username + password.

466 Too Many Requests

You have surpassed your concurrent requests limit or bandwidth limit. To avoid this error, you can use fewer concurrent requests or bandwidth or upgrade your plan to get more concurrent requests or bandwidth.

461 Port Limit Reached

You are already using the maximum number of sticky ports assigned to your account. To avoid this error, you can use fewer ports or upgrade your plan to allow for more concurrent requests.

465 Port Not Allowed

You are trying to connect to a port that is not intended to be connected to. This commonly occurs when you are incorrectly trying to connect to SMTP, IMAP, or POP.

464 Host Not Allowed

You are not allowed to connect to the hostname, domain, or IP address. We keep a record of blacklisted hosts in our database.

460 Geo Not Enabled

You have not subscribed to the relevant plan and are trying to use geo-features. To avoid this error, you will need to upgrade your plan.

463 Malformed Request

You have sent unexpected parameters in your request. To avoid this error, make sure that your request is formatted correctly.

561 Proxy Unreachable

The exit node is not reachable. If this happens, you will need to retry the request.

560 Geo Location Not Found

There are no available exit nodes for your request. A common issue is using the incorrect country code in your request. If you have checked and the country code is correct, you can try removing the geo-targeting parameters or trying again later.

562 Proxy Not Found

We are unable to find an exit node for the request. To overcome this error, you can try removing your location targeting from the request.

564 Proxy Not Online

The proxy assigned to your session is no longer active. To avoid this error, you can try refreshing your sticky sessions and trying again.

We hope this information helps you understand the various response codes that may be encountered when using our services.