EN

Game servers

How to Create an Enshrouded Server

Complete guide to hosting a dedicated Enshrouded server on a VPS or dedicated Linux server with Wine: SteamCMD, passwords, roles, systemd service and backups.

9 min read, updated on 18 November 2026

On this page

Your values

Enter them once and the commands in this guide update.

This guide explains how to host a dedicated Enshrouded server on your VPS or dedicated Linux server, configure its passwords and roles, run it as a systemd service under a dedicated user, then back it up.

Order a Server

Enshrouded requires a powerful processor and a good amount of memory. HostMyServers offers several suitable options:

Prerequisites

  • SSH access as root or user with sudo privileges
  • 64-bit Linux system: Debian 12/13 or Ubuntu 22.04/24.04
  • Active firewall: nftables, iptables or ufw (use only one tool at a time)
  • A public IPv4 address: Enshrouded multiplayer only uses IPv4

Required Configuration

Keen Games provides these guidelines for its Windows server. Wine adds a slight overhead, so allow some headroom.

Component 4 to 6 players Up to 16 players
CPU 6 cores / 12 threads at 3.2 GHz or more More powerful processor, high frequency
RAM 16 GB 16 GB or more
Storage 30 GB of free SSD space 30 GB of free SSD space or more
Upload bandwidth 2 Mbps per player 2 Mbps per player

According to the publisher, the process uses about 4.4 GB of RAM at idle, plus up to 100 MB more per player.

Ports Used

Port Protocol Usage
15637 UDP Query and connection port (queryPort)

Enshrouded's documentation does not describe any RCON-style remote administration interface, so there is no administration port to open. Permissions are managed in-game, through roles.

System Update

Terminal
sudo apt update && sudo apt upgrade -y

Installing Dependencies

Terminal
sudo dpkg --add-architecture i386
sudo apt update
sudo apt install -y lib32gcc-s1 curl tar ca-certificates gnupg nano cron jq

Installing Wine

The Wine versions shipped by distributions differ widely from one another. The official WineHQ repository provides the same stable branch on Debian 12/13 and Ubuntu 22.04/24.04:

Terminal
sudo mkdir -pm755 /etc/apt/keyrings
curl -fsSL https://dl.winehq.org/wine-builds/winehq.key | sudo gpg --dearmor --yes -o /etc/apt/keyrings/winehq-archive.key
. /etc/os-release
sudo curl -fsSL -o "/etc/apt/sources.list.d/winehq-${VERSION_CODENAME}.sources" "https://dl.winehq.org/wine-builds/${ID}/dists/${VERSION_CODENAME}/winehq-${VERSION_CODENAME}.sources"
sudo apt update
sudo apt install -y --install-recommends winehq-stable
wine --version

Creating a Dedicated User

The server must never run as root. Create a user reserved for it:

Terminal
sudo useradd --create-home --shell /bin/bash enshrouded

Firewall Configuration

With UFW

Terminal
sudo ufw allow 15637/udp
sudo ufw reload

With iptables

Terminal
sudo apt install -y iptables-persistent
sudo iptables -A INPUT -p udp --dport 15637 -j ACCEPT
sudo iptables-save | sudo tee /etc/iptables/rules.v4

Saving the rules across reboots requires the iptables-persistent package.

With nftables

These commands enable nftables, then use the inet filter table and the input chain from the /etc/nftables.conf file shipped with the package, on both Debian and Ubuntu.

Terminal
sudo apt install -y nftables
sudo systemctl enable --now nftables
sudo nft add rule inet filter input udp dport 15637 accept
(echo "flush ruleset"; sudo nft list ruleset) | sudo tee /etc/nftables.conf

Installing SteamCMD

Open a session as the dedicated user, then download SteamCMD:

Terminal
sudo -iu enshrouded
mkdir -p ~/steamcmd ~/enshrouded-server
cd ~/steamcmd
curl -fsSL https://steamcdn-a.akamaihd.net/client/installer/steamcmd_linux.tar.gz | tar -xzf -

Downloading the Server

Since the server only exists for Windows, you must explicitly request that platform from SteamCMD. Still as the enshrouded user:

Terminal
~/steamcmd/steamcmd.sh +@sSteamCmdForcePlatformType windows +force_install_dir /home/enshrouded/enshrouded-server +login anonymous +app_update 2278520 validate +quit

When it finishes, the message Success! App '2278520' fully installed. is displayed. If the download is interrupted, run the same command again.

Preparing Wine

Create a Wine environment reserved for the server:

Terminal
export WINEPREFIX=/home/enshrouded/.wine-enshrouded
export WINEARCH=win64
export WINEDEBUG=-all
wine wineboot --init
wine winecfg -v win10
wineserver -w

First Launch

The first launch creates the enshrouded_server.json file. Still in the same session, start the server for three minutes:

Terminal
cd ~/enshrouded-server
timeout --signal=INT --kill-after=60 180 wine /home/enshrouded/enshrouded-server/enshrouded_server.exe
wineserver -k
ls -l enshrouded_server.json

If the file does not appear, see the "Troubleshooting" section at the end of this guide.

Server Configuration

Edit the File

The server must be stopped while you edit the file. The file contains passwords, so restrict read access to the dedicated user.

Terminal
chmod 600 ~/enshrouded-server/enshrouded_server.json
nano ~/enshrouded-server/enshrouded_server.json

Edit the values in the generated file without replacing it entirely, so that you keep the settings added by your server version:

JSON
{
  "name": "My Enshrouded Server",
  "saveDirectory": "./savegame",
  "logDirectory": "./logs",
  "ip": "0.0.0.0",
  "queryPort": 15637,
  "slotCount": 16,
  "voiceChatMode": "Proximity",
  "enableVoiceChat": false,
  "enableTextChat": false,
  "gameSettingsPreset": "Default"
}
Parameter Description
name Name displayed in the server list
saveDirectory World save folder
logDirectory Log folder
ip Listening address (0.0.0.0 = all IPv4 addresses)
queryPort Server UDP port; update the firewall if you change it
slotCount Number of players, 16 maximum
voiceChatMode Voice chat mode, for example Proximity
enableVoiceChat Enables voice chat
enableTextChat Enables text chat
gameSettingsPreset Difficulty: Default, Relaxed, Hard, Survival or Custom

The detailed settings in the gameSettings block only apply with the Custom preset. The enshrouded_server_readme.txt file, supplied with the server, describes the accepted values for your version.

Passwords and Roles

The password field at the root of the file is no longer used: leave it empty or omit it, because if it is filled in, the server creates a default group with that password. Access is managed with the groups in userGroups: the password a player enters determines their role.

A new file usually contains the following groups, with randomly generated passwords:

Group Kick / ban Inventories Edit world Edit bases Extend bases
Admin Yes Yes Yes Yes Yes
Friend No Yes Yes Yes No
Guest No No Yes No No
Visitor No No No No No

Replace the passwords with long, distinct values, and remove any groups you don't need:

JSON
"userGroups": [
  {
    "name": "Admin",
    "password": "VeryLongAdminPassword",
    "canKickBan": true,
    "canAccessInventories": true,
    "canEditWorld": true,
    "canEditBase": true,
    "canExtendBase": true,
    "reservedSlots": 1
  },
  {
    "name": "Friend",
    "password": "VeryLongFriendsPassword",
    "canKickBan": false,
    "canAccessInventories": true,
    "canEditWorld": true,
    "canEditBase": true,
    "canExtendBase": false,
    "reservedSlots": 0
  }
]
Field Description
name Group name
password Password that grants access to this role
canKickBan Kick and ban players
canAccessInventories Access inventories
canEditWorld Edit the world outside bases
canEditBase Edit bases
canExtendBase Extend bases
reservedSlots Slots reserved for this group when the server fills up

Check the File

A single missing comma is enough to make the file unreadable. Check it, then exit the session:

Terminal
jq empty ~/enshrouded-server/enshrouded_server.json && echo "Configuration is valid"
exit

Configuration as a systemd Service

Create the Service File

Terminal
sudo nano /etc/systemd/system/enshrouded.service
Configuration
[Unit]
Description=Enshrouded Dedicated Server (Wine)
Wants=network-online.target
After=network-online.target

[Service]
Type=simple
User=enshrouded
Group=enshrouded
WorkingDirectory=/home/enshrouded/enshrouded-server
Environment=WINEPREFIX=/home/enshrouded/.wine-enshrouded
Environment=WINEARCH=win64
Environment=WINEDEBUG=-all
ExecStart=/usr/bin/wine /home/enshrouded/enshrouded-server/enshrouded_server.exe
KillSignal=SIGINT
KillMode=mixed
TimeoutStopSec=90
Restart=on-failure
RestartSec=30
LimitNOFILE=100000

[Install]
WantedBy=multi-user.target

KillSignal=SIGINT asks the server to stop cleanly. KillMode=mixed sends this signal only to the main process, so that Wine stays active during shutdown.

Enable and Start the Service

Terminal
sudo systemctl daemon-reload
sudo systemctl enable --now enshrouded.service

Management Commands

Terminal
# Check status
sudo systemctl status enshrouded.service

# Stop the server
sudo systemctl stop enshrouded.service

# Restart the server
sudo systemctl restart enshrouded.service

# View service logs
sudo journalctl -u enshrouded.service -f

Check That the Server Is Listening

Terminal
sudo ss -ulnp | grep 15637

The detailed game logs are in /home/enshrouded/enshrouded-server/logs/.

Connecting to the Server

From the In-Game List

  1. Launch Enshrouded and open the server list.
  2. Enable the Show dedicated server filter.
  3. Search for your server's name and join it.
  4. Enter the password for the role you want.

By IP Address

If the server does not appear, add it to your Steam favorites:

  1. In Steam, open the View menu, then Game Servers.
  2. In the Favorites tab, click +.
  3. Enter SERVER_IP:15637.

The server then appears at the top of the list in the game.

Server Update

The server and the players must use compatible versions. Back up before every update, using the backup.sh script described in the next section:

Terminal
sudo systemctl stop enshrouded.service
sudo -u enshrouded /home/enshrouded/backup.sh
sudo -iu enshrouded
~/steamcmd/steamcmd.sh +@sSteamCmdForcePlatformType windows +force_install_dir /home/enshrouded/enshrouded-server +login anonymous +app_update 2278520 validate +quit
exit
sudo systemctl start enshrouded.service

Automatic Backup

The savegame folder contains the world, and enshrouded_server.json contains the configuration and passwords.

Backup Script

Terminal
sudo -u enshrouded nano /home/enshrouded/backup.sh
Terminal
#!/bin/bash
BACKUP_DIR="/home/enshrouded/backups"
SERVER_DIR="/home/enshrouded/enshrouded-server"
DATE=$(date +%Y-%m-%d_%H-%M-%S)
ARCHIVE="$BACKUP_DIR/enshrouded_$DATE.tar.gz"

umask 077
mkdir -p "$BACKUP_DIR"

tar -czf "$ARCHIVE" -C "$SERVER_DIR" savegame enshrouded_server.json
STATUS=$?

# Exit code 1 only means a file changed while it was being read
if [ "$STATUS" -gt 1 ]; then
  rm -f "$ARCHIVE"
  echo "Backup failed" >&2
  exit "$STATUS"
fi

# Delete backups older than 7 days
find "$BACKUP_DIR" -name "enshrouded_*.tar.gz" -mtime +7 -delete

echo "Backup completed: $ARCHIVE"
Terminal
sudo chmod +x /home/enshrouded/backup.sh

Schedule the Backup

Terminal
sudo crontab -u enshrouded -e

Add:

Text
# Backup every 6 hours
0 */6 * * * /home/enshrouded/backup.sh

Also keep a copy on another machine: a backup stored on the same disk does not protect you if that disk fails.

Restore a Backup

Replace the archive name with the name of the backup you want to restore:

Terminal
sudo systemctl stop enshrouded.service
sudo -iu enshrouded
cd ~/enshrouded-server
mv savegame savegame.old
tar -xzf ~/backups/enshrouded_2026-01-01_12-00-00.tar.gz savegame
exit
sudo systemctl start enshrouded.service

To restore the configuration as well, add enshrouded_server.json to the end of the tar command. Once you have checked the world in-game, you can delete savegame.old.

Troubleshooting

Service won't start

  • Check the logs: sudo journalctl -u enshrouded.service -n 100
  • Check the most recent file in /home/enshrouded/enshrouded-server/logs/
  • Validate the configuration: sudo -u enshrouded jq empty /home/enshrouded/enshrouded-server/enshrouded_server.json
  • Check Wine: wine --version
  • Check disk space and memory: df -h and free -h

Wine says the folder doesn't belong to you

The message is not owned by you appears when a command was run as the wrong user, for example root. Give the files back to the dedicated user:

Terminal
sudo systemctl stop enshrouded.service
sudo chown -R enshrouded:enshrouded /home/enshrouded
sudo systemctl start enshrouded.service

enshrouded_server.json file doesn't appear

  • Check that enshrouded_server.exe is present in ~/enshrouded-server
  • Open a new session with sudo -iu enshrouded, then repeat the Wine preparation and the first launch without setting WINEDEBUG, so you can read the errors
  • Run SteamCMD again with validate to repair the files

Server doesn't appear in the list

  • Enable the Show dedicated server filter
  • Add the server to your Steam favorites with SERVER_IP:15637
  • Check that port 15637 is open on UDP and that the server is listening

Players can't connect

  • Check that the server and the game are up to date
  • Check that queryPort matches the firewall rule
  • Use the server's IPv4 address
  • Check that the password matches a group in userGroups

SteamCMD Errors

  • state is 0x202: check disk space with df -h and file ownership.
  • state is 0x6: check the server's connection to Steam, then run the command again.
  • Unable to determine CPU Frequency. Try defining CPU_MHZ.: run export CPU_MHZ=2000, then run SteamCMD again.

Server stops working after an update

A game or Wine update can break compatibility. Check the logs, check the version with wine --version, then run SteamCMD again with validate. Your data remains available in your backups. If the problem comes from Wine compatibility, watch for announcements from Keen Games and WineHQ, because the publisher does not provide support for this method.

Performance Issues

  • Reduce slotCount
  • Check that the machine is not running other heavy services
  • Monitor the processor and memory with top
  • Upgrade to a plan with a faster processor