Troubleshooting

The most common issues on an Enshrouded server, and how to fix them. In every case, the panel Console is your first tool: read the last lines shown before the shutdown or error.

The server does not start

Error in enshrouded_server.json

This is the most common cause after a change. One comma too many (especially after the last item of a block), a missing quote or a true / false value wrapped in quotes is enough to make the file invalid.

1. Stop the server
2. Compare enshrouded_server.json with your last working copy, or check it with a JSON validator
3. Fix the error, save, then restart

See Configure enshrouded_server.json.

The first start seems stuck

On first launch or after an update, the server downloads and prepares its files, then creates or loads the world. This can take several minutes. As long as the console is progressing, don't restart.

Server files modified

The Enshrouded dedicated server is built for Windows: YorkHost runs it in a managed Windows environment (compatibility layer). Don't replace the server's executables or libraries with files downloaded elsewhere, and don't delete files outside savegame and enshrouded_server.json: the environment might no longer start. If you already have, contact support.

The world no longer loads

After a world import, a manual reset or a major update, the world may no longer load (or an empty world is created instead). Restore a backup from the Backups tab: see Backups and world import.

Players who cannot connect

Symptom	Likely cause	Fix
The server doesn't appear in the list	Server still starting, or search too broad	Wait for loading to finish, search for the server's exact name, or add the panel's IP:PORT to your Steam favorites (View → Game Servers → Favorites)
Connection failed / timed out	Server not ready yet, or port changed	Wait for loading to finish; check that the ports in enshrouded_server.json haven't been changed
Password refused	Password changed without a restart, or a typo	Restart the server after any change; watch out for capitals and spaces
Connected but with the wrong permissions	Another group's password was entered	Reconnect with the right group's password; make sure each group has a different password
Refused because of a version mismatch	Client and server not on the same version	See Client version mismatch
Server full	slotCount reached (16 at most)	Wait for a slot to free up, or adjust slotCount and reservedSlots
Player on console	Compatibility not confirmed	Our servers host players on the PC version; compatibility with any console versions hasn't been confirmed yet

Ports

Opening the required ports is handled by YorkHost. Don't change queryPort (or gamePort if present) or ip in enshrouded_server.json: the server must listen on the port assigned by the panel. See Are all ports open? and Unable to connect to the server.

Client version different from the server

A client and a server on different versions cannot connect. This mostly happens on update day, when Steam has already updated the game but not the server yet (or the other way around).

1. Make sure every player has installed the latest update in Steam
2. Restart the server from the Console and check in the logs that it starts without errors
3. If the mismatch persists, contact support and mention the version shown in the game

Version 1.0

Version 1.0 is announced for October 15, 2026. On release day, the dedicated server may ship a little after the game: be patient, and make a backup before updating. See Preparing for the 1.0 update.

Lag and slowdowns

Enshrouded is mostly CPU-bound: the voxel world, enemies and building physics are computed continuously. If the server lags:

1. Check CPU usage in the panel while it lags. A processor constantly maxed out is the most common sign.
2. Keep players together: players scattered across the map multiply the active areas to simulate.
3. Tone down the difficulty if you're in Custom mode: very high values for enemy counts (for example randomSpawnerAmount or aggroPoolAmount, depending on the version) increase the load.
4. Restart the server regularly, for example every night, with an automatic restart from the Schedules tab.
5. Check the player's connection: if only one player lags, the issue is often their connection or PC, not the server.

If the processor stays saturated despite these settings, especially with 9 or more players or large bases, a tier with more vCores is justified. To analyze resource usage, see also Debugging performance.

Not enough memory

Enshrouded uses little memory compared to other survival games, but RAM can still fill up with a full server, very large bases or after many hours without a restart. Typical signs: the server stops abruptly with no clear error in the console, or RAM usage is constantly maxed out in the panel.

1. Restart the server and schedule a daily restart
2. Check whether the shutdown coincides with a peak in players or building
3. If RAM stays saturated under normal use, move up a tier from your client area

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