Proxy errors: 407, 403, 502, 503 and timeouts
An error code tells you who refused the request: the proxy or the site. Find the code you see below. Each entry says what it means and what to change.
First: who answered
A 407, 502 or 503 comes from the proxy side: the request never reached the site. A 403 or 429 comes from the site itself, which means the proxy worked and delivered the request.
To check the proxy on its own, open a neutral address through it, for example api.ipify.org. If it returns an IP, the proxy is fine and the problem is with one particular site.
Checking the proxy without the site
curl -x http://login:password@proxy.sotaproxy.com:10000 https://api.ipify.org # residential
curl -x http://login:password@198.51.100.20:50100 https://api.ipify.org # IPv4, ISP407 Proxy Authentication Required
The proxy did not accept the login and password. On static proxies it is almost always a typo or a password copied with a missing character. On residential it also happens when a suffix in the login is malformed, for example a lower-case country code or a space in a city name.
Copy the login and password from the dashboard again instead of typing them. On residential, try the bare login without suffixes first, then add them back one at a time. Also check that your program actually sends the credentials: some tools silently drop a login written inside the address. The 407 page covers each case.
403 or 429 from the site
403 Forbidden means the site received the request and refused it. Many sites block data center addresses, and no number of retries fixes that: use residential or ISP proxies for that site. On residential, sites with an anti-bot check often fail when the address changes on every request, so create a list with Sticky (session) rotation.
429 Too Many Requests means one address is sending too much, too fast. Spread the work over more addresses or ports and add a pause between requests.
502 and 503 on residential
502 Bad Gateway means the network could not find a working exit for your request. A single 502 is normal on residential, so retry once. If it holds for a minute with the same country or city, the pool for that location is empty right now: choose a wider location or another country.
A 503 with the text "Target host denied" means the provider does not allow this site through residential proxies. It is a block-list on the provider side, so retrying or changing the country will not help. Write to support with the site name and we will suggest a proxy type that works for it.
Connection refused or timeout
A "connection refused" right away usually means a wrong port or proxy type. IPv4 and ISP proxies use 50100 for HTTP and 50101 for SOCKS5, residential uses the port shown in the dashboard. Copy the proxy again and check that the type in your program matches the port.
A timeout means no answer came in time. On residential the first request of a session takes longer, so set the timeout in your program to 30 seconds. If nothing connects at all, a firewall, an antivirus or your network may be blocking the proxy port: try another network. For slow work in general, see the page on slow proxies.
"Wrong package key" (403) on a new residential package
Right after a residential purchase the provider still has to switch the package on. Usually that takes up to 5 minutes, sometimes 30 to 40. Until then creating a list can fail with "wrong package key" and code 403. The traffic is already yours, nothing is lost.
The dashboard shows "Your package is still activating", checks again every minute and unlocks list creation as soon as the package is ready. If it still does not work an hour after payment, write to support.