Forge Server Tools · every failure mode · guides

Mod rejections connection closed Minecraft

Players are being kicked for a mod mismatch — ERROR

What this actually means

The client's mod set doesn't match the server's for mods that register a network channel. Any version difference on a networked mod is enough.

How to fix it

The listed mods must be the SAME VERSION on both sides. If you updated a mod on the server, everyone needs the same jar. A running client keeps the jar it launched with, so players must fully restart the game, not just reconnect.

How to be sure it is this

The kick message lists exactly what disagreed.

What it gets mistaken for

Same mod, different version is by far the most common cause and reads like 'both have it, so it should work'. Versions must match exactly.

What to do next

Bump the pack version so launchers force the update instead of trusting people to re-download. Full detail in mod-mismatch kicks.

What it looks like in your log

Search your crash report or latest.log for any of these:

Mod rejections
Incompatible mod set
Connection closed - mismatched mod channel list

The free edition covers the eight most common startup failures, and this is not one of them — it is in the paid tool, which checks all 24 and names the mod jar from the stack trace. The fix above is the same one it prints, so you do not need it to solve this.