How to Fix Minecraft Internal Exception java.net.SocketException Connection Reset?

Minecraft Java Edition can find a multiplayer server but disconnect with “Internal Exception: java.net.SocketException: Connection reset” while joining or loading the world. The message means the connection was abruptly interrupted, not that Minecraft could not find the server.

The error does not identify what interrupted the connection. A server fault, unstable Wi-Fi, network filtering, or a problem with that Minecraft installation can produce the same message. Browsing normally or loading a single-player world does not rule those out.

1. Compare Another Server and Restart Minecraft

Before changing Windows settings, check whether the problem affects more than one server. A brief interruption may clear after reopening the game; persistent trouble on one server needs a more focused check.

1. Try another Java server compatible with your current installation. Ask whether another player on a different network can join the affected server.

   

   The pictured ban notice is a different error. A server ban requires the owner’s appeal process, not connection repairs.

2. Close Minecraft and the launcher. If the game remains in Task Manager, end only its confirmed process, not every Java or OpenJDK application. Save your work and restart the PC if you cannot identify it.

   

3. For repeated connection drops, restart your home router and modem: disconnect power for about a minute, reconnect the modem first, then the router, and wait for internet access to return.
   
4. Reopen Minecraft and retry the same server. An Ethernet connection is also worth testing if Wi-Fi is unstable.

This is a power restart, not a factory reset. If another server works, your PC can make multiplayer connections, but a network problem affecting only the original server is still possible.

2. Match the Server Version and Check Custom Java Settings

A server update can leave your existing installation incompatible. Use the server’s required release, rather than automatically switching to Minecraft’s newest version.

1. Check the required version with the server owner. In the official launcher, open Installations, create or edit an installation, and select that release. Minecraft provides a version-selection walkthrough.

   

2. For an installation with a manually selected Java executable, record its current setting. Open Edit > More Options and clear the custom Java executable path so the launcher uses its bundled runtime. Leave JVM arguments unchanged.

   

   The pictured Java 17 path is an example, not the required runtime for every release.

3. For a third-party launcher, use the Java runtime and mod-loader version recommended by the modpack. Relaunch and test.

If the matching installation stays connected, keep it for that server. Leave an already-default runtime alone, and restore a custom setting if changing it causes launch trouble.

A separate “Failed to login: Invalid session” message needs an account sign-in refresh instead.

3. Compare Connections Before Changing Network Settings

A working browser does not guarantee a stable Minecraft connection. Testing the same server through another connection is more useful than assuming your internet speed is the problem.

1. If you use a personal VPN, disconnect it and retry. An existing VPN can also improve a troublesome connection, but only test that where the network and server rules permit it.
2. Try a trusted alternative network, allowing for mobile-data charges. For a phone hotspot, enable it on the phone, select it from your PC’s Wi-Fi list, and retry the same server.

   

   The image shows Windows proxy settings. Leave a required proxy unchanged; that switch alone is not a general Minecraft connection fix.

3. Check your security software’s blocked-connection history for Minecraft or its Java executable. Correct a confirmed block using a narrowly scoped exception; keep antivirus and firewall protection enabled.

A successful hotspot test narrows the problem to differences between connections; it does not prove the router is faulty. Report that result to your ISP or network administrator. School, work, and family filters should be handled by whoever manages them.

Clear DNS only when the server address or network changed

DNS tells Minecraft which address to connect to. Clearing its cache can help with stale address information, but it is not a general repair for a connection that already established successfully.

1. Close Minecraft. Search for Command Prompt and choose Run as administrator.
2. Run ipconfig /flushdns, then reopen Minecraft and test.

   

The screenshot also shows /release and /renew. Those interrupt your network connection and are not needed for this DNS check.

4. Check the Java Executable in Your Firewall

Java Edition’s game process is separate from the launcher. Security software may therefore permit sign-in while blocking the executable used to join a server.

1. With Minecraft open, find its Java/OpenJDK process in Task Manager > Details. Right-click it and select Open file location to identify the actual executable.
2. Check for a block affecting that file in your security software. In Windows, Firewall & network protection > Advanced settings > Outbound Rules shows outgoing-connection rules. Change only a confirmed, unintended rule you control.
3. For a required Windows app exception, open Allow an app through firewall > Change settings > Allow another app. Select that executable and limit permission to the necessary network profile.

   

Windows normally permits outgoing connections; the screenshot’s Private/Public boxes mainly concern incoming access and cannot override an explicit outgoing block. Microsoft’s app-exception instructions explain the risks.

Do not open router ports just to join a server. If multiplayer works after correcting a block, keep that correction; remove any new exception that did not help.

5. Test the Server’s Resource Pack

Some servers download a resource pack as you join. Testing without it, or downloading a fresh copy, checks whether that download is involved without deleting your game data.

1. Open Multiplayer, select the server, and choose Edit. Temporarily set Server Resource Packs to Disabled, then reconnect.

   

2. If the server requires its pack, restore the previous setting. Close Minecraft and open that installation’s game directory, shown under Installations > Edit > Game Directory. The usual Windows default is %APPDATA%\.minecraft.
3. Rename the downloaded-pack cache to keep a backup: downloads on Java 1.20.3 and later, or server-resource-packs on older releases. Add -old to its name, then rejoin and let the pack download again.

Minecraft’s 1.20.3 release notes document that folder change. Leave saves and resourcepacks untouched. Rejection for refusing a required pack is expected, not evidence that this fixed the connection.

If a fresh download works, keep it. Otherwise, close Minecraft, move the new cache aside, and restore the original folder name. Restore the original pack preference if disabling it did not help.

6. Test a Separate Vanilla Installation

A client mod can disrupt multiplayer even when the game opens normally. A separate unmodified installation lets you compare without dismantling your modpack.

1. In Installations, create an unmodified installation using a compatible release and a new, empty Game Directory.
2. Test a vanilla-compatible server, not one that requires your modpack.

   

3. If that works, check the affected pack’s required client mods and loader versions against the server’s published pack. Test a copy without recently added optional client mods, keeping required dependencies.

A successful vanilla test does not identify a particular faulty mod. Retry the original server after each mod change, and restore add-ons that make no difference. Keep existing worlds out of the test installation.

7. Lower Render Distance for Disconnects During Loading

Minecraft may let you enter the world, then disconnect as terrain loads. A lower render distance reduces that load and has helped some players keep the connection.

1. Open Options > Video Settings and set Render Distance to 6-8 chunks.

   

2. Pause large downloads or streams competing for bandwidth, then reconnect.

If the world stays connected, increase the distance gradually. This test is unlikely to help a disconnect before login, and it does not establish that your GPU caused the error.

8. Repair the Launcher Only if It Also Malfunctions

Launcher repair is relevant when updates, downloads, or runtime installation also fail. It is not a routine cure for a game that launches normally and disconnects from one server.

1. Close Minecraft and the launcher. Open Settings > Apps > Installed apps > Minecraft Launcher > Advanced options.
2. Choose Repair and test before considering Reset.

   

If Repair restores downloads and the game runs, stop there. If those Windows options are unavailable, follow Minecraft’s installation troubleshooting rather than deleting the game directory.

9. Check Windows TCP Settings Before a Full Network Reset

On Windows, disabled TCP receive-window auto-tuning has been linked to this error in player reports. It controls how much incoming data the connection can receive at once. Check the setting before attempting broader repairs.

1. Open Command Prompt as administrator and run netsh interface tcp show global. Save the output.
2. Only if Receive Window Auto-Tuning Level is disabled and not intentionally managed, run:

netsh interface tcp set global autotuninglevel=normal

Retry the same server. If nothing improves, restore the recorded value; for an originally disabled setting, use netsh interface tcp set global autotuninglevel=disabled.

Leave other TCP settings alone. Microsoft’s netsh reference explains this option.

Reserve network resets for broader connection problems

For persistent Windows networking trouble beyond one Minecraft server, run these commands separately, then restart:

netsh winsock reset
netsh int ip reset resetlog.txt

If that still fails, Microsoft’s network-repair guidance reserves Network reset for the last step.

On Windows 11, open Settings > Network & internet > Advanced network settings > Network reset; on Windows 10, find it under Status.

Select Reset now only when prepared to reconnect and restore your settings afterward. If the same server alone still disconnects, stop repeating Windows resets and collect its error details.

10. Check Logs With the Server Owner or Support

Simultaneous disconnects need server-side investigation. Even one affected player can have a server-side problem, such as a mod error involving that player’s inventory.

1. Note the disconnect time and time zone. From the active game directory, collect the nearby entries in logs/latest.log, your Minecraft/modpack version, and the results of the other-server and network tests.
2. Ask the owner to compare that time with the server and any proxy logs. They should investigate the preceding error, not only the final “connection reset” line.
3. Owners should back up the world and configuration before restarting or testing compatible plugin/mod changes.

A proxy forwards players to the game server. For Velocity, check player-information forwarding and keep the backend protected from direct public connections. Do not disable public-server authentication or delete player data to bypass the error.

If a Realm still disconnects, contact its owner or Minecraft Support with those details. Remove account tokens and private information before sharing logs; keep proxy secrets private.