Minecraft Internal Exception: java.net.SocketException: Connection reset means the network connection between your Minecraft: Java Edition client and a multiplayer server was unexpectedly reset. It does not identify the culprit by itself. The interruption may originate from your Wi-Fi or router, a VPN or security filter, the internet route, a proxy, or the server. The most reliable fix is to find out which side is failing before changing Java settings or opening ports.
Start here: Rejoin once, try a different Java Edition server, close Minecraft completely, and restart your computer. If the problem continues, move through the checks below in order. These instructions focus on Java Edition multiplayer, including the 1.21 generation of releases; Bedrock Edition has different networking and error messages.
A socket is a network connection used to exchange data. The Java exception reports that an established connection was reset while Minecraft was using it. A reset can be caused by an endpoint or a device in between; the error screen alone cannot establish whether a particular server intentionally kicked you. Sometimes it appears while joining, sometimes after loading chunks, and sometimes after several minutes of apparently normal gameplay.
The phrase “Link Lapses” is not a separately verified official Minecraft Java error code. If you encounter that wording in a forum or launcher description, use the actual on-screen exception and the client/server logs to diagnose the disconnect.
| What happens | Most useful first test | Likely area to investigate |
|---|---|---|
| Only one server disconnects you | Join another server using the same client | That server, proxy, plugins, or version requirements |
| Every server disconnects on home Wi-Fi | Try Ethernet or a trusted phone hotspot | Local network, router, ISP route, or security software |
| Modded profile fails but unmodded works | Launch a clean, matching game version | Mods, loaders, or custom Java configuration |
| Multiple players disconnect at the same time | Ask the admin to compare server logs | Server resource load, hosting network, or proxy |
In Minecraft: Java Edition, open Multiplayer and attempt to join a different compatible server. You can use Direct Connection to enter a known, trusted server address. Make sure the server is actually online and supports the Minecraft version you are launching. The official Minecraft guide to joining Java servers documents the available connection methods.
If only one destination fails, ask its administrator whether there is maintenance, a proxy issue, a recent update, or a required modpack. If every destination fails, continue with the checks on your device and network. Also compare whether friends on other networks can join the same server.
Quit the game and launcher fully, restart your computer, and reconnect. Pause large downloads, cloud backups, or streaming on your network while testing. If other devices are also losing connectivity, restart your router using its normal power cycle; do not perform a factory reset. A network speed test can reveal a general outage, but a high download speed does not rule out packet loss or brief dropouts.
Reconnect and note the time and circumstances of the failure. A disconnect that always occurs shortly after joining is different from one that happens only when the household connection is busy.
Use a wired Ethernet connection if possible. If Ethernet works but Wi-Fi fails, investigate wireless signal, interference, and router settings before changing Minecraft. As a diagnostic test, you can briefly connect a computer to a trusted mobile hotspot. Follow your carrier's data limits and avoid exposing a self-hosted server through the hotspot.
A VPN is not an automatic fix. If you already use one, disconnect it for a controlled comparison. A VPN can change routing, but may also introduce latency or blocked traffic.
On Windows 10 or 11, open Windows Security > Firewall & network protection > Allow an app through firewall. Inspect rules for the actual Java runtime used by Minecraft, not just the launcher. The executable is often named javaw.exe, but its location depends on the launcher and installation. If a trusted executable is being blocked, allow that specific application on the appropriate network profile, then retest.
Do not permanently disable Windows Firewall or antivirus software, and do not indiscriminately open inbound ports on a computer that is merely joining a remote server. Microsoft's Windows Firewall documentation explains the protection provided by app- and network-specific rules. For third-party security suites, review connection-blocking logs and use their vendor's documented allowlist procedure.
In the official Minecraft Launcher, use an unmodified release installation that matches a server version it supports. If that connects reliably while a Fabric, Forge, NeoForge, or custom-client profile disconnects, the comparison points toward a mod, loader, resource-related customization, or its network compatibility. Update the components from their official project pages, and temporarily remove optional mods from a copied profile to isolate the offender.
Do not delete a working .minecraft folder or your saves as a first troubleshooting step. Make backups before editing a modpack or player data. A version mismatch often generates a more specific message, so treat a matching version as a baseline test rather than a guarantee.
The official launcher normally handles the Java runtime needed by its supported release. Installing a separate Java version or raising the memory limit is not a general remedy for a TCP connection reset. If you changed the Java executable manually, restore the launcher-managed default and retest. For third-party launchers, verify the chosen runtime against the game's and mod loader's documented requirements.
For self-hosted Paper servers, requirements depend on the actual server release: the current PaperMC Java compatibility table lists Java 21 for Paper 1.20 through 1.21.11 and Java 25 for the 26.1 generation. Do not assume Java 21 is the correct choice for every newer release. Check the server console for a version or startup error instead of changing client JVM arguments blindly.
If a server hostname no longer resolves correctly, reconnecting by the administrator's confirmed address or refreshing the local DNS cache can help diagnose the issue. Close Minecraft, open Command Prompt, and run:
ipconfig /flushdnsThis clears the Windows DNS resolver cache; it does not repair packet loss or stop every in-session reset. See Microsoft's ipconfig reference for the command's exact purpose.
Use netsh winsock reset only as a later Windows-specific repair when other applications also show networking problems and you have ruled out simpler causes. Run it from an elevated Command Prompt, record any custom network software settings, then restart Windows. Microsoft's Winsock documentation explains that it restores the Winsock catalog; it is not a Minecraft-only switch.
When a disconnect repeats, open the Java Edition game directory and look at logs/latest.log after the failure. On standard Windows installations the game directory is commonly under %APPDATA%\.minecraft; custom launcher instances can use different locations. Note the exact error text, time, game version, server address or name, and whether it happened during login or ordinary play.
Share the relevant excerpt with the server administrator, who should compare it with logs/latest.log and console output on the server at the same moment. Redact access tokens, IP addresses, account identifiers, and other private details before posting logs publicly. A Connection reset by peer line is a symptom; adjacent messages can reveal whether a proxy, a plugin, a timeout, or a failing backend was involved.
Before changing production configuration, stop the server and back it up. PaperMC's basic troubleshooting guide recommends inspecting stack traces and checking plugins systematically. Test with a known-good configuration or a staging copy rather than deleting every plugin or modifying live world files.
server-port=25565 is a typical default, and the game connection uses TCP. Confirm the actual value in server.properties; a custom port, host firewall, proxy, or managed provider can require different setup. The Paper server.properties reference documents these fields.view-distance, network-compression-threshold, or max-tick-time without evidence can hide a problem or create another one. Record baseline values and test changes individually.Players who only connect to a public server generally do not need to forward TCP 25565 or any UDP port on their home router. Port forwarding is relevant when accepting inbound connections to a server you operate; it should be configured narrowly and only when necessary.
Use the result of your comparisons, rather than repeating the same generic reset commands. If the failure follows one server, provide the admin with timestamps and logs. If it follows your home network but disappears on Ethernet or a hotspot, focus on router firmware, ISP support, and the route to that server. If it follows only one modded profile, work back from a clean installation while adding components gradually. If it affects multiple games and websites, troubleshoot the computer's wider network stack.
For broader official instructions, consult Minecraft's multiplayer connection guidance. There is no documented universal success rate or permanent one-click cure for Internal Exception: java.net.SocketException: Connection reset: a durable fix depends on identifying where and why the connection breaks.
No. A reset indicates an established network connection was forcibly closed or reset; a timeout generally means an expected response did not arrive within the allowed period. Both can involve network or server faults, but they are different symptoms.
Not by itself. Extra memory may help a genuinely memory-starved game or server, but it does not repair an unstable network path. Change memory settings only when logs or performance metrics point to memory pressure.
Usually not. First test another server, another network, and an unmodified profile. Reinstallation risks losing custom settings or saves if backups are neglected, while a separate Java install may have no effect on the official launcher's bundled runtime.
Fix Fortnite texture pop-in on PC with official steps for GPU drivers, file verification, DirectX 12, high-resolution textures, VRAM, SSDs, and stutter.
Learn what Heroes of the Storm minimap size and position options are verified, improve readability, and choose camera-click controls that suit you.
Set Super Smash Bros. Ultimate Quickplay to prefer hazards-off stages. Follow the Preferred Rules menu steps and learn why matchmaking may not always honor them.
Enable Server Latency and Packet Loss in Warzone to monitor connection quality, read the overlay, and use recurring spikes to guide troubleshooting.
Learn how to carry from mid lane in League of Legends by setting up waves, choosing safe roam windows, reading side lanes, and converting pressure into objectives.
Fix Minecraft Evoker spell problems with a safe vanilla test, version checks, log review, and a step-by-step way to isolate mod or datapack conflicts.
Fix PUBG stuck on Initializing on Steam with a focused checklist for PC service notices, launch options, game files, downloads, and connection issues.
Fix Brawl Stars stuck at 92% loading with an ordered checklist for service notices, network tests, safe updates, Android cache, and account-safe reinstalling.
Best Dead by Daylight visual filter settings start with a small Gamma lift, neutral color and contrast, and a quick check for dark corners, fog, and bright lights.
Find the Steam and EA app fields for Apex Legends launch options, use EA’s documented FPS command, and see why +exec autoexec.cfg remains unverified.
