Project Zomboid Server Crashes: Common Causes and Fixes
A crashing server almost always has a specific, findable cause — it's rarely random. Here are the five we see most often, what each one actually looks like, and what fixes it rather than just working around it.
Out of memory on a heavily modded server
Symptom: Server becomes unresponsive or exits during play, more likely a few hours into a session rather than on startup.
Each mod adds to the server's memory footprint, and a handful of large mods together can push a small plan past its limit faster than any single one would suggest. If this happens repeatedly on a modded server, the fix is more RAM, not a config change — move up a tier rather than continuing to add mods to a plan that's already at its ceiling.
Backup writes running out of scratch space
Symptom: A backup silently fails, or the server briefly hangs around the time a scheduled backup runs.
We found and fixed a real instance of this: Project Zomboid's own backup process writes temporary scatter files to the container's fast, small scratch storage by default, and a large enough world can exceed that space mid-backup. Our servers route this to a larger volume instead, so this failure mode shouldn't occur on Zeros Host — worth knowing about if you've hit it hosting elsewhere, or if a backup ever looks incomplete.
A mod built for the wrong build
Symptom: Server fails to start after adding a mod, or starts but the mod's content is missing.
Project Zomboid's mod folder structure differs between Build 41 and Build 42 — a mod built for the wrong one doesn't just misbehave, it doesn't load at all, and can sometimes cause the server to fail startup if the mod list references something the build can't resolve. Remove the mod and confirm the server starts clean, then check the mod's Workshop page for an explicit build-42 statement before re-adding it. See our Build 42 mod compatibility guide for the specifics.
Improper shutdown corrupting the active save
Symptom: World fails to load on next start, or loads with visibly missing recent changes.
Project Zomboid writes save data periodically, not continuously — killing the process abruptly (rather than a graceful stop) can catch a save mid-write. Always stop the server through the panel's power controls rather than force-killing it. If a save does end up corrupted, automatic backups with integrity checks mean you're recovering from a recent backup, not starting over.
Under-provisioned plan for the player count
Symptom: Server runs fine solo or with one player, but struggles or crashes once several people are on at once.
Our Starter tier is tested to start and run stably, but not specifically load-tested with an active multi-player session — it's a fair fit for a solo or very small private server, not a group that's regularly online together. If you're seeing instability that only shows up with several players connected, that's the tier being under capacity for the load, not a bug to chase — Standard or Pro give the headroom a group actually needs.
See exactly what happened, straight from the panel
Console output and logs without SFTP, automatic backups with integrity checks. Try it free for 24-hour, no credit card required.
Frequently asked questions
My server crashed once — is that normal?
An isolated crash can happen for reasons outside anyone's control (a specific mod interaction, a corrupted individual asset). What's worth investigating is a repeated pattern — the same crash under the same conditions is a real cause to track down, not bad luck.
How do I check server logs to find out what actually happened?
Your panel gives you direct access to the server console output and log files without needing SFTP or a separate log viewer. Check the console around the time of the crash for the last few lines before it stopped — that usually points at what was happening (a specific mod, a specific action) right before things went wrong.
Does a crash lose my world progress?
Not if backups are working as expected — Project Zomboid servers on Zeros Host back up automatically on a schedule with integrity checks, so a crash costs you the time since the last backup, not the whole world.
Will upgrading my plan fix a crash caused by a bad mod?
No — if the crash is caused by a specific mod being broken, incompatible with your build, or genuinely buggy, more RAM does not fix that. Removing or replacing the mod is the actual fix. More RAM only helps if the underlying cause was genuinely running out of memory.