Error Codes › Connection timed out: no further information

Connection timed out: no further information

JOIN-001 · Connection timed out

Friends get 'Connection timed out: no further information' when they try to join your Minecraft server. The usual causes (port forwarding, firewall, wrong IP, CGNAT) and how to tell which one it is.

What it looks like in the log

Failed to connect to the server
io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection timed out: no further information: /203.0.113.7:25565

What it means

The player's game sent a connection request and heard nothing back at all. Nobody refused it; it simply never arrived, or the answer never made it home. That points at something between the player and your server dropping the traffic, not at Minecraft itself: a router with no forwarded port, a firewall, the wrong address, or an ISP that never gives your home a public address.

If the message says "Connection refused" instead, that is a different problem; see Connection refused: no further information.

How to find which one it is

Is the server actually running? Join it yourself first, from the same PC, with the address localhost. If that fails, nothing on this page applies yet; fix the server first.
Which address are they typing? Friends on your Wi-Fi use your local address (like 192.168.1.42). Anyone elsewhere needs your public IP, or a name that points at it. Your local address never works from outside, and your public address often does not work from inside your own house, so test with a friend or a phone on mobile data, not with your own PC.
Is the port forwarded? Your router drops unsolicited traffic unless you tell it to pass port 25565 (or your server-port) to this PC. In Coalstack, open the server's Port Forwarding tab to ask your router to do it over uPnP; otherwise follow the port forwarding guide. Forward TCP, to the PC's local address, and give that PC a fixed local address in your router so the rule doesn't go stale.
Is the firewall letting Java in? On Windows, allow java.exe and javaw.exe on both Private and Public networks. Coalstack's uPnP tool adds a firewall rule for you.
Does your home even have a public address? Compare the WAN or Internet address shown in your router's status page with the address a "what is my IP" website reports. If they differ, or the router's address starts with 100.64 to 100.127 or is a private address, your provider is sharing one public address between many homes (CGNAT) and port forwarding cannot work. Ask your ISP for a public address, or host somewhere that has one.

Your public IP can change. If it worked last week and not today, a custom domain gives friends one address that keeps working. If you use a Coalstack domain and the server is stopped, the name deliberately points at a placeholder, so a timeout there usually just means the server isn't running.

More help

Coalstack's Auto Debugger scans a Java server's log for known errors like this one and links straight to the fix. Download Coalstack to try it.