Proxy Troubleshooting by Error Code and Symptom

A failed proxy request stops in one of three places: your own client, the proxy, or the website. Find out where before you change anything. Each needs a different fix, and blind retries send more traffic without changing the answer.

By Proxies.sx Team. Reviewed .

Proxy error and troubleshooting guides

Each guide starts from what your client printed and ends with the change to make.

Start from what your client printed

What you seeUsually produced byRead next
407, or a body starting E_AUTH_, E_BALANCE_EXHAUSTED or E_CAP_EXCEEDEDThe gateway407 codes and the authentication guide
429 with an E_ code in the bodyThe gatewayAccount limits
429 after the page loaded, often with Retry-AfterThe websiteRetry-After and bounded retries
502, 503, 504 or a status from 590 to 599Either sideProxy 502 Bad Gateway
net::ERR_TUNNEL_CONNECTION_FAILED in Chrome, Playwright or PuppeteerThe gateway, hidden by the browserRead the proxy's error
E_NO_STOCK_COUNTRY, or traffic leaving from the wrong countryYour username and current stockUsername format
The exit IP changed inside a sticky sessionSession settings or the device's networkSticky proxy IP changes
E_WRONG_PORT, ECONNREFUSED, or a timeout before any responseYour client settings or networkConnection issues
Certificate errors on HTTPS pagesYour client or a local intercepting proxyKeep TLS verification on
DNS or WebRTC leak resultsYour clientDNS leak test and SOCKS5 vs SOCKS5h
Slow pages or low throughputThe route or the workloadSpeed issues
A browser or app will not accept the proxyThe app's proxy settingsSetup guides by device and browser

Find which side refused

Your client produced the error when there is no HTTP response at all. ECONNREFUSED, ENOTFOUND for the proxy host, or a timeout before anything comes back mean the request never reached a working proxy. Check the host gw.proxies.sx, the port and your outbound firewall.

Our gateway produced it when the response body starts with an E_ code and ends with (req: …). For an HTTPS URL, the gateway answers the CONNECT request before the TLS handshake starts. Browsers hide that answer and curl prints only its status, so the guides above show how to read the body.

The website produced it when the status arrives after the TLS handshake. By then the gateway is forwarding encrypted bytes and cannot add a status line of its own. curl shows the difference in one line of output.

curl -sS -o /dev/null --max-time 30 -x http://gw.proxies.sx:7000 \
  -U 'psx_ab12cd-peer-us:YOUR_PROXY_PASSWORD' \
  -w 'connect=%{http_connect} code=%{http_code}\n' https://example.com/

# connect=407 code=000  -> the gateway refused your credentials
# connect=502 code=000  -> the gateway found no usable endpoint
# connect=200 code=403  -> the tunnel worked; the website answered 403

Three checks before anything else

Start with the password. The gateway accepts the proxy password shown in your dashboard or a pak_ access key. It never falls back to your dashboard login password, and an account without a proxy password gets E_AUTH_INVALID until one is generated.

Next, check stock for the country in your username. The public stock endpoint returns endpoint counts per pool and country, with the time it generated them. A device count is not a count of distinct exit addresses.

curl -s https://api.proxies.sx/v1/gateway/pool/stock \
  | jq '{peer: .pools.peer.us, mobile: .pools.mbl.us, generatedAt, stale}'

Finally, keep the request id. Copy the (req: …) value from the failed response, with the UTC time, before you change anything. It lets support find the exact refusal in our logs.

Tools for a second observation

The proxy tester runs a request with the details you enter. The username builder shows the tokens the gateway reads, and the format converter rewrites credentials for tools that want a URL or a list. To see whether an address changes over time, sample it with the rotation checker. Once requests work, the bandwidth calculator estimates the traffic a job needs.

The Pool Gateway page describes the product these guides cover, and the Pool Gateway documentation lists the connection details. Proxy settings for Python, Node.js and Docker are in the client configuration guides.