← Back to Forum
0
Troubleshooting
Tunnel shows online in LocaltoNet but Minecraft gets connection refused
This broke sometime this morning for no obvious reason, which is always a fun feature. The tunnel still says online, the server is running on my PC, and I can join it locally with 127.0.0.1, but anyone coming in through the public LocaltoNet address just gets connection refused.
Before I start randomly poking at things, what are the LocaltoNet specific checks you'd do first? I'm mainly thinking tunnel type being wrong (TCP vs HTTP), target host/port, or whether the Minecraft server is only listening on localhost instead of the LAN address.
Comments (2)
I'd also check whether LocaltoNet reassigned you a different public port or endpoint after a reconnect, I've had that happen and everyone was still trying the old address. If the tunnel looks fine on their side, try hitting your PC's LAN IP from another device on your network too, that usually tells you pretty quickly if it's just bound too tightly or if Windows firewall started being "helpful" overnight.
Yeah, testing from a second device on the LAN is the clean split point here. If that works, the next LocaltoNet-specific thing I'd verify is the tunnel target in the dashboard, specifically that it's forwarding raw TCP to the exact Minecraft port and not an old service profile, I've seen those settings persist after an app restart and look "online" while pointing nowhere useful.
Please log in to post a comment.