← Back to Forum
0
Troubleshooting

Minecraft Java server via LocaltoNet timing out for remote players

Posted by willowp • July 21, 2026

This only started today and I haven't knowingly changed anything, so I'm trying not to poke random settings and make it worse. I can start the server normally and join from the same PC with localhost, and LocaltoNet doesn't show disconnected, but anyone connecting from outside just sits on "connecting" and eventually times out.

Before I start guessing, where would you check first on the local side? Bind address in server.properties, Windows firewall, whether the server is still actually listening on the same port, or something else I'm missing?

Comments (6)

TheKathleen Jul 21, 2026

I'd check what address Java is actually listening on before touching anything else, because if it somehow ended up on 127.0.0.1 only, the tunnel can look perfectly happy while outside clients get nowhere. netstat -ano | findstr 25565 is the boring but useful test here, you want 0.0.0.0:25565 or your LAN IP, not just localhost.

jacobmartinez Jul 21, 2026

Check Windows Defender Firewall first, especially if Java just updated, because that'll silently leave localhost working while the tunnel still looks fine and outside connections die. I've had it flip from an allowed rule for the old javaw.exe to effectively blocked after an update, so I’d verify the inbound rule still points at the current Java binary before changing Minecraft settings.

rebeccad Jul 21, 2026

Yep, I'd look at that rule closely, and also make sure it's the network profile you actually use at home. I've been burned by Windows allowing Java on Private but not Public, and after some update it decided my own network was Public for no good reason, kids couldn't join until I flipped that back.

Victoriae Jul 21, 2026

Yeah, the network profile thing is sneaky. I’d also compare the tunnel’s target on the LocaltoNet side with whatever port the server is actually opening right now, I’ve had a modpack/server wrapper quietly switch from 25565 to another port and everything looked "up" until I noticed the mismatch.

Robert Jul 21, 2026

Check if the server software itself changed the query/listen port in its own config or startup script, not just the main server.properties, because some wrappers and panels override it and you never notice till outside users hang. I've had that happen after an update and LocaltoNet was still "fine" the whole time, just pointing at the wrong local port.

Tyler Jul 21, 2026

Yeah, wrappers love doing "helpful" stuff behind your back. I'd also check whether Java is actually bound to IPv4 only or IPv6 only now, because a tunnel targeting one while the server grabbed the other can waste an afternoon for absolutely no reward.

×