How to Fix the “Server Connection Timed Out” Error in Minecraft

The “Server Connection Timed Out” error is one of the most common reasons players can’t join a Minecraft server. It appears when your client attempts to connect but receives no response within the allowed time window. This can happen on both modded and vanilla servers, and the cause isn’t always a bad internet connection. Server configuration, firewall rules, and mod mismatches all trigger the same error message.

This guide covers every practical fix, starting with the simplest steps.

Vanilla Solutions

Direct Connect

Using a direct IP address instead of the server list bypasses some detection failures that cause timeout errors.

1. Log into your Apex server panel and click on your server.
2. Locate the IP Address:Port and or Subdomain section.
   

3. Copy the address of either one, then open Minecraft and go to Multiplayer.
4. From there, click on Direct Connection and paste the address in the Server Address field. You may want to try both of the addresses for this purpose.
   

5. That’s it! You’re done, and it should work unless there is an underlying issue.

Restart the Minecraft Server

A full server restart clears stuck processes and forces a clean network handshake. Many timeout errors resolve after a single restart.

1. Navigate to your Apex server panel and choose your server.
2. Click on Restart, then wait for it to fully load. You can confirm it’s loaded fully by locating the Console to the left of the panel, then looking for the Startup Done message.
   

3. After that, please proceed to join the Minecraft server. That may resolve the situation!

Check Your Firewall and Antivirus

Windows Firewall and antivirus tools sometimes block Minecraft’s outbound connections without showing a clear error. To test this, temporarily disable your Windows Firewall or add a Minecraft exception, then try connecting. If the timeout stops after disabling, you need to add a permanent firewall exception for the Minecraft Java executable (javaw.exe).

Third-party antivirus tools follow the same logic. Check your antivirus activity log for any blocked Minecraft connections and add an exception if one appears.

Adjust the Server Read Timeout

If players consistently time out during heavy load or on slower connections, the server’s default read timeout may be too short. You can raise it by editing server.properties:

1. Go to your Apex server panel and open the File Manager.
2. Open server.properties and locate (or add) the network-compression-threshold setting.
3. For timeout-specific tuning, set read-timeout in your server configuration. The default is 30 seconds; raising it to 60 can help players on slower connections complete the login handshake.
4. Save the file and restart the server.

If you’re running a modded server where login takes longer because of a large mod list, raising the read timeout is often the most effective fix.

Modded Solutions

On modded servers, timeout errors often occur because the login process takes longer than the server allows. The Minecraft client must complete a handshake while also syncing the full mod list, which can exceed the default timeout window on large modpacks.

Forge 1.8 to 1.16.5

1. Download the RandomPatches Forge mod from CurseForge and make sure the version matches your server version.
2. Install the mod on your server from the Apex server panel, which you can review more on that process here.
3. Once installed, restart the server and wait for it to load.
4. Next is to upload the same mod into your launcher’s local mods folder. It’d be where all the files are for the launcher or modded profile for it.
5. After everything is installed correctly with the server online, join it to confirm everything works as intended.

Fabric 1.15.2 to 1.16.5

1. Head to the RandomPatches Fabric download page on CurseForge, then start downloading the correct version for your server.
2. After that, install the mod onto your server from the Apex server panel. Learn more about that here.
3. Start up the server from the panel and wait for it to finish loading.
4. Make sure to upload the same mod into your local Fabric mods folder, which should be in your launcher files or profile for it.
5. Once the server is done loading and you installed the mod locally, try joining to see if that fixed the situation.

If you’re running Minecraft 1.17 or later, RandomPatches is not available for those versions. In that case, check whether any mods in your pack have known compatibility issues that cause login stalls, and try removing recently added mods one at a time to isolate the problem. You can also try the read-timeout fix described in the vanilla section above, as it applies to modded servers too.

Common Questions

The error is often tied to individual connection quality rather than server settings. Players on slower or unstable connections time out before completing the handshake, while those on faster connections succeed. The firewall fix and read-timeout adjustment help the most here.

Not necessarily. If other players can join while one person gets the error, the server is running. The issue is between that player’s client and the server. Start with the Direct Connect method and firewall check before assuming the server needs to be restarted.

Modded servers take longer to complete the connection handshake because the client and server must sync their full mod lists. For large modpacks, this can exceed the default timeout window. A mismatched mod channels error can also produce similar timeout symptoms.

Conclusion

The Server Connection Timed Out error has several possible causes, and the fix depends on where the problem originates. Start with Direct Connect and a server restart. If those don’t work, check your firewall settings. For modded servers on older Forge or Fabric versions, RandomPatches extends the connection window and resolves most timeout issues. If you’re also seeing the Outdated Server error alongside timeouts, a version mismatch is the likely culprit and should be addressed first.