This guide covers common DayZ server issues and how to resolve them, including mod signature errors, server browser problems, XML parsing failures, BattlEye configuration, and RCON remote administration. For general server configuration, see the DayZ Server Setup Guide.

Signature and Mod Errors

Players are kicked with "Signature check timed out" or "No entry in key directory"

• This means a mod's .bikey file is missing from the server's keys/ directory. Check that every mod in your -mod= parameter has its key file copied into keys/.
• If the server has verifySignatures = 2;, all mods must have matching keys. There are no exceptions -- even one missing key will prevent players who have that mod from connecting.
• After adding the missing key file, restart the server. Key changes take effect on restart.
• See the DayZ Mod Installation guide for full details on key file management.

Players are kicked with "Game signature mismatch"

• This occurs when the player's local mod files do not match the server's mod files. Usually caused by one side having an outdated version of a mod.
• Ask players to update their subscribed mods in the DayZ Launcher or Steam Workshop before reconnecting.
• If the server's mods are outdated, stop the server, delete the cached Workshop files for the outdated mod, and restart the server so it re-downloads the latest version.

Server Startup Issues

Server crashes on startup or fails to load the mission

• The most common cause is an XML parsing error in types.xml or another mission file. Check the server console output in GPanel for a line containing xml, parse, or the name of the file that failed to load.
• Download types.xml via SFTP and validate it with an XML editor or online XML validator. Look for unclosed tags, mismatched quotes, or stray characters.
• A mod load order problem can also cause a crash at startup. Try removing all mods from the -mod= parameter and starting a vanilla server first. If the vanilla server starts cleanly, re-add mods one at a time to identify which mod or combination causes the crash.
• See the Loot Economy guide for tips on validating types.xml.

Server not appearing in the DayZ Launcher server browser

• Confirm the steamQueryPort in serverDZ.cfg matches the query port shown in GPanel's Network tab exactly.
• The server browser can take 10-15 minutes to index a newly started server. Use direct connect (Favourites tab in the launcher) to verify the server is reachable while you wait.
• The DayZ Launcher server browser may not list servers with certain filter mismatches. Ensure forceSameBuild = 1; is set in serverDZ.cfg so only players on the correct game version can see and join the server.

Loot and Economy Issues

types.xml changes are not taking effect after restart

• Confirm the file was saved before the server was restarted. Open it in the GPanel file editor after saving to verify the values you entered are present.
• If you are running mods that include their own types.xml entries, those entries may override your changes. Check the mod's db/ folder for a types.xml file and merge your changes into it, or adjust the mod's economy file directly.
• Ensure the path is correct for your map. The types.xml for Chernarus is at mpmissions/dayzOffline.chernarusplus/db/types.xml. For Livonia, it is mpmissions/dayzOffline.enoch/db/types.xml.
• See the Loot Economy guide for full details on editing types.xml.

BattlEye Configuration

BattlEye is the anti-cheat system used by DayZ. It is enabled by default on all servers. The BattlEye configuration folder is located at:

battleye/

Inside this folder you will find filter files such as scripts.txt, remoteexec.txt, and publicvariable.txt. These files define what actions BattlEye flags or kicks players for. Out of the box, BattlEye is configured to catch common cheats. If you are running mods, some mods may trigger false positives and kick legitimate players.

BattlEye is kicking players unexpectedly

• Check the BattlEye log files inside the battleye/ folder. The log will show which filter triggered the kick and the exact string that matched.
• Follow the mod author's recommended BattlEye whitelist instructions. Most mod pages include a section covering required filter adjustments.
• If no mod author instructions are available, temporarily set the offending filter line to 0 (log only) to stop the kicks while you investigate.

Handling BattlEye False Positives from Mods

If players are being kicked by BattlEye after installing mods, check the BattlEye log for the specific filter that triggered the kick:

1. In GPanel, open the Files tab and navigate to battleye/.
2. Open the relevant filter file (e.g., scripts.txt for script violations or remoteexec.txt for remote execution kicks).
3. Each line in the filter file begins with a number indicating the action:

   Value	Action
   0	Log only (no kick)
   1	Log and kick
   2	Log and ban

   Change the number at the start of the offending line to 0 to suppress the kick while you investigate, or follow the mod author's instructions for whitelisting the exception.
4. Save the file and restart the server. BattlEye filter changes do not require editing serverDZ.cfg.

RCON via BattlEye

BattlEye includes a built-in RCON interface that allows remote administration commands without an in-game admin password. RCON is configured in battleye/beserver_x64.cfg.

You can set the RCON port and password directly in GPanel's Startup tab rather than editing the file manually. A minimal beserver_x64.cfg looks like this:

RConPassword yourpassword
RConIP 0.0.0.0

Connecting with an RCON Client

To send remote commands to your server via RCON:

1. Download an RCON client that supports BattlEye RCON (such as BattlEye RCon or DayZ Server Admin Tool).
2. Enter your server's IP address, the RCON port from GPanel's Network tab, and the RCON password you set in the configuration.
3. Connect and use the client to send commands such as kicking players, sending global messages, or restarting the server.

Related Articles

• DayZ Server Setup Guide -- serverDZ.cfg configuration and how players connect
• DayZ Mod Installation -- Steam Workshop mods, load order, and key files
• DayZ Loot Economy (types.xml) -- customising item spawn rates and loot tables
• How to Upload Files via SFTP