Troubleshooting

The most common problems on a 7 Days to Die server, and how to fix them. In every case, the panel Console is your first tool: read the last lines shown before the stop or the error.

The server does not start

It stops during world generation

With GameWorld set to RWG, world generation uses a lot of RAM. If the server stops during this phase with no other obvious error, memory is most likely insufficient for the requested size.

• Reduce WorldGenSize (for example from 10240 to 8192 or 6144)
• Or generate the world on your PC and upload it as a pregenerated map: see Maps and worlds
• Or upgrade to a plan with more RAM

Be patient

RWG generation can take a long time. As long as the console keeps progressing, do not restart: each restart starts generation over from the beginning.

XML error after adding a mod

An incompatible or misplaced mod often blocks loading. The console usually shows the file and line involved.

1. Stop the server
2. Remove the last mod added from the Mods/ folder
3. Restart
4. If the server starts again, that mod is the culprit: check its version and compatibility with your other mods

See Install mods.

Error in serverconfig.xml

An unclosed tag, a missing quote or an invalid value prevents the server from reading its configuration. Compare your file with your last working copy, or check it with an XML validator. See Configure serverconfig.xml.

The map cannot be found

If GameWorld points to a pregenerated map, the value must match exactly the folder name (case and spaces included) in Data/Worlds/ or GeneratedWorlds/. Also check that all the map files were transferred.

The save no longer loads

After a major game update or adding/removing an overhaul, an old save may become incompatible. Restore a backup from the Backups tab, or start a new game by changing GameName: see Backups and world reset.

Players who cannot connect

Symptom	Likely cause	Solution
The server does not appear in the list	Server not public, or still loading	Connect by IP; check ServerVisibility and that the console has finished loading
Connection failed / timed out	Wrong IP or port, server not ready yet	Use the IP and port shown in the panel, wait for loading to finish
Refused because of a different version	Client and server not on the same version	Same Steam branch and same version for everyone (see Changing version)
EAC or authentication error	Modded server with EAC enabled, or player launched without EAC on a server that requires it	Align EACEnabled with the way players launch the game
Wrong password	ServerPassword changed without a restart	Restart the server after changing it
Disconnected right after loading	Client mod or overhaul missing or a different version	Same mods, same version for everyone (see Install mods)
Server full	ServerMaxPlayerCount reached	Raise the value (keeping RAM in mind)
Player refused although everything is correct	Player banned, or whitelist active	Check ban list and the <whitelist> section of serveradmin.xml

Ports

Opening the required ports is handled by YorkHost. Do not change ServerPort in serverconfig.xml: the server must listen on the port assigned by the panel. See Are all ports open? and Unable to connect to the server.

Lag during the Blood Moon

The Blood Moon is the most demanding moment for the server: dozens of zombies pathfind towards players at the same time and destroy blocks. A bit of lag that night is normal; if it becomes unplayable:

1. Lower BloodMoonEnemyCount: this value is multiplied by the number of connected players. Going from 8 to 6 or 4 relieves the server a lot.
2. Limit MaxSpawnedZombies: the total number of zombies on the map.
3. Reduce ServerMaxAllowedViewDistance: a shorter view distance limits the number of loaded chunks.
4. Group players together: players spread across the map multiply the active areas, each with its own hordes.
5. Restart the server regularly, for example before the Blood Moon or every night, with an automatic restart.

If the server stays maxed out on RAM or CPU despite these settings (especially with an overhaul or a large map), a higher plan is justified. To analyse resource usage, see also Server performance debugging.

The server degrades over time

Like many game servers, 7 Days to Die runs better after a restart. Schedule a daily restart at an off-peak time from the Schedules tab: see Configure automatic restart. Type saveworld before a manual stop if you are not using the panel's stop button.

Still stuck?

Contact support 7 days a week on Discord or through your client area, including:

• your server's name
• what you changed just before the problem
• the last lines of the console at the time of the error