Photo by Ferenc Almasi on Unsplash

So there I was, Friday night, finally got my friends together for a Minecraft session we'd been planning for two weeks. Server's up, everyone's online — and half the group just keeps staring at this garbage:

io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: no further information
    at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.fulfillConnectPromise
Failed to connect to the server

Yeah. That one. If you've hit the "failed to connect to server" error in Minecraft, you already know how weirdly vague it is. It could mean literally five different things, which is what makes it so annoying to troubleshoot.

I've dealt with this across Java Edition, Bedrock, and on hosted servers — so let me just walk you through what actually fixes it, in the order I'd try them myself.

Why This Even Happens

Honestly, the error message is useless on its own. "Failed to connect to server" is Minecraft's way of shrugging at you. Under the hood, it usually means one of these things:

• The server's offline or still starting up
• You've got the wrong IP or port
• Your firewall or antivirus is blocking the connection
• Your DNS cache is stale and pointing nowhere
• Java version mismatch between client and server

The connection refused variant (like the one above) almost always means the server isn't actually running or it's listening on a different port than what you're hitting. The timeout variant — where it just hangs forever — that's usually a firewall or network thing.

Fix 1: Flush Your DNS and Reset Network Stack

This one fixes it way more often than it should. Stale DNS entries are sneaky — your machine thinks it knows where the server is, goes to an old IP, gets nothing. Classic.

On Windows, open Command Prompt as administrator and run these one by one:

ipconfig /flushdns
ipconfig /release
ipconfig /renew
netsh winsock reset

Then restart your machine. I know, I know — restarting feels like giving up. But after a winsock reset, you actually need it for the changes to take effect.

On macOS:

sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

On Linux it depends on your distro, but most systemd-based ones:

sudo systemd-resolve --flush-caches

After this, try connecting again before doing anything else. You'd be surprised how often this is all it takes.

Fix 2: Check the Firewall (Windows Defender Loves Blocking This)

Windows Defender Firewall is quietly aggressive. If Java got an update recently, or you reinstalled Minecraft, the firewall rule for Java might have gotten wiped or reset. This is probably the number one cause I've seen when people swear "it was working yesterday."

Here's how to add a proper inbound rule manually. Open PowerShell as admin:

New-NetFirewallRule -DisplayName "Minecraft Java" -Direction Inbound -Protocol TCP -LocalPort 25565 -Action Allow
New-NetFirewallRule -DisplayName "Minecraft Java UDP" -Direction Inbound -Protocol UDP -LocalPort 25565 -Action Allow

If you're running the server on a non-default port (some hosts use things like 25566, 19132 for Bedrock, etc.), swap out 25565 for whatever yours actually is.

Also worth checking — if you're the one hosting the server, make sure port forwarding is set up on your router. The server needs TCP port 25565 forwarded to your local machine's IP. I can't tell you how many times someone's set up a server, added a firewall rule, and completely forgotten about the router. Your local firewall and your router are two separate walls the connection has to get through.

Fix 3: Verify the Server Is Actually Running and Check the Port

Okay this sounds obvious but bear with me. Sometimes the server crashes on startup silently, especially if it ran out of memory or there's a plugin conflict. Before anything else on the server side, check the actual process:

On Linux/Mac server:

ps aux | grep minecraft

If nothing shows up, the server's just... not running. Start it up again and watch the console output this time. On Windows, just check if the server window is still open or if it closed itself.

Once it's running, verify it's actually listening on the right port:

# Linux/Mac
ss -tulnp | grep 25565

# Windows (PowerShell)
netstat -ano | findstr :25565

You should see a line showing something is LISTEN on that port. If it's empty, the server started but didn't bind to the port — usually a server.properties misconfiguration or a port conflict with something else on the machine.

While you're in server.properties, double-check this line:

server-port=25565
online-mode=true

If online-mode is set to false and you're trying to connect with a legitimate account, that can cause weird auth failures that look like connection errors. And if it's true but you're trying to connect with a cracked/offline client — that's your problem right there.

Fallback: Try Connecting via Direct IP Instead of Hostname

If you're connecting to a server using a domain name (like play.someserver.net) and nothing above has worked, try grabbing the actual IP address and connecting with that directly.

nslookup play.someserver.net

Take the IP it spits back and plug that into Minecraft's server address field instead of the domain. If that works, it's a DNS resolution issue on your end specifically — maybe your ISP's DNS is slow or broken. In that case, switching to Google's DNS (8.8.8.8) or Cloudflare's (1.1.1.1) in your network adapter settings usually sorts it out permanently.

One more thing — if you're on a college or work network, there's a decent chance they're blocking port 25565 entirely at the network level. There's not much you can do about that without a VPN, and honestly even then it's a coin flip depending on how locked down things are.

Hope this saves you the 45 minutes of Googling I've done more than once. The DNS flush + firewall rule combo fixes probably 70% of these cases in my experience, so start there and work your way down.