IP-allowlist proxies do not work; use username/password
You might be here because: “my proxy uses IP whitelist not password” · “I allowlisted my IP but sessions fail” · “what IP do I whitelist for Driftstack” · “proxy has no password, works at home, fails here” · “auth failed but there is no password”
Short answer
IP-allowlist access does not work with Driftstack. Profiles run from Driftstack’s servers, not from your IP, so an allowlist that names your address never matches. Ask your provider for username/password credentials and enter those in the proxy’s fields.
Check first
- Signed in and online? Proxies save to your account.
- Read the exact refusal under the form — it names the line or field.
Likely causes and fixes
- Provider set to “IP authentication”. Switch the proxy (or the whole provider account) to “user/pass authentication” in the provider’s dashboard, then put the username and password into Proxies → Edit and re-test.
- You tested from your computer and it was green. That test runs from your machine and cannot tell the difference. The Driftstack side of the test is the one that predicts a session.
- The launch says the proxy rejected the credentials, or could not be reached. From Driftstack’s servers an allowlist proxy can refuse the connection outright or refuse the login; either way the fix is username/password credentials.
- “Can I allowlist Driftstack’s IP instead?” Not supported. There is no published list of addresses to allowlist, so username/password is the supported route.
If it still fails
Press Talk to a person in this chat (or open Help) and include: the proxy label and whether the provider confirms user/pass auth is on. A person cannot change your provider settings for you.