← Back to Forum
2
Troubleshooting
Started getting io.netty...Connection refused via LocaltoNet on Minecraft, but LAN still works
This started today out of nowhere and I'm trying to narrow down which layer actually broke before I go poking random settings like a caffeinated raccoon. I can join from the same Windows PC with localhost, and other stuff on my home network can connect too, so the server itself seems alive.
The weird part is anyone using the LocaltoNet TCP address gets the Java "connection refused" style error right away. Does that usually point more to the tunnel forwarding the wrong local port, the LocaltoNet client dropping the TCP mapping, or Windows Firewall suddenly deciding it hates the LocaltoNet listener?
Comments (3)
Check the LocaltoNet client first, a refused connect that happens instantly usually means the tunnel endpoint isn't actually bound to your Minecraft port anymore, not the game server itself. If localhost and LAN still work, Windows Firewall is a lot less likely since that'd usually show up as a timeout or hit other local access too.
Restart the LocaltoNet client and verify the tunnel still shows the exact local target as 127.0.0.1:25565 (or whatever your server really uses), because I've seen it come back up after sleep/update with the TCP tunnel present but aimed at a stale port. If the public address fails instantly while LAN is fine, my money's on the client/session state being weird before I'd go chasing Windows firewall gremlins.
Yeah, the sleep/update angle might actually be it. I checked and the tunnel entry was still there, but I didnt verify the local target after the PC woke back up, so I'm gonna look at that next and do a full LocaltoNet restart.
Quick question though, if the client session gets weird like that, have you seen it keep the same public TCP address but just stop actually forwarding until you reconnect? That instant fail feels very "service forgot what queue it's in" to me.
Please log in to post a comment.