Error codes
What each FuseProxy proxy error means, from 407 NO_USER to 503 NO_RAY, how SOCKS5 reports errors, and how to fix each one.
When the proxy itself rejects or cannot complete a request, it answers with an HTTP status code and an error name, such as 407 TRAFFIC_EXHAUSTED. Errors from the website you are visiting, such as a 404 or a site's own 403, pass through unchanged.
HTTP and HTTPS errors
| Error | What it means | What to do |
|---|---|---|
400 Bad Request | The proxy could not read the request, usually a malformed CONNECT | Check the proxy URL format and that your client supports HTTP proxies |
403 PORT_BLOCKED | The destination port is blocked | Use an open destination port |
403 SITE_PERMANENTLY_BLOCKED | The destination is blocked network-wide, such as government, banking, payment and adult sites | This site cannot be reached through FuseProxy |
403 HOST_BLOCKED | The destination is blocked for your account | Contact support if you think this is a mistake |
407 NO_USER | The username or password is wrong, or the plan no longer exists | Copy the credentials again; check that targeting parameters follow the username after two underscores |
407 TRAFFIC_EXHAUSTED | Your plan has no traffic left | Buy more traffic in the dashboard; your credentials stay the same |
407 THREADS_EXHAUSTED | Too many open connections | Lower concurrency or close idle connections; see the limit below |
407 PORT_NOT_ALLOWED | The sticky port is outside your plan's range | Use a port from your sticky port range |
407 USER_BLOCKED | The account has been suspended | Contact support |
500 INTERNAL_SERVER_ERROR | The gateway hit an unexpected problem | Retry with backoff; contact support if it continues |
502 NO_HOST_CONNECTION | The proxy could not connect to the destination | Check the URL, then retry: the next attempt may use another IP |
503 NO_RAY | No IP matches your targeting right now | Widen the targeting, for example from city to country |
The concurrent connection limit is 2000 per account.
SOCKS5 errors
SOCKS5 has no room for an error name, so problems show up in two ways:
- Authentication is denied when the credentials are wrong, the plan has no traffic left, or the connection limit is reached (
NO_USER,TRAFFIC_EXHAUSTED,THREADS_EXHAUSTED). - The connection is reset after a successful login when the port is blocked, no IP matches your targeting, or the destination is unreachable (
PORT_BLOCKED,NO_RAY,NO_HOST_CONNECTION).
To see the exact error, send the same request over HTTP to the HTTP port. It returns the named error.
Is it the proxy or the website?
| Signal | Likely source |
|---|---|
The status line carries an error name such as NO_RAY | The proxy |
| A normal error page or the site's own message | The website |
403 or 429 from the site after many fast requests | The website is rate limiting you |
When a website rate limits you, slow down: lower concurrency, add delays, retry with exponential backoff, and stop when a site asks you to. A new IP does not make an overloaded site want more requests.