Docs › Minecraft

Fix "An existing connection was forcibly closed" (Minecraft)

2 min readUpdated Nov 3, 2026Copy link

The player got in, then the connection dropped. Work out whether it's one player (their network or client) or everyone (the server froze, restarted or crashed).

The player is kicked to a screen showing one of these:

Internal Exception: java.io.IOException: An existing connection was forcibly closed by the remote host

Internal Exception: java.net.SocketException: Connection reset

Timed out

The first wording comes from Windows; macOS and Linux players usually see "Connection reset".

Why it happens #

Something closed the connection between the game and the server. "Remote host" just means the other end, and on a player's screen that can be the server or anything on the network in between. Typical causes:

• The server stopped, restarted or crashed. Everyone is kicked at the same moment.
• The server froze for many seconds (memory full, a heavy plugin, chunk generation) and connections timed out.
• The player's connection dropped: weak Wi-Fi, a VPN, mobile data, or a router that cuts idle connections.
• Antivirus or a firewall on the player's PC killed the connection.
• Mod or version problems: a modded client and server that don't match can disconnect right after joining, often with a DecoderException nearby. See mismatched mods.

If it hits everyone #

1. Read the console around the time of the kick. Look for a crash, a restart, Can't keep up! or a watchdog message.
2. Crash? The crash-reports folder in Files has the details; see lag and crashes.
3. Freeze? See "A single server tick took 60 seconds" and Can't keep up.
4. Memory at the limit on the Console graph? See Java heap space.
5. A scheduled restart in the panel's Schedules kicks everyone too; that's expected.
6. Check the status page (status.esnoffical.com) to rule out a node problem.

If it hits one player #

1. Try a wired connection or move closer to the router, and turn off any VPN.
2. Restart the router if drops happen across different servers.
3. Allow Java through the firewall and turn off "web/HTTPS scanning" style features in antivirus for Java, or test with them off.
4. Match the server exactly: same Minecraft version, and on modded servers the same modpack version.
5. Test another network (a phone hotspot). If it's stable there, the home network is the cause.
6. Update Java and graphics drivers if the game itself also stutters or freezes.

Things that don't help #

• Raising network-compression-threshold or other network settings at random. Change one thing at a time and only if the console points there.
• Restarting the server over and over when only one player is affected. Their side is the place to look.
• Changing server-port. Keep the port the panel assigned.

What to send if you need help #

If you can't find the cause, post this in a ticket on the ESN Discord:

• The exact message the player saw, and the time it happened.
• Whether one player or everyone was kicked.
• The console lines from a minute before to a minute after (from Files → logs if the console has restarted since).
• Your server type and version, and whether it is modded.

That's usually enough to tell a server freeze from a network drop at a glance.

FAQ #

Does "forcibly closed by the remote host" mean the server kicked me?

Not necessarily. Anything between you and the server can close the connection. If others stayed online, the cause is usually on your side.

Why does it happen only when I explore?

New chunks cost the server the most. If the server freezes while generating them, connections time out. Pre-generating the world helps.

Can the host fix a player's Wi-Fi drops?

No. If only one player drops and others stay connected, the fix is on that player's network or PC.

Sources: Minecraft Wiki: server.properties keys and defaults (checked Nov 3, 2026) · Minecraft Wiki: crashes and crash reports (checked Nov 3, 2026)

Still stuck? Use the live chat on the panel or ask in the ESN Systems Discord. Last updated November 3, 2026.