Minecraft Connection Timed Out
‘Minecraft Connection Timed Out’ is the message every multiplayer player runs into eventually. Behind the friendly wording sits a Java network exception, and the meaning is precise: your client tried to reach the Minecraft server and got no response at all within the timeout window. The good news is that this is one of the most predictable errors in multiplayer. Work through the checks below in the right order and you’ll be back in the world in minutes.
Quick Fixing:Most Minecraft timeouts clear by step 4:
- Check the server is actually online at mcsrvstat.us.
- Match your Minecraft version to the server’s version.
- Allow Java(TM) Platform SE Binary (Windows) or the Java/Minecraft binary (macOS) through your firewall.
- Add an inbound rule for TCP and UDP port 25565.
- Flush DNS: ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS.
What ‘Minecraft Server Connection Timed Out’ Actually Means
The Minecraft timeout error has a specific technical meaning that’s worth understanding because it changes which fix applies. ‘Connection timed out’ means your client sent a connection request and waited (usually around 30 seconds) without ever getting a response. Nothing on the other side rejected the connection; nothing answered it at all. That points to a network or firewall problem somewhere along the path: your local firewall blocked the outbound packet, the server’s machine is unreachable, the IP/port is wrong, or a router along the way is dropping traffic.
This is different from ‘Connection refused’, which means a machine was reached at the address but actively closed the door, usually because the server software isn’t running on the expected port, or it’s offline. Both errors look similar in chat, but the fix paths diverge. This guide focuses on the timeout case.
Standard Checks for the Minecraft Server Timeout
Before changing any settings, run the cheap checks first. Most cases of ‘Minecraft server timed out’ are solved here:
- verify the server is up: paste the IP into a status checker like mcsrvstat.us
- confirm the address: typos in IP or port are the single most common cause
- restart your router: unplug for 30 seconds, plug back in, wait until it reconnects
- restart the launcher: closes any stale network sessions
- match your version to the server’s: a 1.20.4 client can’t join a 1.20.6 vanilla server
- try a different server: if that one works, the issue is on the original server’s side, not yours
If everything above checks out and the timeout persists, move on to firewall settings.
Firewall & Antivirus Blocks in Minecraft
The single most common cause of a persistent Minecraft connection timed out error is the Windows Defender Firewall silently blocking Java. The Minecraft client doesn’t run as Minecraft.exe, but as javaw.exe, which the firewall handles separately, and a recent system update or game version change can revoke the rule without warning.
Allow Java Through Windows Firewall
The exact path differs between Windows and macOS, but the principle is the same: the operating system needs explicit permission for the Java binary that Minecraft runs on. Once that’s granted, the timeout typically clears on the next launcher restart.
On Windows
Windows handles Java through the Defender Firewall’s app list. A handful of clicks gets Minecraft permanently whitelisted:
- open Windows Security → Firewall & network protection → Allow an app through firewall
- click Change settings, then find Java(TM) Platform SE Binary
- tick both Private and Public for every entry
- if Java isn’t listed, click Allow another app and browse to your Minecraft installation
- Save & try the server again
On macOS
MacOS uses an application-based firewall, which means you whitelist the Minecraft Launcher and its bundled Java binary as separate entries rather than opening a port. On Sonoma and later, an additional permission layer applies to local network access:
- open System Settings → Network → Firewall
- if the firewall is on, click Options (older macOS: Firewall Options)
- click the [+] button and add the Minecraft launcher and the Java binary inside it
- set both to Allow incoming connections
On macOS Sonoma 14 and later, also check Privacy & Security → Local Network and enable access for the Minecraft Launcher and Java.
Open Port 25565 for Minecraft
Java Edition uses TCP port 25565 by default. If allowing the app didn’t work, add an explicit rule for the port itself.
On Windows
On Windows, follow these steps:
- open Windows Defender Firewall → Advanced settings → Inbound Rules → New rule
- choose Port → TCP → 25565 → Allow the connection
- repeat the same for UDP 25565
- self-hosted servers will usually need this opened on the router as well
On macOS
MacOS doesn’t expose per-port inbound rules in the GUI the way Windows does. The application firewall works app-by-app, not port-by-port. For most setups that means the steps above (allowing the Java binary) are enough. If you’re hosting from your Mac and external players still time out, your router’s port forwarding is the bottleneck, not the macOS firewall. For advanced users, the underlying pfctl packet filter can be configured via the terminal, but that’s rarely necessary for client-side Minecraft.
Mods using extra services like voice chat need their own additional ports opened on top of 25565.
Antivirus, VPN & Router Quirks
Third-party antivirus apps and active VPN connections can throttle or block Minecraft traffic. Norton, Kaspersky, McAfee and ExpressVPN are frequent culprits. Disable them temporarily; if the connection works, add a Minecraft exception inside the antivirus settings rather than leaving protection off.
Mac users should also check whether iCloud Private Relay is active. Private Relay routes Safari and unencrypted traffic through Apple’s servers, and while Minecraft’s own connection isn’t strictly proxied, the feature has been linked to a noticeable share of intermittent timeouts on macOS and iOS.
- System Settings → [your Apple ID] → iCloud → Private Relay
Toggle it off, or disable it for the current network under:
- Wi-Fi → Details → Limit IP Address Tracking
A simple router power cycle on top of that clears stale routing tables on home networks and resolves a surprising share of stubborn timeouts.
Advanced Fixes When the Minecraft Timeout Sticks Around
If standard checks and firewall rules haven’t fixed the Minecraft server timeout, the next layer of causes is more technical. None of these require deep networking knowledge, but they do require a couple of specific steps.
Flush DNS and reset the network stack
Your DNS cache may hold a stale record for the server’s domain name. The commands differ between operating systems.
On Windows
Open the command prompt as administrator and run the following commands one at a time:
- ipconfig /flushdns
- ipconfig /release
- ipconfig /renew
- netsh winsock reset
Restart Windows after the last command. This resets the entire network stack and resolves a large share of the lingering connection errors that don’t clear with simpler fixes.
On macOS
Open the terminal and run the following one-liner. You’ll be prompted for your admin password:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
This flushes the macOS DNS cache and restarts the responder process. Reconnect to your Wi-Fi afterwards to refresh the network stack. On macOS that’s usually enough and a full restart isn’t required.
Version Mismatch Between Client & Server
A common source of the ‘Minecraft server timed out’ error after a recent update is a version mismatch. Big releases like the ‘Caves & Cliffs’ update or any 1.x major bump break compatibility between server and client. Check the server’s required version, then change your launcher version to match. On modded servers, every mod must match exactly: a single missing or extra mod can cause an immediate disconnect that looks identical to a network timeout.
Mojang Authentication Outages
Sometimes Mojang’s own authentication servers go down, and every Minecraft client that requires online verification fails to connect to any server. Check status.mojang.com or the official Minecraft Help Center before chasing your own setup further. If it’s their outage, no local fix will help – the only option is to wait it out.
When the Timeout Is on Your Own Minecraft Server
If you’re hosting the server yourself and players are getting timed out, the cause is usually on the server side. The fixes differ depending on whether you’re running it on your own machine or with a host like GPORTAL.
GPORTAL-Specific Tips
Here are some tips on how to fix the situation on your hosted server:
- restart the server through the web interface – fixes most state-related timeouts
- check log files via FTP for crash messages that don’t surface in the launcher
- confirm players are using the server address and query port shown at the top of the web interface
- for voice chat or other mods needing extra ports, use the additional ports XXX66 to XXX70
Check server.properties
Open your server.properties file and verify three lines:
- server-port=25565 – must match what players are connecting to
- server-ip= – leave this empty for most setups; a wrong value here makes the server bind to the wrong network interface
- max-players=20 – increase if too many players are trying to join at once
Save the file and restart the server.
Allocate Enough RAM
A server starving for memory will hang on player joins until the connection times out. The general rule is at least 2GB for a small vanilla server, 4GB for 5-10 players, and 6GB or more once you add modpacks. If the symptoms are intermittent and worse at peak times, this is the most likely cause and it is time for a RAM upgrade.
Port Forwarding for Self-Hosted Minecraft Servers
If you’re running the server on your home network and external players are timing out, your router needs a port forwarding rule for TCP/UDP 25565 pointed at your computer’s local IP. Be aware that exposing a server to the open internet creates security risks: a rented Minecraft server from GPORTAL handles all of this automatically, with the IP and port already public from day one.
FAQ
Minecraft Java Edition uses TCP port 25565 by default. Bedrock Edition uses UDP port 19132. Server owners can change these in server.properties, but unless there’s a specific reason, leaving them at the default avoids most port-related timeouts.
No, ‘connection timed out’ means there’s no response at all. This is usually a firewall or routing issue. ‘Connection refused’ means a machine was reached but rejected the connection, which usually means the server isn’t running or is on a different port than expected.
Some routers drop idle TCP connections after 5 to 15 minutes, and large networks like Hypixel enforce idle timeouts on their own. If you only get a timeout while AFK, the easiest fix is a small ‘anti-AFK’ macro or simply staying active in the world.
The issue is local to your client or network. Run through the firewall and DNS steps above. If a friend can connect from a different network, that confirms the server itself is fine and the cause is on your side: usually antivirus, a VPN, or a stale DNS record.
Use mcsrvstat.us or any similar status checker. Paste the IP and port and the tool will tell you whether the server is responding, what version it’s running, and how many players are currently online.
Time’s Up – Get Back Online
Connection issues are the price of admission for online play, but the ‘Minecraft connection timed out’ error is one of the most predictable problems in multiplayer – work the checks from cheap to technical, and one of them will land. If you’re tired of fighting your own router and firewall every time you want to play with friends, a Minecraft server from GPORTAL takes the networking work off your plate: the IP and port are public from day one, the firewall is configured, and the only thing standing between you and the world is the launcher itself.
similar articles
Minecraft
Minecraft Note Block
Minecraft
Minecraft Creative Mode
Minecraft