Minecraft "Mismatched Mod Channel List" Fix (Forge and NeoForge)
Fix "Mismatched mod channel list" and "Mod rejections" when joining a modded Minecraft server by matching the client and server mod lists exactly.
Updated Oct 7, 2026 · 6 min read
On this page
"Mismatched mod channel list" means the mods on your game and the mods on the Minecraft server do not line up: one side has a mod the other lacks, or the same mod in a different version. Forge and NeoForge compare every mod's network channel during the handshake and refuse the join if any required one differs. The fix is to make the two lists match, and the error screen itself tells you which mods to look at.
What the error looks like
Depending on the loader and Minecraft version, the screen says one of these:
Connection closed - mismatched mod channel list
Incompatible FML modded server
Newer Forge and NeoForge builds follow the first message with a list of the channels or mods that were rejected, split into missing and mismatched entries. The second message appears on the multiplayer list, with a red cross over the server icon, before you even click join. Hover the icon and it shows the same differences. The server console also logs which channels it rejected, with words like "rejected", "missing" or "mismatch" on the line.
Read the list carefully. A mod missing on your side means you need to install it. A mod the server lacks means you have something extra. A mismatch means both sides have it, at different versions.
Why Forge and NeoForge are this strict
Each mod that adds blocks, items, entities or its own packets registers a network channel with a version number. When you connect, the server sends its list of channels and the client checks every one. If a mod says it is required on both sides and the versions differ, the handshake stops. This is on purpose: letting a client with a different version of Create join a Create server would corrupt the contraptions and inventories of everyone nearby.
Mods that only change visuals or menus, like a minimap, a shader loader or Just Enough Items, usually mark themselves as optional on the other side, so they do not cause this error.
Fix 1: Use the same modpack version as the server
This is the answer nine times out of ten. Packs like All the Mods, Better MC or Prominence update often, and the launcher may have updated your client while the server is still on last week's build (or the other way round).
- Find the server's pack version. It is in the pack's files on the server, often in
config/or amodpack.json,manifest.jsonorinstance.cfg, or the server owner can check the version they installed. - In the CurseForge app or Modrinth App, open the pack, choose Change version (CurseForge) or the version picker (Modrinth) and select the same one.
- Launch and join again.
If you run the server, it is usually easier to update the server to match what players have. See installing a CurseForge modpack on a server or installing a Modrinth modpack for the server side.
Fix 2: Add or remove the mods named in the list
When it is a hand built mod list instead of a pack, go through the error line by line.
- Missing on your side: download that exact mod version for your loader and Minecraft version and add it to your
modsfolder. - Missing on the server: remove it from your client, or add it to the server if everyone should have it.
- Version mismatch: replace the older file on whichever side is behind.
Keep the server's mods folder as the master list. When you add a mod, add it to the server first, then share the list with players. A simple way to share it is a private modpack on CurseForge or Modrinth, so players install one thing and stay in sync.
Fix 3: Match the loader version
Two players can have identical mods and still fail if the Forge or NeoForge versions are far apart, because some mods declare a minimum loader version. The error then names the loader itself, or the client crashes before reaching the server.
On the server, the loader version is set when the server is installed. On a GamezServers server it is the Exact Forge version or Exact NeoForge version setting in the panel, followed by Update game. On the client, the launcher profile shows it. Match them, or at least make sure both are above what every mod requires.
Fix 4: Client only mods on the server
Not every mod belongs on the server. Installing a client only mod on a dedicated server can crash it on startup or register channels the client never sees. Common client only mods:
| Mod type | Examples | Server? |
|---|---|---|
| Rendering and shaders | Oculus, Iris, Embeddium, Sodium | No |
| Minimaps and HUD | Xaero's Minimap | Usually optional, check the mod page |
| Menus and tooltips | Mouse Tweaks, Controlling, AppleSkin | Optional |
| Content mods | Create, Mekanism, Farmer's Delight | Yes, both sides |
When a modpack offers a separate "server pack" download, use that. The pack author has already removed the client only mods.
Fix 5: Fabric servers
Fabric does not have the Forge channel check, so you will not see this exact message. You get one of these instead:
- A Fabric API registry sync disconnect that lists unknown or missing registry entries (items, blocks or entities). A content mod is missing on one side.
- Players joining and seeing invisible blocks or getting kicked when they open a modded machine. Same cause.
The fix is the same: match the mod list and versions on both sides. The guide on installing Fabric mods on a server covers which mods go where.
How to stop it from happening again
- Pin the modpack version on the server and announce updates before you apply them.
- Turn off automatic modpack updates in the launcher for everyone in the group, or agree to update together.
- Take a backup before every update so you can roll the server back if a new pack version breaks worlds.
- Write the loader and pack version in the server description so players can check at a glance.
On GamezServers you pick the Forge or NeoForge server type, set the loader version in the panel and upload mods through the Files tab or SFTP, with one click backups before each update. If juggling all of that on a home PC is wearing thin, a modded Minecraft server keeps the pack online for the whole group.
FAQ
What does "Mismatched mod channel list" mean?
Forge or NeoForge compared the mods on your game with the mods on the server and found a difference in a mod that must be on both sides. The screen lists which ones.
Do I need every server mod on my client?
Only mods that add content or their own packets. Server only mods, like performance or admin mods, are not needed on the client, and the error will not list them.
Why does it say mismatched when I have the same modpack?
Usually the versions differ by one update. Check the pack version on both sides, then the loader version. A single extra client mod you added yourself can also trigger it.
Can I turn the mod check off?
Not safely. Joining with a different mod version risks corrupting chunks and inventories. Matching versions is the only real fix.
Skip the setup. Your own Minecraft server.
Then $4.99/mo. Just trying it? $1.25 for 3 days