Diese Seite gibt es noch nicht in Ihrer Sprache. Sie lesen den englischen Text.
Knowledge base
The tunnel broke and could not be raised again. Pages will not load
Pages stop and that is the point
The local port died together with the tunnel, so every request from that window is turned away. Nothing left through the address of this computer.
A browser that quietly switched to a direct connection would look identical to you and completely different to the site.
A dead window is the safe outcome
Three attempts on the same port
The app reconnects on the port the browser already knows, because a window that is already running would never learn a new one.
It tries three times with a growing pause between them. Endless retries would burn the connection limit at your server and hide the problem.
The server ended the session
An idle timeout, a reboot, a full connection table or an automatic block against repeated logins closes the session from the other end.
The first reconnect then arrives at a server that is turning everything away for a while.
Your own network moved
A laptop that changed network or woke from sleep loses every open connection at once. All three attempts can fall inside the gap before the new network is ready.
Start the profile again
When the server answers again, launch the profile: a fresh launch raises a fresh tunnel and takes a fresh local port.
The check button on the proxy entry tells you whether the server is back before you spend a launch on it.
Collecting the evidence
Note the exact minute the window went dead and press Check on the proxy entry right away: the answer separates your server from your network.
Write from the Support screen. The report that travels with the message carries the last notifications, and this line is one of them.
What this article does not cover
- A tunnel that never came up at all. That refusal happens at launch and carries a different line.
- Pages that load slowly. A live tunnel to a distant server is not this.
- Sessions lost inside a site. Cookies on disk are not touched when a tunnel dies.
Where this is decided
Each claim above is one place in the code and one stand.
- Three reconnect attempts run and the third failure reaches the person
- apps/desktop/test/выход-по-ssh.js
- A note that promises to tell the person is backed by a road that reaches them
- apps/desktop/test/обещание-сказать-человеку-держится.js
- A profile with an exit it cannot use is never opened directly
- apps/desktop/test/proxy-covers-https.js
- A refusal carries its reason rather than dropping quietly
- apps/web/test/отказ-не-молчит.js
Questions
- Did the profile go online directly while it was down?
- No. The port the browser was told to use simply stopped answering, so requests failed instead of leaving another way.
- Why three attempts and not more?
- Because endless attempts eat the connection limit at your server and leave you staring at a dead browser with no explanation.
- Do I hear about a successful reconnect?
- Yes. A separate line says the tunnel came back on the same port and the profile keeps working.
Still stuck
Support reads the report that travels with your message and answers with the cause, not with a checklist.