Fixing common Minecraft connection errors

"Connection timed out"

Full text on Java is usually:

io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection timed out: no further information

What it means: your client sent a request and nothing came back at all. Not a refusal — silence. The packets went out and vanished.

What causes it, in order of likelihood:

• A typo in the address. Overwhelmingly the most common cause. Check every character.
• A firewall or network blocking the traffic. School, university, office and public Wi-Fi networks very often block game ports. This is the classic "it works at home but not at res" problem.
• The server is genuinely down or restarting.
• Your own firewall or antivirus blocking Java. Some security suites are aggressive about outbound connections from javaw.exe.
• Router or ISP problems — less common, but it happens.

How to fix it: tether to your phone's mobile hotspot and try again. This single test separates "the network I am on is blocking it" from everything else, and takes under a minute. If it works on mobile data, the problem is your network, not the game. If it fails on both, check whether the server is up and confirm the address.

On Windows, it is also worth flushing your DNS cache. Open Command Prompt and run ipconfig /flushdns, then restart Minecraft.

"Connection refused"

io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: no further information

What it means: this is different from a timeout, and the difference is informative. Something answered — it just said no. Your client reached a machine at that address, but nothing was listening on the port it tried.

Usual causes: the address resolves but the server software is not currently running (mid-restart, or crashed); you have specified the wrong port; or the address points somewhere that is not a Minecraft server.

How to fix it: check the port. On Java, use play.minecraftsa.co.za with no port at all — the default of 25565 is correct and adding a wrong one breaks it. If you previously typed a port into the address field, delete it. Then wait a few minutes and retry; if the server is restarting, refused connections are exactly what you would expect for a minute or two.

"UnknownHostException"

java.net.UnknownHostException: play.minecraftsa.co.za

What it means: your device could not turn the address into an IP address. This is DNS failing, not the server.

How to fix it:

1. Check the spelling again. A mistyped domain produces exactly this error, and .co.za is easy to get wrong.
2. Flush your DNS cache — ipconfig /flushdns on Windows.
3. Test whether the name resolves at all. Run nslookup play.minecraftsa.co.za in Command Prompt or Terminal. If you get an IP address back, DNS is working and the problem is elsewhere. If it fails, DNS is your problem.
4. Try a different DNS provider. Some South African ISP resolvers are slow or occasionally flaky. Switching your device or router to a public resolver such as Cloudflare's 1.1.1.1 or Google's 8.8.8.8 often fixes it outright, and generally speeds up browsing as a side effect.
5. Restart your router if DNS is failing for multiple sites, not just this one.

"Outdated client" or "Outdated server"

You will see something like Outdated client! Please use 1.21 or Outdated server! I'm still on 1.20.4.

What it means: exactly what it says, and it is the most straightforward error in this list. Minecraft clients can generally only speak to servers running a matching protocol version.

Outdated client — you are behind. Update through the launcher (Java) or your app store (Bedrock).

Outdated server — you are ahead, which happens when a new Minecraft version releases and servers have not moved yet. Server operators cannot always update on day one, because plugins and mods need to be updated first and that depends on other people's release schedules.

On Java you can simply switch versions:

1. Open the Minecraft Launcher.
2. Go to the Installations tab.
3. Click New installation.
4. Pick the version you need from the dropdown and save it.
5. Launch that installation and connect.

You can keep as many installations as you like side by side, which is the normal way to play on several servers running different versions.

"Invalid session" and "Failed to verify username"

Failed to login: Invalid session (Try restarting your game and the launcher)

What it means: Java Edition verifies your account with Microsoft's authentication servers when you join a server. Your session token has expired or was rejected.

How to fix it: restart both the game and the launcher — genuinely, in that order, and close the launcher fully rather than minimising it. This works most of the time. If it does not, sign out of your Microsoft account in the launcher and sign back in.

Failed to verify username! is a related but distinct problem: it usually means Microsoft's authentication service itself is having trouble, and no server can verify anyone. If several servers reject you at once, this is almost certainly what has happened, and there is nothing to do but wait it out.

Disconnects during play

Different class of problem: you connect fine, then get dropped.

Internal Exception: ReadTimeoutException

Internal Exception: io.netty.handler.timeout.ReadTimeoutException

Your client stopped hearing from the server long enough for it to give up. That is usually an unstable connection on your side — Wi-Fi dropping briefly, mobile signal fluctuating, or another device saturating the line. Occasionally it is a server-side stall.

If it happens repeatedly, the fixes are the ones in the ping guide: get onto a cable if you can, stop large downloads, and check whether your connection is stable generally.

An existing connection was forcibly closed by the remote host

Something between you and the server severed the connection abruptly. Sometimes a network hiccup, sometimes overzealous firewall or antivirus software deciding a long-lived game connection looks suspicious. If it is frequent and only happens to you, try temporarily disabling third-party antivirus network filtering to test.

Connection lost / timed out mid-session

The generic version of the same thing. One-offs are not worth worrying about. A pattern — every twenty minutes, say — points at your router or your ISP, and is worth raising with them.

Bedrock: "Unable to connect to world"

Bedrock's error handling is far less informative than Java's. Almost everything surfaces as this one message, which means you have to work through the possibilities rather than read the cause off the screen.

Check in this order:

1. The port. Bedrock needs 19132. This is the single most common cause. Open the server entry and confirm the port field is right — if you left it blank or entered the Java port, it will never connect.
2. The address. play.minecraftsa.co.za, with no http:// and no spaces. Watch for a space auto-inserted by a phone keyboard at the end.
3. Fully restart Minecraft. Bedrock caches failed lookups more stubbornly than Java. Close the app from your recent-apps list, not just to the main menu.
4. Check you are signed in to Xbox Live. Bedrock multiplayer requires it. If your Microsoft session has expired, servers fail with this same unhelpful message.
5. Check multiplayer privacy settings. In your Microsoft account's Xbox privacy settings, "You can join multiplayer games" must be allowed. This catches out child accounts constantly, and the setting can only be changed from the parent account.
6. Delete and re-add the server entry. Corrupted saved entries are a real thing on Bedrock, and re-adding from scratch fixes them.
7. Try mobile data. Same test as on Java — it instantly tells you whether your network is the problem.

If nothing above worked

A short list of last resorts that occasionally succeed when the obvious things have not:

• Restart your router. Not a joke, and not a stalling tactic — stale NAT state genuinely causes intermittent connection failures that survive every client-side fix.
• Disable VPNs and proxies. If you are running one, take it off for the test. See the ping guide for why a VPN is usually working against you on a local server anyway.
• Test on another device. If your phone connects and your PC does not, on the same network, the problem is on the PC — firewall, antivirus, or Minecraft installation.
• Reinstall, as an actual last resort. Back up your worlds first. This fixes very little, but it does fix corrupted installations.

If you have worked through all of this and still cannot connect, email us with the exact error text — a screenshot is ideal — plus your platform and Minecraft version. Those three details are usually enough to identify the problem immediately, and their absence is why so much troubleshooting takes days.

Frequently asked questions

← All guides