Install a 7 Days To Die server

Step-by-step installation

1. 1

   Install SteamCMD (dedicated folder on Windows, non-root user on Linux).

2. 2

   Download the server: app_update 294420 validate (anonymous).

3. 3

   Copy serverconfig.xml under a unique name (e.g. myserver.xml); don't edit the original.

4. 4

   Edit it with the site's “serverconfig.xml” tool (name, password, slots, world, SandboxCode).

5. 5

   Start the server with -configfile=myserver.xml -dedicated (last option).

6. 6

   Test locally from the client (same version and branch) using 127.0.0.1:26900.

7. 7

   Open 26900 TCP/UDP and 26901-26903 UDP (firewall, provider, router).

8. 8

   Set up administrators (serveradmin.xml) and protect Telnet with a password.

9. 9

   Automate startup (systemd or scheduled task) and schedule backups and updates.

10. 10

    Add your server on game-rank.com/jeux/7-days-to-die.

1. Requirements

• OS: 64-bit Windows or Linux (Ubuntu/Debian). No license key: SteamCMD with anonymous login is enough.
• Hardware: not officially documented in our sources. As a rough, community-based guide (to validate): 4 recent cores and 8 GB RAM for a few players, more beyond that; SSD advised for RWG maps.
• Client and server must run exactly the same version and branch (stable or experimental).

2. Local install (Windows)

Install the server in C:\Servers\7dtd, then copy serverconfig.xml to myserver.xml and create start.bat with the launch command (the game's own startdedicated.bat does the same). For an experimental install, add -beta latest_experimental before validate, in a separate folder.

steamcmd +force_install_dir "C:\Servers\7dtd" +login anonymous +app_update 294420 validate +quit

rem start.bat
start 7DaysToDieServer -logfile "output_log.txt" -quit -batchmode -nographics -configfile=myserver.xml -dedicated

3. Linux VPS / dedicated server (Ubuntu/Debian)

Create a “sdtd” user without root rights, install SteamCMD, then the server. The 7d2dmodding wiki uses a path like /home/sdtd/server and the ./7DaysToDieServer.x86_64 binary with the same options as on Windows.

sudo adduser --disabled-password --gecos "" sdtd
sudo dpkg --add-architecture i386 && sudo apt update
sudo apt install -y steamcmd lib32gcc-s1 screen   # Ubuntu: enable 'multiverse' first
sudo -iu sdtd
/usr/games/steamcmd +force_install_dir /home/sdtd/server +login anonymous +app_update 294420 validate +quit
cd /home/sdtd/server && cp serverconfig.xml myserver.xml
./7DaysToDieServer.x86_64 -logfile output_log.txt -quit -batchmode -nographics -configfile=myserver.xml -dedicated

4. Ports to open

Change the game port with ServerPort in your config file (neighbouring ports follow). On the provider side (OVH, Hetzner, Scaleway… “security group”), allow the same ports. Home hosting: forward them (NAT) to the local IP. Test: connect from an outside network to IP:26900.

• 26900/TCP and UDP — game (ServerPort). The wiki advises staying within 26900-26905 or 27015-27020 for LAN discovery.
• 26901-26903/UDP — additional game traffic.
• 8080/TCP — web dashboard (WebDashboardPort), off by default; open only for administration and with passwords.
• 8081/TCP — Telnet (TelnetPort), on by default; with no password it listens on localhost only. Never expose it without a password.

5. Linux firewall (ufw)

Allow SSH before enabling ufw. Don't open 8080/8081 to the public.

sudo ufw allow OpenSSH
sudo ufw allow 26900/tcp
sudo ufw allow 26900:26903/udp
sudo ufw enable && sudo ufw status

6. Windows firewall

In an administrator command prompt:

netsh advfirewall firewall add rule name="7DTD TCP" dir=in action=allow protocol=TCP localport=26900
netsh advfirewall firewall add rule name="7DTD UDP" dir=in action=allow protocol=UDP localport=26900-26903

7. Automatic start (systemd)

Put this file at /etc/systemd/system/sdtd.service then: sudo systemctl enable --now sdtd. On Windows create a scheduled task “at startup” running start.bat; screen or tmux remain a simple alternative. The -quit launch option is the one the wiki recommends.

[Unit]
Description=7 Days to Die dedicated server
After=network-online.target
Wants=network-online.target

[Service]
Type=simple
User=sdtd
WorkingDirectory=/home/sdtd/server
ExecStart=/home/sdtd/server/7DaysToDieServer.x86_64 -logfile /home/sdtd/server/output_log.txt -quit -batchmode -nographics -configfile=myserver.xml -dedicated
Restart=on-failure
RestartSec=20

[Install]
WantedBy=multi-user.target

8. Updates, backups, restarts

Update: stop the server and re-run the same app_update command (same folder, same branch). Your myserver.xml is not overwritten. Backups: by default, saves and generated worlds live in the game's user data folder (typically ~/.local/share/7DaysToDie/ on Linux, %AppData%\7DaysToDie on Windows); check the real location on your install, then archive it with the server stopped. Cron example for a nightly backup and daily restart:

# crontab -e (user sdtd); stop/start via systemctl needs a sudoers rule
30 4 * * * sudo systemctl stop sdtd && tar -czf /home/sdtd/backups/7dtd-$(date +\%F).tar.gz -C /home/sdtd/.local/share 7DaysToDie
40 4 * * * /usr/games/steamcmd +force_install_dir /home/sdtd/server +login anonymous +app_update 294420 validate +quit && sudo systemctl start sdtd

9. Listing and finding your server

Set ServerVisibility to 2 (public) and fill in ServerName and Region to appear in the in-game list. For more visibility, add your server on game-rank.com/jeux/7-days-to-die (the owner's site for this tool).

10. Troubleshooting

• Incompatible version: client and server must have the same version and branch. Re-run app_update (with the same -beta if experimental).
• Server not in the list: check ServerVisibility=2, that 26900 TCP/UDP and 26901-26903 UDP are open, and connect directly via IP:26900 to isolate the issue.
• Settings ignored: the server didn't get -configfile, -dedicated isn't the last option, or you edited the shipped file that an update overwrote.
• Telnet or dashboard unreachable: without TelnetPassword, Telnet listens on localhost only; the dashboard (8080) is off until WebDashboardEnabled is true.
• No admin rights in game: check serveradmin.xml (exact platform and ID, level 0); reload after editing (admin add console command or restart).

Frequently asked questions

What is the 7 Days to Die server's Steam app ID?

294420 for the dedicated server (anonymous install with SteamCMD); the game client is app 251570.

Which ports does 7 Days to Die use?

26900 TCP/UDP and 26901-26903 UDP for the game; 8080 TCP (web dashboard, off by default) and 8081 TCP (Telnet) for administration only.

Is cross-play possible?

The ServerAllowCrossplay property exists (false by default). The exact prerequisites (EAC, network protocols) are not detailed in our sources: check the official documentation for your version.

How do I switch to the experimental branch?

Add -beta latest_experimental to the app_update command (preferably in a separate install folder); clients must use the same branch.