EN

Game servers

How to Create a Satisfactory Server

Complete guide to installing a dedicated Satisfactory server on a VPS or dedicated Linux server: SteamCMD, systemd service, claiming the server, administration 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 install a dedicated Satisfactory server on your VPS or dedicated Linux server, run it as a systemd service under a dedicated user, claim it from the game, then protect your save games with regular backups.

The server has a native Linux version, distributed free of charge through Steam under application ID 1690800.

Order a Server

Satisfactory mainly relies on memory and single-core processor power, and its needs grow with the size of your factory. 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, on an x86-64 processor
  • Active firewall: nftables, iptables or ufw (use only one tool at a time)
  • The game Satisfactory on your computer, to claim the server

Required Configuration

Component Minimum Recommended
RAM 8 GB 16 GB, beyond 4 players or for a large factory
CPU x86-64, such as Intel Core i5-3570 or AMD Ryzen 5 3600 High frequency, good single-core performance
Storage 20 GB SSD 40 GB NVMe SSD

The server files take up about 8 GB on Linux. The rest of the space is used for backups.

Ports Used

Port Protocol Usage
7777 UDP Game traffic
7777 TCP Server traffic and HTTPS API
8888 TCP Reliable Messaging

The old ports 15000 and 15777 have not been used since version 1.0. The external port number must stay identical to the internal port: forwarding to a different number is not supported for port 7777.

System Update

Terminal
sudo apt update && sudo apt upgrade -y

Installing Dependencies

SteamCMD and the server use 32-bit libraries:

Terminal
sudo dpkg --add-architecture i386
sudo apt update
sudo apt install -y lib32gcc-s1 libsdl2-2.0-0:i386 curl tar ca-certificates nano cron

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 satisfactory

Firewall Configuration

The game needs the following three rules.

With UFW

Terminal
sudo ufw allow 7777/udp
sudo ufw allow 7777/tcp
sudo ufw allow 8888/tcp
sudo ufw reload

With iptables

Terminal
sudo apt install -y iptables-persistent
sudo iptables -A INPUT -p udp --dport 7777 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 7777 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 8888 -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 7777 accept
sudo nft add rule inet filter input tcp dport 7777 accept
sudo nft add rule inet filter input tcp dport 8888 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 satisfactory
mkdir -p ~/steamcmd ~/satisfactory-server
cd ~/steamcmd
curl -fsSL https://steamcdn-a.akamaihd.net/client/installer/steamcmd_linux.tar.gz | tar -xzf -

Downloading the Server

Still as the satisfactory user:

Terminal
~/steamcmd/steamcmd.sh +force_install_dir /home/satisfactory/satisfactory-server +login anonymous +app_update 1690800 validate +quit

When it finishes, the message Success! App '1690800' fully installed. is displayed. If the download is interrupted, run the same command again. Then exit the session:

Terminal
exit

Configuration as a systemd Service

Create the Service File

Terminal
sudo nano /etc/systemd/system/satisfactory.service
Configuration
[Unit]
Description=Satisfactory Dedicated Server
Wants=network-online.target
After=network-online.target

[Service]
Type=simple
User=satisfactory
Group=satisfactory
WorkingDirectory=/home/satisfactory/satisfactory-server
ExecStart=/home/satisfactory/satisfactory-server/FactoryServer.sh
KillSignal=SIGINT
TimeoutStopSec=120
Restart=on-failure
RestartSec=60
LimitNOFILE=100000

[Install]
WantedBy=multi-user.target

KillSignal=SIGINT is important: with systemd's default signal, the server would stop without cleanly finishing its work.

Enable and Start the Service

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

Management Commands

Terminal
# Check status
sudo systemctl status satisfactory.service

# Stop the server
sudo systemctl stop satisfactory.service

# Restart the server
sudo systemctl restart satisfactory.service

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

Check That the Server Responds

Terminal
sudo ss -plnut | grep -E ':(7777|8888)\b'
curl -k https://127.0.0.1:7777

The server uses a self-signed certificate, hence the -k option. A response containing errors.com.epicgames.httpserver.route_handler_not_found is normal: it confirms that the server is listening.

Claiming the Server

A new server has neither an owner nor an administrator password. Claim it as soon as it first starts, before sharing its address.

  1. Launch Satisfactory and open the Server Manager from the main menu.
  2. Add a server with the address SERVER_IP and port 7777.
  3. Accept the server's certificate: it is self-signed, so this warning is expected.
  4. Give the server a name.
  5. Set the administrator password.
  6. Create a new game, or import an existing save.

Protect Player Access

By default, players are not asked for a password. To add one, open the server settings in the Server Manager, then use Change Password next to the player password protection.

Connecting to the Server

Each player adds the server in the Server Manager with SERVER_IP and port 7777, then joins it from that screen. Port 8888 is handled automatically by the game.

The game version must be the same on the server and on the players' computers.

Administration

Server Settings

Common settings are found in the server settings tab of the Server Manager:

Setting Effect
Auto Pause Pauses the game when no player is connected
Auto-Save on Player Disconnect Saves when a player disconnects
Autosave Interval Interval between automatic saves, in minutes
Server Restart Interval Time of the daily restart, despite its name
Network Quality Balance between server smoothness and network quality

Server Console

The Console tab of the Server Manager lets you send commands:

Command Description
server.SaveGame SaveName Saves the game under this name
server.GenerateAPIToken Creates a token for the HTTPS API
server.InvalidateAPITokens Revokes all API tokens
quit Stops the server

To keep the server stopped, it is better to use sudo systemctl stop satisfactory.service. Treat every API token like a password.

Increase the Player Limit

The default limit is 4 players. To change it without relying on the .ini files, which an update can replace, add a launch option. Open the service and replace the ExecStart line:

Terminal
sudo nano /etc/systemd/system/satisfactory.service
Configuration
ExecStart=/home/satisfactory/satisfactory-server/FactoryServer.sh -ini:Game:[/Script/Engine.GameSession]:MaxPlayers=8
Terminal
sudo systemctl daemon-reload
sudo systemctl restart satisfactory.service

Raising this limit can reduce stability and performance.

Configuration Files

Path Content
~/.config/Epic/FactoryGame/Saved/SaveGames/server/ Game saves
~/.config/Epic/FactoryGame/Saved/SaveGames/blueprints/ Blueprints
~/.config/Epic/FactoryGame/Saved/SaveGames/ServerSettings.7777.sav Server settings
~/satisfactory-server/FactoryGame/Saved/Config/LinuxServer/ Engine.ini, Game.ini, GameUserSettings.ini
~/satisfactory-server/FactoryGame/Saved/Logs/ Logs, including FactoryGame.log

Here, ~ refers to /home/satisfactory. Only edit the .ini files while the server is stopped: they are rewritten on shutdown.

Backups

Import an Existing Game

In the Server Manager, open the server's Manage Saves tab to upload a save from your computer, then load it.

Backup Script

The server does not save the game during a normal shutdown. The script below therefore archives the most recently written saves, so enable automatic saves in the server settings.

Terminal
sudo -u satisfactory nano /home/satisfactory/backup.sh
Terminal
#!/bin/bash
BACKUP_DIR="/home/satisfactory/backups"
SOURCE_DIR="/home/satisfactory/.config/Epic/FactoryGame/Saved"
DATE=$(date +%Y-%m-%d_%H-%M-%S)
ARCHIVE="$BACKUP_DIR/satisfactory_$DATE.tar.gz"

umask 077
mkdir -p "$BACKUP_DIR"

tar -czf "$ARCHIVE" -C "$SOURCE_DIR" SaveGames
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 "satisfactory_*.tar.gz" -mtime +7 -delete

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

Schedule the Backup

Terminal
sudo crontab -u satisfactory -e

Add:

Text
# Backup every 6 hours
0 */6 * * * /home/satisfactory/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 satisfactory.service
sudo -iu satisfactory
mv ~/.config/Epic/FactoryGame/Saved/SaveGames ~/SaveGames.old
tar -xzf ~/backups/satisfactory_2026-01-01_12-00-00.tar.gz -C ~/.config/Epic/FactoryGame/Saved
exit
sudo systemctl start satisfactory.service

Then load the game you want from the Server Manager. Once you have checked the result, you can delete ~/SaveGames.old.

Server Update

Before stopping the server, save the game from the console with server.SaveGame BeforeUpdate. Then run the following commands, which use the backup.sh script described above:

Terminal
sudo systemctl stop satisfactory.service
sudo -u satisfactory /home/satisfactory/backup.sh
sudo -iu satisfactory
~/steamcmd/steamcmd.sh +force_install_dir /home/satisfactory/satisfactory-server +login anonymous +app_update 1690800 validate +quit
exit
sudo systemctl start satisfactory.service

Troubleshooting

Service won't start

  • Check the logs: sudo journalctl -u satisfactory.service -n 100
  • Check FactoryGame.log in FactoryGame/Saved/Logs/
  • Check disk space and memory: df -h and free -h
  • Check file ownership: sudo chown -R satisfactory:satisfactory /home/satisfactory

Server can't be found from the game

  • Check that it is running: pgrep -f FactoryServer
  • Check that it is listening: sudo ss -plnut | grep -E ':(7777|8888)\b'
  • Check that the firewall allows 7777 on UDP and TCP, and 8888 on TCP

Loading gets stuck

A loading screen that never finishes is usually caused by port 8888 on TCP being closed or filtered. Check this first.

Encryption token missing

This error occurs when you join the server through Join Game. Add the server and join it from the Server Manager instead.

Certificate is not valid yet

Check the time on the server with timedatectl, as well as the time on your computer. If the server's time was wrong, correct it, stop the server, delete ServerSettings.7777.sav and start the server again. You will then have to claim it again.

Lost administrator password

Stop the server, then delete the settings file:

Terminal
sudo systemctl stop satisfactory.service
sudo -u satisfactory rm /home/satisfactory/.config/Epic/FactoryGame/Saved/SaveGames/ServerSettings.7777.sav
sudo systemctl start satisfactory.service

This also erases the server name, the player password, the automatically loaded game and the certificate. Your saves are kept, but you must claim the server again.

SDL Priority Manager Error

Install the 32-bit SDL library, then restart the service:

Terminal
sudo dpkg --add-architecture i386
sudo apt update
sudo apt install -y libsdl2-2.0-0:i386
sudo systemctl restart satisfactory.service

steamclient.so Error

Terminal
sudo -iu satisfactory
mkdir -p ~/.steam/sdk64
ln -sf ~/steamcmd/linux64/steamclient.so ~/.steam/sdk64/steamclient.so
exit
sudo systemctl restart satisfactory.service

SteamCMD Errors

  • state is 0x606: stop the server before updating, or reboot the machine.
  • Unable to determine CPU Frequency. Try defining CPU_MHZ.: run export CPU_MHZ=2000, then run SteamCMD again.

Processor is not compatible

The server does not work on a generic virtual processor such as kvm64. Check the model shown by lscpu. If yours is affected, contact support from your customer area.

Performance Issues

  • Enable Auto Pause to free up the server when nobody is playing
  • Adjust Network Quality
  • Monitor memory with free -h
  • If the factory has grown a lot, upgrade to a plan with more RAM and a faster processor