Game Server Version Mismatch: How to Fix It in Any Game

A version mismatch error means the player's game and the server are on different builds, so the server refuses the connection. Usually the game just updated and either the server or the player has not caught up yet. Update the server (and restart it), have every player restart Steam so their game updates, and make sure both are on the same branch: a player on a beta and a server on the stable build, or the other way round, cannot connect. On modded servers, the mods must match as well.

What the error looks like

The wording varies by game:

• "Incompatible version" or "Version mismatch" (Valheim and many others)
• "Server is running a different version" or "Client version mismatch"
• "Bad version, server rejected connection" (DayZ)
• "Disconnected: outdated client" or "outdated server" (Minecraft)
• "Workshop item version is different than server's" (Project Zomboid)

All of them mean the same thing: two different builds tried to talk.

Step 1: compare the versions

Find the exact version on both sides:

• Server: the console prints the version on startup. Many games also show it in the server list entry.
• Player: the version is usually on the main menu, in a corner of the screen.

If they differ, you know which side to fix.

Step 2: update the server

Game updates come out through Steam, and dedicated servers do not update themselves unless their start script runs SteamCMD. Stop the server and update it:

steamcmd +force_install_dir /home/steam/server +login anonymous +app_update <server_appid> +quit

Then start it and check the version in the console. If the update fails with a state code, see 0x202, 0x402 or 0x602.

On patch day, Steam sometimes makes the client update available a little before the server update, or the other way round. If the server says it is up to date and players are on a newer build, wait a short while and update again.

Step 3: update the players

Players who leave Steam running for days may not have the update yet.

1. Restart Steam completely (Steam menu, Exit, then open it again).
2. Check the Downloads page for a pending update.
3. If the game still shows the old version, right click the game, Properties, Installed Files, Verify integrity of game files.

Xbox, PlayStation and Game Pass players get updates through their own stores, which can arrive at slightly different times. On crossplay servers, a mismatch right after a patch often clears within hours as every platform catches up.

Step 4: check the branch

Branches are the most overlooked cause. If the server runs an experimental or public test branch and a player is on the default branch (or the other way round), they can never connect.

• Player side: in Steam, right click the game, Properties, Betas, and check what is selected.
• Server side: check your SteamCMD command or panel for a -beta option.

Both must match exactly. See how to install a beta branch on a dedicated server.

Step 5: check mods

On modded servers, the game version can match while a mod version does not. Typical cases:

• Steam Workshop mods updated but the server still has the old copy. Restart the server so it downloads the new version.
• Valheim with BepInEx: mods with version checks kick players whose mod versions differ. Everyone needs the same modpack, ideally shared through a mod manager profile.
• Minecraft modpacks: the client needs the same loader version and mod versions as the server. See Minecraft mismatched mod channel list.
• Project Zomboid: a Workshop mod updated after the server started. Restart the server. See workshop item version is different than server's.
• DayZ: mod keys and versions must match the client. See bad version, server rejected connection.

Step 6: rule out a half updated server

If the server reports the new version but players still get mismatches, the server install may be partly updated. Run the update once more with validate, which checks and repairs every file. Our guide to app_update validate explains what it changes and what to back up first.

Also check you are running the folder you updated. If your start script points at a different install than SteamCMD's force_install_dir, you updated one copy and started the other.

When players are ahead and you want to stay behind

Sometimes the new version breaks your mods, and you would rather keep the server on the old build for a while. Some games offer older version branches for this. 7 Days to Die, for example, publishes previous versions as Steam branches, and Project Zomboid kept a legacy41 branch for Build 41. Players then select the same older branch in Steam. Games without version branches cannot be rolled back this way.

Game specific guides

For step by step fixes in particular games, see 7 Days to Die version mismatch, how to update a Valheim server after a game patch and how to update a Palworld server.

Patch day without the scramble

On a GamezServers server you can update and restart from the control panel and watch the version in the live console. Where a game offers branches, such as 7 Days to Die versions or Valheim's public test, you choose them in the panel too. Take a one click backup before big updates.

FAQ

What does version mismatch mean on a game server?

The player and server are on different game builds. One of them needs updating, or they are on different branches.

How do I fix version mismatch after an update?

Update the server and restart it, then have players restart Steam so their game updates. Check both are on the same branch, and update mods on both sides.

Why do I get version mismatch when my game is up to date?

The server may not be updated yet, or one side is on a beta branch. On modded servers, a mod version can differ even when the game matches.

Can I play on an old version with my friends?

Only if the game offers older versions as branches, and everyone, server included, selects the same one.