Enshrouded Server Troubleshooting: Common Issues

Start with the Console

The Console page shows your server's own log file (logs/enshrouded_server.log) from the start of each boot, with the game's warnings and errors marked, plus short [GameGrid] lines saying what the platform did: a start or stop, a crash and each automatic restart attempt, a backup, a settings event, mods applied or not, and players joining and leaving. Enshrouded has no admin console, so there is no command box there.

The Errors chip (with Prev error and Next error) jumps between the game's errors, and Server shows only GameGrid's lines. See The Enshrouded Console and Server Log.

The server will not start

When Enshrouded refuses its settings file it writes no log at all; the reason is in `logs/stdout.log`, which you can open in Files. The common reasons:

• Two user groups have the same password. Enshrouded stops at once with "user groups passwords must be unique". GameGrid will not save two the same, so this comes from a settings file edited by hand or uploaded: give each group its own password in Settings → User Groups and save.
• A value in the settings file is not one the game knows. A tag, a tombstone mode or another choice it does not recognise ("Failed to parse enum ..."). The Settings page never writes such a value, so this follows a hand edit or an uploaded file. Fix the value in Settings, or correct the file in Files with the server stopped.
• The file was saved with a byte-order mark ("Failed to parse Config"). GameGrid removes it before every start, so a restart fixes it.

Step by step, and the fix that always works: Your Enshrouded Server Won't Start.

A setting seems to do nothing

• Did the server restart? Enshrouded reads its settings only when it starts. Saving restarts a running server for you; a stopped one applies them at its next start.
• Is it outside the game's range? The Settings page refuses values Enshrouded does not accept, but if a value was put in the file by hand, Enshrouded quietly uses its nearest limit instead. XP, for example, stops at x2.
• Is an Event Manager window running? During a window, the preset's settings are in force; yours come back when it ends. The Active tab of Events shows it.
• Is it an Inventory & Storage setting? Existing stacks, backpacks and chests keep their size: only new ones get the change. See Bigger Stacks, Backpacks and Chests.

GameGrid runs every Enshrouded server on the Custom preset, so the gameplay values on the Settings page are always the ones in use. You do not need to switch the preset yourself. At every start the server prints the values it actually applied, in the Console.

Players cannot find the server

• The dedicated-server filter. Enshrouded's server list hides dedicated servers unless the player turns on that option in the list's filter. Check it first, every time.
• Search for your server's exact name, as set in Settings. A new name, new tags and new player slots show after the next start.
• Give the list a few minutes: it is slow to fill, and a server that has just started can take several minutes to appear. Steam's own server list (in the Steam client: View → Game Servers) usually shows it sooner.
• To join straight away, search by address instead, using Server Address from the Connect card on your server's Overview.
• Check that the server is running and has finished starting: the Console shows [GameGrid] Server is ready: players can join.

See Enshrouded Connection Problems.

A player has the wrong permissions

A player's permissions come from the password they typed when they joined, and they keep that group until they leave. If you changed groups or passwords, save (a running server restarts), then have the player leave and rejoin with the right group's password.

If they still have the wrong rights, check which password they are using: Show beside each group's password in Settings → User Groups, and the permissions their join lists in the Console. See User Groups, Passwords and Permissions.

A purchase or kit has not arrived

• Are they linked? Economy → Links should show them as Verified. See Linking Discord Accounts to Enshrouded Players.
• Are they on the server? Items go into a character the server is running. Orders wait for them, for up to 7 days.
• Is it still in the queue? Economy → Transactions shows its place and an estimate, or why it is waiting.
• Did it stop part way? A ✗ with "N of M delivered" means you decide whether to retry or refund. Look in game first.

See How Items Are Delivered on Enshrouded.

Give or Teleport is greyed out on the map

The reason is shown under the menu entry. The usual ones:

• The map says Teleport and Give work only while exactly one player is online: your server is still on an older module build. Restart it at a quiet moment to pick up the current one.
• The player has only just joined and is not identified yet: try again in a moment.
• The note under the map says they are paused after a game update: the server module failed repeatedly on your server's new game build, so Give and Teleport are paused on that build until it is working again. Our team has been alerted, and purchases wait in the delivery queue meanwhile.

See The Enshrouded World Map.

Mods are not loading

• Is EML installed on the Mods page? Without it, no mod of yours is applied.
• Did you restart after installing or enabling the mod?
• If a mod is broken or made for another game version, the server still starts. With several mods, only the mod that failed is left out and the rest apply (the Console says which); with one mod, or none named, the server starts without your mods. The reason is written to logs/mod-framework.log. Open it in Files; EML names the mod that failed. Disable that mod and restart.
• Does the mod need code to run? EML only patches the game's data, so a mod that needs scripts or a DLL does nothing on a server.

See Mods on Your Enshrouded Server.

Lost progress after a crash

Enshrouded saves about every 30 seconds and when it is stopped cleanly. If the server was killed rather than stopped, progress since the last save is lost. To go back further, restore a backup: see Enshrouded Saves, Backups and Restore.

Still stuck

See Server Will Not Start, the Enshrouded Server FAQ, or contact support with the last lines of the Console and of logs/stdout.log.