Get started

Free trial Try any game free for 3 days. No card needed. Start a free trial Start a free trial

Game servers

All games

Guides / DayZ / Mods

Fix the DayZ mod mismatch and signature kick

Kicked from a modded DayZ server for a mod mismatch or missing signature? Match the mod versions, keep each mod's .bikey in keys, then restart.

Updated , checked on DayZ 1.29

A DayZ server that checks signatures kicks any player whose mods do not match the server’s mods exactly. The usual causes are a mod that updated on one side only, a mod the server has but the player lacks (or the other way round), and a missing .bikey key file on the server. If everyone is kicked right after a mod update, restart the server so it downloads the update. Find the code in the kick message, then use the matching fix below.

Read the kick message

The game shows “You were kicked off the game”, a reason, and often the file it did not like, for example (addons\ai.pbo). It also has a code like 0x0004007E. Bohemia lists the codes. These are the ones about mods:

CodeNameWhat Bohemia says it means
0x00040073VE_MISSING_MODThe client is missing a mod which is on the server.
0x00040074VE_EXTRA_MODThe client has a mod which is not on the server.
0x00040079VE_UM_CLIENT_UPDATEDExtra PBO, most likely because the client has a newer version of the mod.
0x0004007AVE_UM_SERVER_UPDATEDExtra PBO, most likely because the server has a newer version of the mod.
0x00040081VE_M_CLIENT_UPDATEDMissing PBO, most likely because the client has a newer version of the mod.
0x00040082VE_M_SERVER_UPDATEDMissing PBO, most likely because the server has a newer version of the mod.
0x0004007EVE_MISSING_BISIGNThe client has a PBO which is missing a .bisign.
0x0004007DVE_INTEGRITYThe client has a corrupted or modified file.
0x00040075VE_CLIENT_CORRUPTThe client installation is corrupt.
0x00040076VE_SERVER_CORRUPTThe server installation is corrupt.
0x00040092PBO_CLIENT_UPDATEDThe client has a more recent version.
0x00040093PBO_SERVER_UPDATEDThe server has a more recent version.

A player can also be refused before joining, with 0x00020016 (EQUAL_MOD): “Server and client do not have equal mods while server enforces it.” A game version that does not fit the server shows as 0x00010006 (VERSION_MISMATCH): “Your currently installed game version is not compatible with this server.”

A PBO is a mod’s data file. A .bisign is the signature file beside it. A .bikey is the public key the server uses to check those signatures.

In the ArthOS panel

  1. Open Startup and look at Verify Signatures (1). It is on by default (value 2). The panel offers 2 and 0; Bohemia documents only 2, so leave it on. When it is on, players with different mod versions are kicked on connection.
  2. Look at Automatic Updates. With it on, the server checks every Workshop mod listed in Additional Mods, the modlist file and [Advanced] Server-Side Only Mods each time it starts, and downloads the ones that changed.
  3. If the code says the server has the newer version (0x0004007A, 0x00040082, 0x00040093), the player must update the mod in their game launcher. Ask them to subscribe again or choose repair in the launcher.
  4. If the code says the client has the newer version (0x00040079, 0x00040081, 0x00040092), the mod updated on the Workshop after the server last checked. Choose Restart on the Console page. With Automatic Updates on, the server downloads the new version while it starts.
  5. If the code says the client is missing a mod (0x00040073), the player needs to subscribe to it. Share the Workshop link or the mod list.
  6. If the code says the client has an extra mod (0x00040074), the player runs a client mod that the server does not run. They must remove it, or you add it to the server.
  7. If the code is 0x0004007E (missing .bisign), or every player fails the check for one mod, open Files and look in keys. Each mod ships its keys in its own keys folder, inside @<Workshop ID>. The server copies them for you when it downloads a mod. Mods you upload yourself need their keys copied by hand.
The Startup page with Verify Signatures and Enforce Game Version
  1. Verify Signatures
  2. Enforce Game Version

Also check Enforce Game Version (2). When it is on, only players on the same game version as the server can join. After a DayZ update, players on the old version are refused until the server updates too, and the other way round.

By hand

  1. Make the server’s mod files the same as the Workshop’s current files. Replace the changed .pbo and .bisign files, then delete any file in the server’s copy of the mod that is not in the new one. The Expansion mod team explains this step by step in their update guide.
  2. Copy every .bikey from each mod’s keys folder into the server’s keys folder.
  3. Check serverDZ.cfg. verifySignatures = 2; turns the check on. Bohemia documents only 2.
  4. Restart the server.

If it does not work

  • Only one player is kicked. The fault is on their side. Ask them to repair or re-subscribe the mod in the launcher, and to remove mods the server does not run.
  • Everyone is kicked right after a Workshop update. The mod updated before the server did. Restart the server so it downloads the update.
  • Everyone is kicked and nothing updated. Look in keys for the mod’s .bikey.
  • A code about the server being corrupt (0x00040076, 0x00040083). Turn on [Repair] Validate Server Files for one start, with Automatic Updates on, so Steam checks the server files. Then turn it off.
  • A mod on the server needs no key for players. A mod in [Advanced] Server-Side Only Mods runs on the server only. Players do not need it while Verify Signatures is on.

If players see “Client not responding” instead, that is a different problem: see the client not responding kick. More about the game: DayZ servers.

Sources: Bohemia wiki: Error Codes, Bohemia wiki: Server Configuration, github.com: Entrypoint.sh, github.com: [Server Hosting] How to update mods on a DayZ server CORRECTLY, store.steampowered.com: 221100

DayZ serversAll DayZ guides