Drıftstack docs
Docs

‘The part of this session’s connection that we run did not start / stopped’

You might be here because: “Connection could not start on our side” · “Connection dropped on our side” · “Tunnel could not be started” · “This one is ours, not yours” · “session died and it says it’s not my fault” · “is something wrong with my proxy”

Short answer

A part of the session’s network path that we operate failed — before the session ran, or while it was running. Nothing is wrong at your end, and your proxy was not the cause. Launch a new session; that usually clears it.

Check first

  • Read the recap wording exactly — it says whose side the problem is on.
  • Do not change your proxy or profile in response to these messages; they name our side.
  • Simply launch again first.

Likely causes and fixes

  1. “Connection could not start on our side — The part of this session’s connection that we run did not start, so the session never ran. Nothing is wrong at your end, and a new session usually clears it.”. Launch again.

  2. “Connection dropped on our side — The part of this session’s connection that we run stopped while it was running, so the session was ended.”. Launch again; anything unsaved in the page is lost, but a profile’s cookies were saved at close.

  3. “Tunnel could not be started — The VPN software did not start on our side, so nothing was attempted. This one is ours, not yours.”. Launch again.

  4. “Tunnel did not finish connecting — The proxy endpoint answered and the handshake completed, but our side did not finish bringing the session up in time. This one is ours, not yours.”. Launch again.

Other “Tunnel did not finish connecting” variants point at your proxy’s address or config — see the proxy docs for those.

If it still fails

Rule of thumb: if it fails again and again within a few minutes, that points at a service-side problem — press Talk to a person in this chat (or open Help) and include the session ids and the exact recap sentence. No account action is needed.