Posted on Fri, 24 Oct 2025
We’ve added server-side connection breakup
We’ve just rolled out a small but important reliability update: server-side connection breakup.
When a user clicks Disconnect, the client normally tears down the tunnel. But on unstable networks, that message might never reach the server — leaving “ghost” sessions alive until timeout.
Now, if the client fails to close the link within a short window, our servers will step in and terminate the connection from their side.
How we fixed it
We updated our server architecture so that:
-
When you send the “disconnect” command from your client, the server logs that intent immediately.
-
If the client connection becomes unresponsive or cannot close cleanly within a short grace period, the server forcibly tears down the session from our end.
Why this matters
-
No more lingering sessions. When you say disconnect, it actually disconnects — even over flaky Wi-Fi or mobile links.
-
Cleaner resource handling. Stuck sessions are cleaned up immediately.
-
User experience: You no longer need to double-check or manually intervene when the network hiccups. Press “stop”, and you’re stopped.
-
Future-proofing: Networks will get more heterogeneous (5G, WiFi 6E, satellite, mobile roaming). Ensuring robust disconnect semantics is a step toward better reliability under all circumstances.
This enhancement is part of the ongoing work to tighten up the edge-cases — the ones only triggered when the network does funny things. We hope you’ll notice fewer “ghost” sessions, clean cut-offs when requested, and an overall smoother experience.
Thank you for using the service and for your feedback — it helps us fine-tune features like this for real-world conditions.
Warm regards,
The sshreach.me team