# “Network Protocol Error” in Minecraft: what it means and how to fix it

> Why Minecraft kicks you from a server with “Network Protocol Error”, how to read the report the game saves and how to fix it, as a player or as an admin.

Original page: https://napnodes.com/en/guides/minecraft-network-protocol-error · Updated: 2026-11-11

You join the server, or you've been playing for a while, and the disconnect screen just says “Network Protocol Error”. It isn't your internet connection: your game has received something from the server that it can't read. It's almost always a mod or a plugin, and the game itself saves a report that says which one. Here's how to find it and what to do, whether you play or run the server.

## What “Network Protocol Error” means

Your game and the server talk with short messages, packets, with a fixed format for each version. Since 1.20.5, when the game receives one that doesn't fit (a piece of data is missing, there's one too many, or it's about something your game doesn't know), it cuts the connection and shows “Network Protocol Error”. In earlier versions you got a long line with `io.netty.handler.codec.DecoderException` instead, which means the same thing.

That's why a cable or restarting the router won't fix it: even with a perfect connection, the packet will keep arriving just as wrong. The useful clue is in the report the game saves, and it almost always points to one of three things: the mods aren't the same in your game and on the server, a mod has a bug, or a server plugin is out of date after an update.

Don't confuse it with “Timed out” or “Connection Lost”, which really are network cuts ([why the server kicks me](https://napnodes.com/en/guides/minecraft-kicked-from-server)), or with “The server sent an invalid packet”, which is the server talking about you rather than the other way round.

## The report: “Open Report Directory”

In recent versions, the error screen has an “Open Report Directory” button. It opens the `debug` folder of your Minecraft (inside `.minecraft`, or inside the instance folder if you use CurseForge, Modrinth or Prism), and in it there's a text file that starts with `disconnect-` and ends with `-client.txt`, with the date and time of the cut.

Open it in Notepad. You don't need to understand all of it: look for the lines starting with `Caused by` and, below them, the ones starting with `at`. Each `at` line carries the name of a code package, and the ones from mods usually have the mod's name in them (something like `com.author.modname`). The first name that isn't Minecraft (`net.minecraft`) or the network library (`io.netty`) is almost always the culprit.

If the server has mods, also look at the server's “Console” at the same time: the real error is often there and your game only sees the consequence.

## 1. Different mods in your game and on the server

It's the most common cause on Fabric, Forge or NeoForge servers. It's enough for you to be missing a mod the server has, to have another version of the same mod, or for your Minecraft to be a different version from the modpack's, for a packet from the server not to fit in your game.

The fix is to have exactly the same: the same Minecraft version, the same loader and the same mods in the same versions. If the server uses a modpack, install that modpack with its app (CurseForge or Modrinth) instead of gathering the mods by hand ([how to join a modded server](https://napnodes.com/en/guides/join-modded-minecraft-server)). If someone has updated a mod on the server, all of you have to update it too.

On NapNodes, the play page of each modded server (napnodes.com/jugar/ plus its identifier) has the player-side modpack ready to download, and it rebuilds itself whenever whoever runs the server installs or removes a mod. If you get the error after a change on the server, download it again from there.

## 2. A mod with a bug

Sometimes the mods are the same on both sides and it still happens, always when doing something specific: opening a modded chest, entering an area, seeing a certain creature. It's a bug in the mod itself, and the report usually names it.

First, check whether the mod has a newer version for your Minecraft version: these bugs are often fixed in the next one. If there isn't one, whoever runs the server can remove it from the server (and everyone from their game) or go back to the earlier version that worked. When the report doesn't make it clear, search by halves: remove half the mods on a test copy and see whether it still happens ([mod errors on the server](https://napnodes.com/en/guides/minecraft-server-mod-errors)).

There are mods that only stop the game from disconnecting you with this error. They don't fix it: the packet keeps arriving wrong and whatever was failing keeps failing, just without a warning. Only use them if there's no other way out, knowing that.

## 3. On a plugin server: something went out of date after updating

On a Paper server without mods, players without mods can get it too. It's usually after updating the server to a new Minecraft version: plugins that build or change packets on their own (ProtocolLib, PacketEvents, ViaVersion, Geyser and the ones that depend on them, such as holograms, NPCs or anti-cheats) have to be on the version made for the new one. If they stay on the old one, they send packets in the old format.

The fix is to update those plugins. On NapNodes, in “Mods & plugins” → “Installed”, remove the plugin and install it again from the search, which downloads its latest version made for your server's version; then “Restart”. If it's the Bedrock one, “Turn off Bedrock” and “Turn on Bedrock” download the new Geyser. If its author hasn't marked it for the new version yet, the panel warns you when installing: if the error keeps appearing with it, you'll have to wait or remove it for a while.

Before updating the server, make a backup: with it you can go back if something isn't ready ([how to update without losing the world](https://napnodes.com/en/guides/update-minecraft-server-version)). And if the error only appears for people joining with another game version, it's down to ViaVersion ([joining with another version](https://napnodes.com/en/guides/viaversion-minecraft-server)).

## Step by step for players

1. **Ask whether it happens to the others**: If it only happens to you, it's your game: your mods or your version. If it happens to everyone, it's the server and whoever runs it has to look at it.
2. **Check the version**: In the launcher, the Minecraft and loader versions have to be the server's (or the modpack's).
3. **Open the report**: “Open Report Directory” and the latest `disconnect-…-client.txt` file: look for the first name that isn't `net.minecraft` or `io.netty`.
4. **Match the mods**: Reinstall the server's modpack as it is. If you play without a modpack, remove the mods the server doesn't have (performance or visual ones usually work, but try without them).
5. **Send the report to whoever runs the server**: If it keeps happening, send them the whole file and the time it happened: with that and the server's “Console” they'll find the mod or plugin.

## Questions

### What does “Network Protocol Error” mean in Minecraft?

That your game received a packet from the server that it can't read, and cut the connection. It isn't an internet problem: it's almost always different mods in your game and on the server, a mod with a bug or an outdated plugin after a server update.

### Where is the error report?

In the debug folder of your Minecraft (or of the instance), in a file that starts with disconnect- and ends with -client.txt. The “Open Report Directory” button on the error screen takes you there.

### Does restarting the router fix it?

No. The packet arrives whole; what fails is its content. You have to match the mods or update the mod or plugin that sends it.

### Why do I get it after updating the server?

Because some plugin that handles packets (ProtocolLib, PacketEvents, ViaVersion, Geyser) or some mod is still on the old version. Update it to the one made for the new version, or remove it until there is one.

### Is it the same as “Error de protocolo de red”?

Yes. “Error de protocolo de red” is the same message with the game in Spanish.

---

NapNodes gives you a free Minecraft server, no card and no end date: it isn't always on (it switches itself off after an hour with nobody on, and you start it again with one click). How it works: https://napnodes.com/en/free. Paid plans, always on and with no commitment: https://napnodes.com/en/pricing.
