Drıftstack docs
Docs

Proxy works on my computer but ‘fails from Driftstack’

You might be here because: “fails from Driftstack but works here” · “the pill says fails from Driftstack” · “proxy works in my browser but not in the app” · “test is green on my mac but session won’t launch” · “no answer from Driftstack, this Mac is fine” · “why does it say measured from your computer”

Short answer

Your profiles run on Driftstack’s servers, not on your computer. The Proxies tab measures a SOCKS5 proxy from two places — “from this Mac” and from Driftstack — and shows both. A green result from your computer does not predict a session; the Driftstack result does. “fails from Driftstack” outranks a green from here.

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. The proxy is on your own network or admits only your IP. A proxy at localhost, 127.0.0.1, 10.x, 172.16–31.x, 192.168.x, or one that authorises by IP allowlist, tests green here and is dead from Driftstack. Use a public address and username/password credentials.
  2. The Driftstack side reads “no answer”. Hover it: “Driftstack could not use this proxy:” followed by the reason. Fix that reason (unreachable, credentials, egress blocked) — see the related docs.
  3. The Driftstack side reads “busy”. Nothing was measured from there yet — Driftstack was busy. Test again shortly.
  4. The notice says “Checked from Driftstack’s server, not the network your profiles run on”. The check ran from a fallback place; test again to check from where profiles run.
  5. A live session reported “Driftstack could not connect through this proxy.”. Treat it like “fails from Driftstack” and re-test.

If it still fails

Press Talk to a person in this chat (or open Help) and include: the proxy label, what the two sides of the latency cell say, and the hover text of the Driftstack side. Never send the password.