How to Read the Server Log of Your Enshrouded Server

The server log records what your Enshrouded server does: the startup, the loading of the save and every player connection. When something goes wrong it is the first place to look – and exactly what our support team needs from you.

There are two ways to access the log: live in the console of the dashboard, or as a file via SFTP.

Follow the log live in the console

1. Open dashboard
   Open the dashboard of your server and switch to the console.

2. Start the server
   Start your server. From now on the console prints every line of the log directly.

3. Follow the output
   Read the messages from top to bottom. Pay close attention to the lines shortly before a crash or a failed join – that is usually where the cause shows up.

Download the log file

1. Connect via SFTP
   Connect to your server via SFTP.

2. Open the logs folder
   Navigate to the logs folder in the main directory.

3. Download the file
   Download the file enshrouded_server.log to your PC. It contains the same output you also see in the console.

Understanding common messages

Server started successfully

Your server has fully started and is ready for players as soon as these messages appear:

[Session] 'HostOnline' (up)!
[Session] finished transition from 'Lobby' to 'Host_Online' (current='Host_Online')!
[server] Load deserialization took <time> s

If these messages are missing, your server did not finish starting. In that case the lines above them are the ones that matter for finding the cause.

A player connects

When a player connects, these lines show up among others:

[online] Session accepted with peer ( id 76561198000000000 ).
[online] Added Peer #0.

The number after id is the player's SteamID64. It tells you who connected and when.

Connection closed or failed

A failed join looks like this, for example:

[online] Session failed for peer #0 with error 4.
[online] Removed Peer #0.

A Removed Peer line on its own only means that a player's connection has ended. Only a Session failed line right before it shows that the join failed.

If you are stuck

If the log does not tell you enough, simply attach the file enshrouded_server.log to a support ticket and briefly describe when the problem occurred. That way we can look into it specifically.