Project Zomboid Server Troubleshooting Guide

This page helps you troubleshoot the most common issues people run into when hosting a Project Zomboid Server on HypeServ.

Quick checklist (do this first)

Before digging into specific errors, please check these 4 things first:

1. Restart the server.
2. Check the server version vs client version (e.g., make sure both are on Build 41, or both are on Build 42).
3. If you just added a new map mod, confirm you added the map folder name to the Map= line in your .ini file.
4. If you installed mods recently: remove the newest mod and retry (mods are the #1 cause of startup crashes).

Connection and networking problems

“Connection Failed” / “Server Failed to Respond” / “Getting Server Info” loop

This usually looks like one of these patterns:

• You can play singleplayer, but joining your server fails or times out.
• The game sees the server in the browser but gets stuck indefinitely on "Getting server info".
• Joining works for some people but not others.

“Server has port 16262 closed. Performance may be severely limited.”

If players see this warning when joining:

This means the primary game connection worked, but the secondary direct-connect port failed to route. The game falls back to routing traffic through Steam's relay servers, which causes high ping and rubber-banding.

Fix: On HypeServ, your secondary ports and UDP routing are handled automatically. If you see this warning, simply Restart your server from the panel so the system can refresh your port bindings. If the issue persists after a restart, please open a support ticket.

Server won’t start or keeps crashing

“Server has stopped during launch” / “Normal Termination”

If the server immediately stops after you click Start, or shuts down while loading the map:

1. Open the Console tab and look for the word Exception or Error.
2. Look for java.lang.OutOfMemoryError. If you see this, your server ran out of RAM while trying to load the map or mods.
3. If you see Normal Termination with no obvious error above it, the server silently crashed due to a broken mod or a corrupted map chunk.

Endless “Initializing” cycle

If the server console shows it initializing, but it suddenly restarts and tries to initialize again in an endless loop:

This is almost always caused by a corrupted world save. If the server was forcefully stopped while it was saving map chunks (or crashed out of memory), the database can become corrupted, and the server will refuse to load it.

Fix:

1. Stop the server.
2. Go to the Backups tab in your HypeServ panel and restore your most recent working backup.
3. If you don't have a backup, you must go to /serverfiles/Saves/Multiplayer/ and delete your world save folder to force the server to generate a fresh map.

Performance and resource problems (lag, stutters, phantom bites)

Zombies teleporting / Players rubber-banding in cars

Project Zomboid requires intense, real-time simulation. If the server CPU falls behind, you will experience combat desync (phantom bites) and cars driving into "black walls" (unloaded chunks).

Fixes that usually work well:

• Lower the Zombie Population: Open your _SandboxVars.lua and reduce the Zombies multiplier. This is the #1 cause of server lag.
• Enable PauseEmpty: Ensure PauseEmpty=true in your .ini file so the server isn't simulating the world when no one is online.
• Upgrade your CPU Cores: Fast driving requires the server to generate and send hundreds of map chunks per second. Moving to a higher-tier HypeServ plan with more CPU cores will drastically improve chunk loading speeds.