Drıftstack docs
Docs

HTTP proxies can be saved but not used for a session

You might be here because: “HTTP proxies cannot be used for browser sessions” · “my http proxy is greyed out in the picker” · “HTTP can’t carry a chat” · “no SOCKS5 or VPN proxies to test” · “why won’t my proxy launch, it saved fine” · “400 naming supported schemes” · “does driftstack support http proxies” · “https proxy not working”

Short answer

You can save and manage an HTTP proxy, but it cannot carry a session on this deployment. A launch through one is refused: “HTTP proxies cannot be used for browser sessions. Use a SOCKS5, OpenVPN, or WireGuard proxy instead.”. Ask your provider for SOCKS5 access to the same proxy — many offer both on different ports.

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

  1. The proxy’s type is HTTP. Open Proxies → Edit and check the Type. If your provider offers SOCKS5 on another port, change Type to SOCKS5 and the port, then re-enter the password when asked (changing the address requires it).
  2. The picker shows it greyed out with “HTTP can’t carry a chat”. Only a SOCKS5 proxy, or a VPN your plan includes, can carry a chat or session. Choose another, or add a SOCKS5 one.
  3. “Test all” is disabled with “No SOCKS5 or VPN proxies to test. HTTP proxies can’t run a session.” An HTTP row’s only check is that its address can be found (“Check endpoint”); nothing else is tested.
  4. API caller. Passing an http proxy’s id as proxy_id returns 400 naming the supported schemes.

If it still fails

Press Talk to a person in this chat (or open Help) and include the proxy label and its Type as shown in Edit. A person cannot enable HTTP sessions — this is how the deployment works.