Skip to main content
If your Project Zomboid server is not starting, check four things in this order: a No space left on device error from backups on start, a plan with too little memory for Build 42, a wrong name in Map, and a broken or Build 41 mod. Read the last lines of the Console or open Logs to see which one it is, then use the fix below.

​
How to find the error

1

Watch the console

Click Start and watch the Console. The last lines before it stops usually name the problem.
2

Open the game's logs

Project Zomboid writes its own logs to .cache/Logs. Open that folder in Files and open the newest log to read the full error.

​
Fix 1: No space left on device

Backup when the server starts copies and zips the save into a small temporary folder every start. After a few days the server stops starting with “No space left on device”.
1

Turn off the start backup

Open Game settings. In the warning Backups on start can fill the temporary space, click Turn it off, or switch off Backup when the server starts in the Backups section.
2

Save and start

Click Review and save, save and start the server.
3

Use panel backups instead

Set daily backups on Automatic backups. See automatic backups.
If it still says “No space left on device”, open a ticket.

​
Fix 2: Out of memory during start-up

The server sets Java’s maximum memory (-Xmx in ProjectZomboid64.json) from your plan’s memory at every start, so you don’t need to edit it, and a value you edit is overwritten. In our tests, a 2 GB plan (1024 MB for Java) did not finish starting Build 42, so we recommend at least 4 GB for Build 42. If the server stops while it loads the world, remove mods you added recently, or upgrade your service to a plan with more memory and restart. See RAM allocation for how much Java gets on each plan.

​
Fix 3: Wrong map name

A wrong map name stops the server from starting. Open Game settings > Mods and map, set Map back to Muldraugh, KY, save and start. Map mods add their name before Muldraugh, KY, spelled exactly as on the mod page.

​
Fix 4: A broken mod

1

Remove the last mods you added

In Game settings > Mods and map, remove the mod ids and Workshop items you added last.
2

Start the server

If it starts, add the mods back one at a time to find the broken one.
3

Check the build

Make sure each mod supports Build 42. See Workshop mod errors.

​
Still not starting?

Restore a backup from before the problem: open Backups, click Restore and confirm. If you need help, click Share log in the Console, create a link and open a ticket with it. Passwords, keys and IP addresses are removed from shared logs automatically.

​
Frequently asked questions

​
Why does Game settings say the settings file doesn’t exist?

The server hasn’t finished a first start yet. Start it once so it creates its settings files, then come back.

​
My server starts but nobody can join. Is that the same problem?

No. Check the address, the server password and that players run Build 42. See getting started.

​
I changed Server Name and my world is gone. What happened?

Server Name is the internal name of the save and config files. A new name starts a new world with new settings. Change it back to the old name and restart to get your world back.

Project Zomboid guide

Every Project Zomboid page in one place.

RAM allocation

How much memory Java gets.

Workshop mod errors

Mod mismatches and broken mods.

Read server logs

Find the error in your logs.
Tested by the FREAKHOSTING team on 30 October 2026 (Project Zomboid Build 42 on our Game Panel). Steps may differ slightly if the game or its mods change.

​
Need Extra Help?

If you encounter any issues, our support team is ready to assist:

​
Save on Your Hosting

Ready to upgrade your hosting? Use code KB20 at checkout for 20% off your first order!
Last Updated: October 2026