Minecraft Fatal Error: Fix “This Connection Is Terminated” Disconnects
The Minecraft message “A fatal error has occurred, this connection is terminated” means the current connection ended; it does not identify why. In many cases, Java Edition returns to the server list while the game itself stays open. Start by checking whether the problem affects one server, every server, or a single-player world. That quick comparison helps distinguish a server or mod issue from a problem on your computer or network.
Use the checks below in order. Keep your worlds and mod files intact while testing. The phrase Minecraft fatal error is not a single, universal error code, so the newest log and the circumstances of the disconnect matter more than the wording alone.
First, identify what is actually shutting down
- Only one server disconnects: the server, its modpack, or its compatibility settings may be responsible.
- Several servers disconnect, but single-player works: investigate the client version, mods, and network path.
- The game window closes or freezes: that is a client crash. Check the crash report as well as the log.
- A single-player world disconnects: the integrated server or a local mod may have stopped; this is different from an internet connection dropping.
A line such as “Shutting down internal server” can appear as Minecraft exits a session. It is not proof that a public server shut down or that your internet failed.
How to fix the Minecraft “connection is terminated” error
1. Restart the session and test another server
Close Minecraft and the launcher completely, reopen them, and try joining again. If the same error returns, test a second server you are permitted to join. Ask a friend or the server administrator whether other players are disconnecting at the same time. If only one server is affected, repeated changes to your computer are unlikely to fix a server-side problem.
2. Match the game edition, version, and server setup
Java Edition connects to Java Edition servers, and Bedrock connects to Bedrock worlds and servers. The server may also require a specific Minecraft release or modpack. Check the server’s posted instructions and select the version it supports; the newest release is not automatically compatible with every server. For a modded server, the client and server generally need compatible loader, mod, and configuration versions.
Use the official launcher’s existing installation or create a separate test installation. Avoid changing Java arguments or installing a different Java runtime as a first fix: the launcher manages the runtime for standard profiles, while custom launchers and modpacks may have their own documented requirements. Minecraft’s multiplayer requirements explain the edition, release, and connection basics.
3. Run one clean, unmodded test
If you normally use Forge, NeoForge, Fabric, a custom launcher, or a large modpack, test with a separate vanilla profile on the same game version when the server allows it. Do not delete your mods or worlds. If the clean profile connects, the problem is more likely related to a mod, loader, resource pack, or configuration. Update only the components that the server requires, then re-enable or add mods in small groups until the disconnect returns. This controlled test is more useful than removing files at random.
If the server requires mods, a vanilla profile may be rejected by design. In that case, compare your installed mod list with the server’s instructions and ask the administrator which client files are required.
4. Check the network path without disabling protection
Restart your router and computer if the connection is unstable, then try Ethernet or a reliable Wi-Fi connection. If you use a VPN or proxy, and your network rules allow it, test once without it or try a trusted alternate network. This helps isolate the route without assuming the VPN is the cause.
On Windows, check that Minecraft or its Java process is allowed through the firewall for the network profile you use. Keep the firewall enabled; do not create broad exceptions or open server ports on your router just to join a public server. Port forwarding is generally relevant to people hosting a server, not ordinary players joining one. Minecraft’s network connection troubleshooting page is a good next stop for broader connection problems.
5. Read the log around the disconnect
For the official launcher, open the game directory and inspect the newest file in its logs folder, named latest.log. On Windows the usual directory is %appdata%\.minecraft\logs; on macOS it is ~/Library/Application Support/minecraft/logs; on Linux it is ~/.minecraft/logs. Third-party launchers may use a separate instance directory, so check their documentation.
Search the final lines for the disconnect time, an exception, or a mod name. Terms such as Connection reset, ReadTimeoutException, or DecoderException are clues, not diagnoses: the server, network path, or a mod can produce similar symptoms. If the game process actually crashes, look in the separate crash-reports folder. A crash report contains crash details; latest.log records the broader game session. Fabric’s documentation explains where to find and share logs and how crash reports differ.
6. Contact the server administrator when the issue is server-specific
If other servers work, send the administrator the time of the failure, your Minecraft version, loader and modpack versions, and the relevant log excerpt. They can compare it with the server console and check whether the server is rejecting a version, mod, packet, or player state. Redact your Microsoft username, local file paths, and private server address before posting logs publicly. Minecraft’s guide to joining a Java multiplayer server covers the official connection flow.
What not to change as a first response
- Do not edit undocumented timeout or ping values in
options.txt; those are not a reliable general fix for this message.
- Do not allocate a fixed amount of RAM unless the log points to a memory problem. More memory does not repair a server disconnect and can destabilize a system if over-allocated.
- Do not reinstall Minecraft or delete configuration folders before checking the log and backing up worlds. If the game closes with an out-of-memory crash, follow Minecraft’s memory-allocation crash guidance.
- Do not assume a performance mod will fix a network or server-side issue. Graphics performance and multiplayer connection failures have different causes.
Quick checklist
- Confirm whether the disconnect happens on one server or all servers.
- Match the edition, game release, loader, and required mods.
- Try a clean profile without deleting your normal installation.
- Check the network route and allow the game through the firewall without turning protection off.
- Read
latest.log; use a crash report only when the game itself crashes.
- Send a redacted log excerpt to the server administrator if the issue is limited to that server.
This sequence narrows down the Minecraft connection terminated error without relying on unsupported fixes. If the game remains open and only one server drops you, start with that server’s administrator; if multiple servers fail, compare a clean profile and a stable network before changing files.