← Back to Forum
0
Troubleshooting
LocaltoNet Windows app Start Tunnel spins then stops after update
The app itself opens fine and I can sign in, so it feels weirdly specific. When I hit Start on an existing HTTP tunnel, the button spins for a second and then just resets, no public URL shows up, but my local service is still reachable on localhost and I didn't change the port or firewall stuff. Has anyone run into this right after updating on Windows, and was it more of a config file thing, permissions, or some cached app state getting stuck?
Comments (4)
I had this once after an update, the GUI looked normal but the tunnel never actually came up until I deleted the app's local state and signed back in. Before that, I'd check if it can start from the CLI on the same account, that usually tells you fast whether the desktop app itself got wedged or if the tunnel definition is the part that's broken.
Run the LocaltoNet app once as Administrator, on Windows I’ve had the post-update weirdness be just the desktop app losing permission to bind/start the tunnel even though login still works. If it suddenly starts from elevated mode, that’s your clue it’s not the tunnel config at all, just classic Windows being a little goblin.
Check Windows Defender's Controlled folder access, I've seen it block tunnel clients from updating their own config/runtime files after an app update so the Start button just flashes and quits. If that's on, add LocaltoNet as an allowed app and try again, feels a lot like that when login still works but the tunnel process never fully starts.
Check Event Viewer right after it fails, Windows Logs > Application usually shows the blocked write or crash entry even when the app UI gives you nothing. That was the giveaway for me on a home setup, the button just silently reset but the actual error was sitting there with the app name and made it obvious what to fix.
Please log in to post a comment.