Project Zomboid Server Stuck on "Initializing" — The Full Fix Checklist
You hit Connect, the loading screen says Initializing, and 60 seconds later you're either still on that screen, get kicked back to the menu, or see "Connection lost." This page covers every cause we've seen for the Project Zomboid stuck on initializing bug, in roughly order-of-likelihood, with a fix for each.
Quick triage: 70% of the time it's a mod mismatch. 15% is a Steam Workshop subscription not yet downloaded. 10% is server-side overload. 5% is everything else. Run through the checks in order and one of them will land.
1. Mod Mismatch (Most Common)
The single biggest cause. The server has a different mod set, mod order, or mod version than your client. PZ doesn't error cleanly — it just stalls on Initializing.
Diagnose
- Open the server's
servertest.ini(or your named ini). Compare theWorkshopItems=andMods=lines against your client's Workshop subscriptions list in Steam. - Check the order.
Mods=order in the .ini must match the load order on the client.
Fix
- Have every player Steam-subscribe to the exact same Workshop items in the server's list.
- Wait 1-3 minutes for Steam to download. Big mod packs (Brita's, Eerie Country) can take 5+ minutes.
- Clear PZ's mod cache: delete
~/Zomboid/mods-cache(Linux) or%USERPROFILE%\Zomboid\mods-cache(Windows). The client redownloads cleanly on next launch. - Verify mod versions on Workshop haven't auto-updated since the server was set up — pinned servers fall out of sync when an unpinned client updates.
2. Steam Workshop Hasn't Downloaded Yet
You subscribed to the right mods, but Steam is silently downloading them in the background and PZ doesn't wait. Result: client thinks it has the mod, but the actual files are still in transit.
Fix
- Open Steam → Downloads. Confirm Workshop downloads show 0 in queue.
- If anything is downloading, let it finish before clicking Connect.
- Restart Steam. Sometimes it leaves orphaned download tasks that block dependencies.
3. Wrong Password or Password-Field Bug
If the server has a password and the client's Steam-cached password is stale (you changed it serverside), the client may show "Initializing" while it silently retries auth.
Fix
- Click Forget Server in PZ's server browser, then re-add fresh.
- Confirm the password matches exactly (case-sensitive, leading/trailing whitespace counts).
4. Steam Authentication Outage
PZ uses Steam's auth ticket system. If Steam's auth servers are slow (occasional during peak hours), PZ stalls on Initializing while waiting for a ticket.
Fix
- Check steamstat.us — if Steam Auth is degraded, just wait 5-10 minutes.
- Restart Steam, then retry.
5. Server is Out of Memory
If the server's JVM heap is full, the server can accept the TCP handshake but fails to load player data. Players see "Initializing" forever; server logs show OutOfMemoryError.
Fix
- SSH/console into the server, tail
~/Zomboid/server-console.txt. - If you see OOM errors, see our Project Zomboid Server Memory Guide — bump
-Xmx. - Stop-gap: restart the server. RAM clears and the next batch of players gets through until it fills up again.
6. Port Blocked or CGNAT Issue
UDP 16261 (game) or 16262 (Steam) is blocked somewhere — your router, your ISP's CGNAT, or a corporate firewall.
Fix
- Test with another player on a different network. If only YOU stall, your network is the issue.
- Check your router's port-forwarding rules.
- If you're on a CGNAT ISP (most mobile/cellular gateways), ask the ISP for a public IP or move to managed hosting. See our PZ Server Ports & CGNAT Guide.
7. Build 41 vs Build 42 Mismatch
Client on Build 42 trying to join a Build 41 server (or vice versa) doesn't show a clear error — it just stalls.
Fix
- Confirm both client and server are on the same Build branch in Steam → PZ → Properties → Betas.
- If you're on managed hosting, switch the server's branch in the panel and have all players match.
8. Map Mods Need Pre-Generation
Custom map mods (Eerie Country, Bedford Falls, etc.) sometimes need the server to pre-generate the world before the first player can join. The server is technically running but generation is hogging the JVM.
Fix
- Check server logs for
generating cellmessages. If they're streaming, just wait — first-time generation can take 5-15 minutes for big map packs. - Pre-generate offline by running the server idle for 20 minutes before opening to players.
9. Player's PZ Save is Corrupt
The player's local copy of the server's save state (in ~/Zomboid/Saves/Multiplayer/) is corrupt. Server says hi, client tries to merge, fails silently.
Fix
- Have the affected player delete their
~/Zomboid/Saves/Multiplayer/<ServerName>_player/folder. This wipes their local cache only — server-side data (their actual character) is preserved. - Reconnect.
10. Server Whitelist or BattleMetrics Block
If your server has a whitelist enabled or uses BattleMetrics auto-ban for VAC-banned players, the rejection often shows as "Initializing" rather than a clean kick.
Fix
- Check
servertest.iniforOpen=false— that's whitelist mode. Add the player's Steam ID to the whitelist. - For BattleMetrics, log into BM and check the player's profile for any auto-action.
Diagnostic Order — What to Try First
- Have one player try; have a second player try. Narrows client-side vs server-side fast.
- Check server logs.
tail -100 ~/Zomboid/server-console.txttells you 80% of what's wrong. - Test connection without mods. Spin up a vanilla server temporarily, see if the player can join. If yes — it's mods. If no — it's network/auth.
- Restart server, then retry. Half of "Initializing" issues clear with a fresh JVM.
If You're on Managed Hosting
If you're hosted with us, mod-version pinning, JVM tuning, port config, and BattleMetrics integration are pre-baked. Most "Initializing" issues for our customers are mod-subscription mismatches on the client side, not server config — the server's already correct. Use the panel's "validate file integrity" action if you suspect server-side corruption.
Related Project Zomboid Guides
- Server Memory & RAM Guide
- Server Ports & Port Forwarding
- How to Add Mods to a PZ Server
- Getting Server Info Stuck
- Build 42 Stuck on Server Info
- PZ Dedicated Server Setup Guide
- Server Stopped During Launch
Tired of debugging? Supercraft PZ hosting from $5.99/mo — mod-version pinning, JVM-tuned -Xmx per plan tier, automatic snapshots before mod updates, 5 regions, 2-day refund. Most "Initializing" failures simply don't happen with a properly tuned server.