Skip to main content
Error codes differ by product. Residential and Mobile have a richer set of plan-limit and targeting errors; Datacenter has a tighter set focused on authentication and upstream failures plus SOCKS5 reply codes.

Residential & Mobile

Authentication & request errors

standard
Your HTTP request is malformed. Check your proxy client is sending a valid HTTP CONNECT or request line.
standard
Username or password is wrong, or your targeting modifiers contain an unrecognised value.Body: Incorrect username or password
standard
Your client sent an Expect: header the proxy can’t satisfy. Remove it or switch libraries.

Plan limit errors

custom
You’ve used all the bandwidth on your plan. Top up or upgrade from the dashboard.Body: exceeded bandwidth limit
custom
You’re making more concurrent connections than your plan allows. Lower concurrency or upgrade.Body: exceeded threads limit

Targeting errors

custom
The country-<code> modifier isn’t a recognised country. Use lowercase ISO 3166-1 alpha-2 codes (e.g. us, de, jp).Body: invalid country code
custom
The state-<code> value isn’t recognised for the country (residential only). Use the standard regional subdivision code.Body: invalid state code
custom
The city-<n> value isn’t recognised, or no IPs are available (residential only). City names should be lowercase and concatenated (westlakevillage).Body: invalid city code
custom
The asn-<number> value isn’t in the supported set, or no IPs are available for the combined geo + ASN targeting. Verify the ASN with whois or bgp.he.net.Body: invalid asn
custom
The ttl-<minutes> value is outside the allowed range. TTL must be a positive integer within the supported lifetime range.Body: invalid ttl

Upstream errors

standard
The target site couldn’t be reached. DNS failure, target-side refusal, or a transient network issue. Retry with backoff.
standard
An unexpected error occurred. If you see this repeatedly, reach out via the dashboard with a timestamp.
standard
A transient internal error. Retry with backoff — if it persists, contact support.

Residential & Mobile summary

Mobile only accepts country- and asn- targeting, so 454 invalid state/city code won’t apply to mobile.

Datacenter (HTTP)

standard
Malformed authentication — typically a bad Base64-encoded Proxy-Authorization header. Your client is sending credentials in the wrong format. Regenerate or re-encode.
standard
Missing, invalid, expired, or capped credentials. Common causes: wrong username/password, expired session credentials, plan bandwidth or thread limit reached, account suspended.
standard
Server-side error after authentication succeeded. Inspect the X-Server-Error response header for a more specific reason.

Datacenter HTTP summary

Datacenter (SOCKS5)

SOCKS5 replies use single-byte reply codes. Most libraries surface these as descriptive errors automatically.

Handling errors in code

Still stuck?

Best support is through the dashboard — fastest response time. You can also reach us on Discord, Telegram, or by email at admin@proxies.fo. Include a request timestamp and the full response when reporting an issue.