Project Zomboid Dedicated Server FAQ and Fixes
Project Zomboid spreads one named server across an INI, sandbox options, spawn regions, Workshop metadata, a player database, and the world save. A mismatch between those pieces can affect only modded players or prevent the server from finishing initialization. Diagnose by server name and preserve the whole matching set. Note whether the host and clients use Build 41 or Build 42 before changing a save, database, Workshop ID, or branch selection.
Read this before changing anything
Use native console save and quit, then copy the owner-named Server files, Multiplayer save, matching database, backups, logs, and mod records before changing build branch, server name, cache root, or Workshop list.
6 common problems
Match the symptom. Make it right.
Open the answer that sounds like your server. Start at the top of its checklist and stop as soon as the server is healthy.
01VersionsIs Build 42 still unstable-only?
What players see
An old setup guide tells the owner to select unstable for every Build 42 server.
What happened
Build 42.20 moved to public Stable on July 29, 2026.
Why it happened
Search results and host templates can retain pre-Stable instructions.
What to do next
- 1Record the exact current Stable point build before installation.
- 2Use legacy branches only for a matching recovery/world requirement.
References[b42-release]
02MigrationWhy did the server create a new world after I copied the old one?
What players see
The destination starts fresh despite an existing Multiplayer folder.
What happened
The process likely selected a different server name or cache root.
Why it happened
Those arguments tie together configuration, save, and account database identity.
What to do next
- 1Stop and compare the source/destination startup arguments.
- 2Restore all owner-named components and launch with the exact source name/root.
References[pzwiki-server]
03NetworkingDo I need one UDP port per Project Zomboid player?
What players see
An older guide asks for a large sequential range.
What happened
Current official networking uses UDP 16261 and 16262 for the documented primary/direct paths.
Why it happened
Old networking architecture produced persistent outdated port advice.
What to do next
- 1Use the current generated settings and official networking reference.
- 2Forward the two required UDP ports to the reserved server address and test externally.
References[network-update][pzwiki-server]
04ModsWhat is the difference between WorkshopItems and Mods?
What players see
A numeric Workshop ID was copied into both settings.
What happened
WorkshopItems asks Steam for content; Mods tells Zomboid which internal mod IDs to load.
Why it happened
One Workshop page can contain one or more differently named internal mods.
What to do next
- 1Copy the numeric item ID only to WorkshopItems.
- 2Copy every required internal ID to Mods in dependency/load order, then test a backup copy.
References[pzwiki-settings]
05RecoveryCan I open my Build 41 world in current Stable Build 42?
What players see
A long-lived Build 41 world needs a server update.
What happened
The official release plan treats Build 41 and Build 42 save data as incompatible.
Why it happened
Build 42 changed map/world systems beyond an ordinary point update.
What to do next
- 1Keep an immutable Build 41 cache snapshot.
- 2Run that world on a compatible legacy41 branch unless a future official migration path applies.
References[b42-plans][b42-release]
06BackupIs Saves/Multiplayer enough to move accounts and administrators?
What players see
The map returns but users, whitelist, or access levels do not.
What happened
The owner database and configuration were omitted from the migration.
Why it happened
Accounts and privileges live outside the world-chunk directory.
What to do next
- 1Stop and restore db/<servername>.db from the same snapshot.
- 2Restore the owner-named Server family and verify the exact server name before reopening.
References[pzwiki-server]
Step-by-step troubleshooting
Complete Project Zomboid server fixes
Use these focused guides when the short answer matches your symptom and you need the full diagnostic path.
A long-lived Build 41 world or its mods fail, reset, or show incompatible map behavior after the server moves to current Stable Build 42.
Project Zomboid Build 41 World Opened on Build 42
Protect and recover a Project Zomboid Build 41 server after it was pointed at current Stable Build 42 binaries.
Read the complete fix →
The destination starts a clean map or asks for new accounts even though the source Multiplayer save was copied to the new PC or host.
Project Zomboid Server Creates Fresh World After Move
Recover a Project Zomboid server when a changed server name or cache directory hides the imported world and accounts.
Read the complete fix →
Steam downloads a Workshop item, but the dedicated server reports a missing mod, ignores it, rejects joining clients, or loads the world without expected mod content.
Project Zomboid WorkshopItems and Mods Mismatch
Fix Project Zomboid mods that download from Steam but do not load because Workshop item IDs and internal mod IDs differ.
Read the complete fix →
Official references
Built from current game guidance
Last reviewed 2026-08-30. Game behavior changes, so official sources win when a new patch changes an option.
Project Zomboid and its artwork are the property of their respective owners. Gone Wrong Servers is independent third-party software.
Can your friends play tonight?
Free gives you the complete server: guided install, settings, connection help, manual operation, mods, backups, and recovery. Pro adds Guardian, scheduling, safe automatic updates, advanced recovery, and concurrent servers.