Drıftstack docs
Docs

Proxy connects but cannot reach the internet (egress_blocked)

You might be here because: “proxy connected but could not reach the internet” · “egress blocked” · “the check did not complete, exit location unknown” · “my proxy tests fine but no traffic goes through” · “proxy is green but pages never load” · “check with your proxy provider” · “proxy connects but nothing loads” · “out of proxy bandwidth”

Short answer

Driftstack connected to the proxy and logged in, but the proxy then refused or failed to reach the destination. The message is “The proxy connected but could not reach the internet. Check with your proxy provider.”. The proxy address and password are right; the provider is not routing your traffic.

Check first

  • Are you signed in to the desktop app, and is the app up to date? An old build can be refused for saves and launches — see ‘Please update Driftstack to keep editing’ (old desktop build refused).
  • Is the proxy saved and tested? Open Proxies, find the row, press Test (SOCKS5) or Check VPN (OpenVPN/WireGuard) and read the result.
  • If the app shows it is offline, reconnect and try again — proxy changes and tests need a connection.
  • Is a proxy actually chosen for the profile you are launching? Open the profile’s Edit and look at the Proxy picker.

Likely causes and fixes

  1. Provider-side limit. This is usually the provider’s plan, quota or an access rule: a suspended account, an exhausted bandwidth quota, or a ruleset restricting destinations refuses every request this way. Log in to your provider and check balance, status and allowed destinations.
  2. Looks healthy elsewhere. Anything that only opens the port calls this proxy healthy; only a real request through it shows the problem, which is what Driftstack’s test does. So “it works in my checker” does not contradict this result.
  3. Proxies tab shows “exit location unknown — the check did not complete”. Same fact: the proxy accepted the connection and login, but no traffic made it through. Try the test again.
  4. Is it this proxy or the whole provider? Test a second proxy from a different provider. If that one launches, the fault is the first provider’s.

Nothing on the Driftstack side changes this outcome, and retrying with the same proxy fails the same way until the provider routes again.

If it still fails

Press Talk to a person in this chat (or open Help) and include: the proxy label and host, the provider’s reply about quota/status, and the exact message. Never send the password.