Connection timed out: no further information, how to fix

Your client never reached the server. Check the server is running, the address is right, and whether the timeout is just you or everyone.

The short version

Connection timed out: no further information means the client never reached the server at all. Check three things in order: that the server is actually running, that the address is exactly right, and whether the timeout affects only you or everyone. Those three answers point at three different problems.

A client-side Connection timed out: no further information (full text: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection timed out: no further information) means your Minecraft client tried to open a TCP connection to the server and got no reply at all. The server might be down, the address might be wrong, or something between the two of you is dropping packets.

#Step 1: is the server actually running

Open Dashboard → your server. If the status pill is anything other than Running, that is your answer; press Start and wait for the dashboard to settle. If the status pill says Running, move on.

#Step 2: is the address right

For Minecraft Java, the address is the bare subdomain you picked at order time: yourname.hostd.it or yourname.hostdservers.com. No http://, no port (unless you have changed the listen port; the Connect tab shows the right form for your server).

A few specific things to check on the client:

  • Open the Minecraft launcher and look at the saved server entry. Spaces, missing characters, the wrong subdomain (typing hostd instead of hostd.it) all produce a connection timeout because DNS resolves to the wrong place.
  • Try the IPv4 fallback shown on the Connect tab. Some home routers do not forward AAAA records cleanly.

#Step 3: is it just you

If one player can connect and another cannot, the server is fine. It is something between that one player and us. Common culprits:

  • ISP-level filtering of Minecraft's port. Rare, but a few mobile and corporate networks block it. The player needs a different network or a VPN.
  • Firewall on the client machine. Windows Defender Firewall, third-party AV (Kaspersky, Bitdefender, McAfee), or a corporate VPN client. Whitelist javaw.exe and java.exe for outbound on port 25565.
  • A region-local outage on the player's route. Often clears within an hour; if the player's ping to other services is fine but to your address is timing out, that is what it is.

#Step 4: nobody can connect

If the server says Running and the address is right and no player can get in, open a ticket from Dashboard → Support. We will check the node-level routing.

#Where to go next

#Frequently asked questions

What does Connection timed out: no further information mean?

Your client sent a connection request and got nothing back. It is not a rejection; it is silence. That means either nothing is listening at that address, or something between you and the server dropped the traffic without replying.

Why can I connect but my friends cannot?

If the server is up and you can reach it, the problem is on their side or their network's. Have them check the address character by character, then try from a different network. One person failing while everyone else is fine is almost never a server fault.

Nobody can connect. What now?

Check the server is genuinely running rather than stuck in a boot loop, then read the console. A server that is starting, crashing and restarting looks online in a dashboard glance and refuses every connection in between.

Written and maintained by the Hostd engineering team. Last updated 2026-05-23. Notice a mistake? Tell us.

Keep reading