How to Fix "Connection Timed Out" When Joining a Minecraft Server

That red Connection timed out: no further information: line — sometimes with java.net.ConnectException stuck in front of it — drops you back to the multiplayer list with no hint about what to do next. It almost never means your game is broken or needs reinstalling. A timeout means a small packet your client sent never got an answer. The cause is one of a short list of findable things, and you can work through them in a few minutes without touching anything you can't undo.

Work the checks in order: confirm the server is actually up first, because that's the cheapest check and the most common cause, then verify the address and port, then rule out your own network and firewall. Doing it in that order keeps you from changing a router setting for a server that was simply offline. This is a Java-focused walkthrough — the literal error text is Java's wording — and if you're not sure the add-server flow itself is right, the how to join a Minecraft server guide covers that part.

What "connection timed out" actually means

Your client tried to open a connection to the address and port you gave it — it sent a connection request and waited for an answer. When nothing ever came back, Java gave up and printed the timeout. This happens at the TCP connect stage, before any Minecraft handshake even starts; there's no connection established yet to handshake over. The "no further information" part just means your operating system handed back no extra detail — not that something exotic went wrong.

The distinction that trips up beginners is the one between this error and "connection refused," because they point at opposite causes. Connection timed out means no reply came back at all: a firewall blocked your outbound packet, a router somewhere along the way dropped it, the host is unreachable, or the address points at nothing that answers. Connection refused (java.net.ConnectException: Connection refused) means the machine was reached but actively turned you away — usually because the server process isn't running, or it's listening on a different port than the one you connected to. A clear "no" came back fast in the refused case; in the timeout case nothing came back at all, and that silence is what tells you the host couldn't be reached. The sister error family that wraps these — io.netty.channel connect exceptions — is broken down message by message in what io.netty.channel errors mean, so if you're seeing that prefix too, read that one alongside this.

You'll sometimes see a getsockopt variant — Connection timed out: getsockopt. That getsockopt isn't a separate problem; it's the operating-system call Java makes to read the result of a non-blocking connect that never completed. Java fires off the connect, and when it later calls getsockopt(SO_ERROR) to check whether it succeeded, the answer is "it timed out." Same timeout at the connect stage, same troubleshooting, no need to treat it as its own thing. None of these have anything to do with your account or your copy of the game. Owning the game and being able to open multiplayer is all you need here; this is about reaching one specific machine.

First, confirm the server is actually online

The single most common cause of a timeout is a server that's down, restarting, or mid-update, and there's no point editing your firewall for that. So check this first.

The fast way is to look the server up on the live rankings or the full server list. Both show a live ping and current player count pulled by the listing site's own status check, which reaches the server the same way your client does. A grey or red signal — or a zero where there's normally activity — means the server is unreachable right now, and that's about the server, not you.

For a second signal that doesn't depend on the listing, grab a different server you know is good and try to join that one instead. If it connects, your game, network, and account are all fine, and the problem is specific to the first server's status or address. If the second one also times out, the problem is on your end, and you can skip ahead to the network and firewall section.

One more thing worth knowing: a server in the middle of a restart or a version update can stop answering for a few minutes and then accept connections once it's back. If the listing shows it as normally healthy, retrying a few minutes apart is the right move before you assume anything's actually wrong.

Double-check the address and the port

Re-copy the address rather than typing it from memory. A single wrong character — a capital O standing in for a zero, a trailing space, a dropped letter — sends your client at an address that answers nothing, and that reads as a timeout. Every listing on the site shows the exact address to copy, so pull it straight from there.

The port catches a lot of people. Java's default port is 25565, and when a server uses the default you type only the hostname with nothing after it. You add :port (like play.example.net:25540) only when the listing names a non-default one. Point at the wrong port — or paste a Bedrock-style 19132 onto the end of a Java address — and you land on something that doesn't answer, which is the same timeout again.

A few formatting mistakes do the same thing: putting the port in a separate field that doesn't exist on Java, adding http:// or a slash, or copying the address along with some surrounding text. The address field wants just the hostname, or hostname:port, and nothing else.

Edition matters too. A Bedrock-only address will time out from Java no matter how perfectly you type it, because the two editions don't talk to each other directly. Check that the listing supports Java, or look at the crossplay entries, which are set up to bridge both. Whatever you typed should match what's listed for both address and version — the listing is the source of truth, so reconcile any mismatch there first.

Rule out your own network and firewall

You only need this section if a known-good second server also timed out, which means the problem is local rather than tied to one server.

A firewall is the most common local cause of a timeout — it blocks the packet silently, so there's no refusal, just nothing. Windows Defender Firewall or third-party antivirus can quietly block javaw.exe, the Java runtime, from making outbound connections, so your packet never leaves the machine and you get a timeout with no other symptom. The fix is to allow Java and Minecraft through the firewall. Temporarily switching the firewall off to test is a quick way to confirm that's the cause before you add the permanent allow rule, just remember to turn it back on after.

If that's not it, restart the path. Power-cycle the router and modem — unplug, wait a minute, plug back in, and give it time to fully reconnect — to clear a stale connection or a cached DNS entry. Toggling Wi-Fi off and back on makes the device pick up a fresh route too.

The cleanest single test for a local-versus-remote split is to swap networks. Try the same server on a phone hotspot instead of your home Wi-Fi, or the other way around. If it works on one and not the other, your router or ISP is the issue, not the server.

DNS is the quieter cause. If the address resolves slowly or to a stale IP, the connection can hang and time out before anything answers. Switching the device or router DNS to a public resolver like 1.1.1.1 or 8.8.8.8 sometimes forces a working route. A VPN cuts both ways here — it can route around a block that's causing the timeout, but a flaky VPN or proxy can also be the thing introducing it, so test with it both off and on.

When it's the server's side, not yours

If the listing shows the server live with players for everyone else, your second test server connects fine, and your address and port match the listing exactly, then the timeout is on the host's end — their network or a brief hiccup — and not a setting you can change.

In practice that's a server that just updated versions, is restarting on a schedule, or is briefly overloaded, any of which can stop answering for a short window. The right response is to wait and retry rather than keep editing your own setup. A player can't fix a host-side firewall or routing problem from the client, so when the address is correct and the server is genuinely up-but-unreachable, your only real levers are to wait, retry, or pick a different server.

And pick a good target to test against. Troubleshooting against a dead or empty server wastes the time you put into it — choose a clearly online, populated server from the live monthly rankings so that any failure actually tells you something.

FAQ

What's the difference between "connection timed out" and "connection refused"?

The body walks through this in full, but the short version: timed out means nothing replied at all, so you can't tell whether the host even exists — a firewall, a dropped packet, an unreachable host, or a wrong address. Refused means the machine answered fast to say there's nothing to connect to, which almost always means the server process is down or you aimed at the wrong port. The practical upshot is that refused points you at the server's port and status, while a timeout sends you through the server-status, address, and firewall checks above.

Why does only one specific server time out when every other server works fine?

That pattern rules out your firewall, network, and account, because those would break every server, not one. It points at that single server being down or restarting, or at the exact address or port you saved for it being wrong. Re-copy the address straight from its listing, check the listing's live ping to see whether it's even up right now, and if it shows online for everyone else, the host is briefly unreachable on their end and waiting a few minutes is the fix.

Does "no further information" or "getsockopt" in the error mean something different?

No. "No further information" just means your operating system handed Java no extra detail about why the connect failed — it's not a special error. "getsockopt" is the operating-system call Java uses to read the result of a connect attempt that never completed; seeing it named just tells you where Java noticed the failure, at the connect stage. Both are the same timeout underneath, so you troubleshoot them the same way: server status first, then address and port, then your own firewall and network.

Minecraft connects on my phone hotspot but not my home Wi-Fi — what now?

That split says the server is fine and something on your home network is dropping the packet — most often the firewall or a router that's holding a stale route. Back on the Wi-Fi, allow Java and Minecraft through Windows Defender Firewall and your antivirus, then power-cycle the router and modem and let them fully reconnect. If it still only works on the hotspot after that, the block is likely at your router or ISP level, and pointing the device's DNS at 1.1.1.1 or 8.8.8.8 is the next thing to try.