When a request through your proxies fails, the reason is shown on the Errors page under Stats in your dashboard, with a "How to fix?" hint for each error. Some errors point to something you need to change. Others happen now and then on any proxy network and only matter if they keep coming back.
Errors that need a change in your setup or plan
These usually repeat on every request until the cause is fixed.
no_proxies_allocated (407): you're connecting to a proxy that is no longer on your proxy list, usually after a replacement, refresh or plan change. Download your current list, or use the Backbone Connection or Rotating Proxy Endpoint so your setup keeps working when the list changes.
client_connect_high_concurrency (429): too many connections are open at once. Connections that stay open (slow websites, keep-alive) count until they close. Close connections you no longer need, or add the High Concurrency feature on the Plans & Pricing page. See What is Concurrency?.
target_connect_resolve_failed (502): the website's hostname doesn't exist. Check the address for typos and make sure it opens without a proxy.
client_connect_unsupported_socks5_command (400): your program sent a SOCKS5 request the proxies don't support, usually UDP. Webshare supports TCP only (HTTP and SOCKS5).
client_connect_invalid_ip (403): you're connecting to a private address, such as localhost or 10.x.x.x, through the proxy. Exclude local and private addresses from your proxy settings.
client_connect_forbidden_host (403): the website is blocked on Webshare for this proxy type and can't be unblocked for one account. More sites are restricted on Rotating Residential; see Restricted Websites on Our Rotating Residential Proxy Network. On Proxy Server and Static Residential plans, the most common cause is proxy chaining: connecting to another proxy through your Webshare proxy. client_connect_forbidden_host_sni is the same block when you connect to the website by IP address; the Errors page may then show a different name (such as cloudfront.net) or "Unknown error".
client_connect_forbidden_port (403): the website's port is blocked (25, 110, 465 and 587). This is the website's port, not the proxy port.
Proxy Authentication Required (407): the proxy couldn't confirm it's you. Usually a typo in the username or password, credentials saved before you changed them, special characters changed by copy-paste, or an IP address that isn't authorized.
Payment Required (402) and client_connect_out_of_bandwidth (402): the plan can't be used right now. Check for a failed auto-renewal, bandwidth used up on the plan you're connecting to (each plan and sub-user has its own limit), an unverified email address, or an account under verification.
client_connect_auth_revoked: a long-running connection was closed because it was no longer authorized, for example the proxy was removed from your list, the bandwidth ran out, or the plan was cancelled.
client_connect_invalid_params (400): Rotating Residential only. Your username contains parameters that can't be read, such as two session IDs or two cities. Copy the format from the Endpoint Generator.
no_available_proxies (422): Rotating Residential only. No proxies are available for the location in your username. Check that the username doesn't contain an extra part that reads as a country code, or try another location.
Errors that are normal in small numbers
Websites are sometimes slow, connections drop and networks have short interruptions, so a few of these errors are expected. Act on them only if they make up a noticeable share of your requests, or keep happening on the same proxies or the same website.
target_connect_timeout (502) and target_read_timeout (502): the website was too slow to accept the connection or to respond. If it keeps happening, replace the affected proxies or turn on the Auto-Replace rule "Proxy may be experiencing a temporary slowdown".
target_connect_refused (502): the website rejected the connection. If it keeps happening for one website, it may be refusing those proxy IPs: check the address, then replace the affected proxies.
target_read_idle_timeout and target_read_deadline: a connection was closed because it sent no data for 15 minutes, or stayed open for 8 hours (the defaults). This often happens to connections your program keeps open between requests. If you need longer connections, raise the Proxy Idle Timeout (up to 2 hours) or the Proxy Session Timeout (up to 168 hours) in Proxy Settings.
client_read_eof (502), client_read_timeout (400) and target_read_eof (502): the connection was closed before the request finished, usually by your own program. If it happens often, increase the timeout in your program.
target_connect_no_route (502): a temporary connection problem. Try again; if it keeps happening with the same proxies, replace them.
target_connect_unknown_error (502): the proxy couldn't reach the website, and the exact reason isn't known. It's a common error on Rotating Residential. Retry once, start a new session after a failure, or try another country.
internal_error_backbone_connect (502): the Backbone Connection couldn't reach the proxy. If it keeps happening, try the same proxy with the Direct Connection and turn on the Auto-Replace rule "Proxy is not available for more than 15 minutes".
Other errors starting with internal_error, target_http_invalid (502) and target_read_not_tls (502): a problem on Webshare's side. These usually clear when you retry. If one continues for 24 hours, contact [email protected].
Errors your browser shows
ERR_PROXY_CONNECTION_FAILED or "The proxy server is refusing connections": the browser couldn't reach the proxy. Check the proxy address, port and connection method; a firewall, VPN or antivirus can also block it.
ERR_TUNNEL_CONNECTION_FAILED: the browser reached the proxy, but the connection was refused. Check the Errors page for the reason.
ERR_TIMED_OUT or ERR_CONNECTION_TIMED_OUT: no answer in time. Check the Errors page for the reason.
The browser keeps asking for a proxy login: see Proxy Authentication Required (407) above.
If your error isn't listed or the fix doesn't help, contact us at [email protected].