Project Zomboid server problems

Common Project Zomboid server problems and how to fix them. Settings named here are on your Startup page, see Project Zomboid settings.

Server version mismatch, or players cannot join after an update

Why it happens: The server and each player must be on the same build. Project Zomboid has separate builds (Build 41 and Build 42), and they cannot play together. Even inside one build, patches must match.

How to fix it:

1. Ask players which build they run. In Steam the branch is under the game’s Properties, Betas.
2. On Startup, check Steam Beta Branch (SRCDS_BETAID). The egg’s own note says to name a beta branch there (for example b41multiplayer) or leave it blank for the normal branch. Branch names change as the game updates, so check the game’s Steam page for the current names. Changing it needs a reinstall.
3. Turn on Steam Auto Update (AUTO_UPDATE, set to 1) if you want updates on start. The default is 0.
4. Back up before any reinstall. See Backups. Saves and mods are not always compatible between builds, so open a ticket before switching.

I cannot connect to my server

Why it happens: The server is still loading, or the address and ports do not match.

How to fix it:

1. Wait for status Online. First start can take a while.
2. Use the address and port from the Network page.
3. SteamPort (STEAM_PORT) sets the UDP port, default 16262. Do not change it unless asked.
4. If it works for you but not a friend, see Can’t connect to any game.

Steam connection problems: “Steam not running”, “Connection to Steam failed”

Why it happens: The player’s game could not talk to Steam, or the server is not listed by Steam.

How to fix it:

1. Make sure Steam is running and logged in on the player’s PC.
2. Have players connect by direct IP and port in the Join Server screen instead of the list.
3. Restart Steam and the game.

The server is not in the list

Why it happens: Project Zomboid lists servers by their Steam server list entry, and new servers are slow to appear.

How to fix it:

1. Wait some minutes after Online.
2. Join directly using the IP and port.
3. If the list never shows the server, open a ticket to check the ports.

Mods are not loading

Why it happens: For a workshop mod you need two values in the server settings file: the Workshop item ID (in WorkshopItems) and the Mod ID (in Mods). Missing one means the mod does not load.

How to fix it:

1. Find the Workshop ID from the mod’s Steam page address (the number after id=).
2. Find the Mod ID on the Workshop page, in the description under “Mod ID”. It is text, not a number.
3. Stop the server. In Files, open the server settings file, named after Server Name (SERVER_NAME). It ends in .ini. It is under the Zomboid/Server folder.
4. Put the Workshop ID in WorkshopItems=, separated with semicolons. Put the Mod ID in Mods=, also with semicolons.
5. Some game builds want the Mod ID written a little differently in Mods=. Check the mod’s Workshop page for the exact form, or open a ticket if the mod will not load.
6. Save and start. Players download the mods when they join.
7. We cannot promise that a mod works. Ask the mod author about mod errors.

Mod errors, or players stuck downloading mods

Why it happens: The mod may be for another build, out of date, or need another mod first.

How to fix it:

1. Check the mod page says it supports your build (41 or 42).
2. Install any required mods and put them before the mod that needs them.
3. Restart the server, then have the player restart the game.
4. Remove the mod if the server will not start.

Map mods: order and spawn

Why it happens: Map mods are listed in the Map= line in the server settings file, and order matters. The base map (Muldraugh, KY) must be last.

How to fix it:

1. Stop the server and open the settings .ini in Files.
2. Add each map mod’s folder name before Muldraugh, KY, separated with semicolons, and follow the mod page’s instructions.
3. Also add the mod’s Mod ID and Workshop ID.
4. A new spawn point may need a new character or a fresh world.

Server runs out of memory or lags

Why it happens: Zomboid uses a lot of memory, and more with many mods, players and a large map.

How to fix it:

1. Check the Console for “Out of memory: true”. See Out of memory.
2. Remove mods you do not need.
3. Restart on a schedule: see Schedules.
4. Upgrade if you need more memory.

Admin password, and how to become admin

Why it happens: The first admin account is set with Admin Username (ADMIN_USER) and Admin Password (ADMIN_PASSWORD).

How to fix it:

1. On Startup, set both values.
2. Start the server, then join with that username and password.
3. If you changed the password after the first run, the account may already exist with the old one. Open a ticket, or change it in game with the admin tools.

PVP is off, or players are not able to fight

Why it happens: PVP is a server setting inside the settings file, not a variable on Startup.

How to fix it:

1. Stop the server.
2. In Files, open the server .ini and set PVP=true or PVP=false.
3. Save and start.

Server pauses when empty, or the world freezes

Why it happens: Project Zomboid can pause the world when no player is online, by the PauseEmpty setting.

How to fix it:

1. Stop the server and open the server .ini in Files.
2. Set PauseEmpty=false if you want time to keep moving while nobody is on, or true to pause.
3. Save and start.

Whitelist: players cannot join or new players get kicked

Why it happens: With the whitelist on (Open=false), only accounts you add can join.

How to fix it:

1. Stop the server and open the .ini in Files.
2. Set Open=true to allow anyone, or keep false and add accounts as an admin from in game.
3. Restart the server after editing.

Where are my saves?

Why it happens: Zomboid stores each server’s world under its own name.

How to fix it:

1. In Files, look under the Zomboid folder, then Saves, then Multiplayer, then a folder named after Server Name.
2. Back up that folder with Backups.
3. Do not change Server Name unless you want a new world, since it names the save and settings files.

My settings keep resetting

Why it happens: Some values are written by the panel on each start.

How to fix it:

1. Use Startup for Server Name, Admin, SteamPort.
2. Edit the .ini only when the server is stopped.
3. If a value keeps changing back, open a ticket.

Still stuck?

Open a ticket or ask on Discord. See Contact support.