Project Zomboid: Reading Server Logs & Debugging
When your **Project Zomboid** server crashes or refuses to start, the answer is always hidden in the logs. However, PZ generates multiple log files, and knowing which one to read is half the battle. This guide will help you interpret `console.txt`, `server-console.txt`, and identify common crash causes.
1. server-console.txt
The **most important** log. It contains the raw output from the server executable, including startup errors, port binding issues, and "Out of Memory" warnings.
2. console.txt (in Logs.zip)
Located deep in the /Zomboid/Logs/ zip files. This detailed log breaks down every single action the Lua script engine takes. Essential for debugging specific mod errors.
3. Kick Reason Logs
If a player is kicked, look for the user_log or safety_log. These often detail Anti-Cheat flags like "Type 12" (Lua Checksum Mismatch).
How to Access Logs via File Manager
- Login to your **Supercraft Control Panel**.
- Navigate to the File Manager.
- Go to the root directory
/server-data/(or just/depending on setup). - Open
server-console.txtto see the latest session. - For deeper history, go to
/Zomboid/Logs/and unzip the archive with today's date (e.g.,15-05-24_12-00-00_DebugLog-server.zip).
Common Error Messages & Fixes
| Error Message | The Meaning | The Fix |
|---|---|---|
Terminated (Exit Code 137) | The server ran out of RAM. The Operating System killed the process to save resources. | Reduce the number of mods, or Upgrade your RAM plan. |
Workshop Item Version Mismatch | Steam Workshop sync failed. | Delete the /steamapps/workshop/content/108600/ folder and restart to force a re-download. |
unknown location "9999,9999,0" | A player is trapped in a corrupted chunk (Void). | Use the admin database to manually teleport that player's coordinates back to a safe zone (e.g., 10800, 10800, 0). |
java.net.BindException: Address already in use | The Port (16261) is blocked. | Your server might be "stuck" running in the background. Kill the process or contact support. |
Expert Tip: When reading logs, pay attention to the STACK TRACE. If you see an error mentioning a specific mod file (e.g., BritaWeapon.lua:42), that mod is almost certainly the culprit. Disable it to restore stability.
Debug like a developer. Host your Project Zomboid server with Supercraft and utilize our live console viewer for instant error tracking and diagnostics.