← Back to Forum
0
Getting Started
Urgent Issue: Tunnel Disconnects in Localtonet v7.0–7.2
Dear Localtonet Support Team,
Since upgrading to Localtonet v7.0–7.2, we face a major issue:
The tunnel and token disconnect as soon as the UI window is closed.
This did not happen in v6.x, where tunnels stayed active after UI closure or reboot.
We run Localtonet as a Windows Service via nssm, but the issue persists.
Impact:
Shared workstations make it impractical to keep the UI open.
Frequent disconnections interrupt client operations and reduce reliability.
Request:
Investigate and fix this regression.
Allow Localtonet to run in the background without UI dependency.
Ensure tunnels/tokens remain stable after reboot or UI closure.
Provide an expected timeline for resolution.
This issue is critical for our operations and needs urgent attention.
Comments (3)
same f* problem. Where is the support?
Hello,
The Localtonet application and tunnels need to remain open for it to connect and stay connected. Closing the application interface will stop the application and, naturally, disconnect you. You can minimize it, but closing it will disconnect the application. This was the case in previous versions as well. If you need to start Localtonet as a background service every time your computer starts, you can do this with NSSM. Versions v7.1 and v7.2 successfully passed tests with NSSM to start it as a background service. We can test this if you share AnyDesk(from Mail) with one of the devices you're experiencing the issue with.
In v7.3, you can run it as a service, which is the preferred method. how to use as a service
Please log in to post a comment.