Installer un serveur dédié Satisfactory pour jouer en coopération

The Satisfactory server software lets a factory session keep running even when nobody is logged in as host, so the whole crew can drop in and out on their own schedule instead of waiting on one person to launch the game. This guide covers installing the software, opening the right ports, claiming the instance from inside the game, and tuning ServerSettings and save behavior for smooth co-op play.

How the Satisfactory Server Software Works

Coffee Stain ships a standalone build of the Satisfactory engine that runs headless, without a graphical interface, as its own process separate from the client you play on. This is what people usually call the "FactoryServer" executable: on Linux it's FactoryServer.sh, on Windows it's FactoryServer.exe. It loads the same Unreal Engine simulation as the regular client but strips out rendering, so it can run on modest CPU allocations while still simulating belts, machines and power grids 24/7.

A single instance hosts one active save at a time. If you want several communities or test environments running in parallel, you need several instances listening on different UDP port ranges, each with its own working directory and save folder. Visibility is handled per session: LAN only, Friends Only, or Public, which determines whether the session shows up in the in-game browser or has to be joined by direct address.

If you'd rather skip the manual Linux setup and jump straight into building, Fly-Serv's Satisfactory server hosting ships with the software pre-installed, Ryzen CPU allocation and anti-DDoS protection active from the first boot.

Installing and Launching the Satisfactory Server Software

Getting the files via SteamCMD

The server build is distributed as its own Steam app, separate from the regular game client, which means you don't need a Satisfactory license to download it. On a Linux machine or VPS, grab it with SteamCMD:

mkdir -p ~/satisfactory-server
cd ~/satisfactory-server
steamcmd +force_install_dir ~/satisfactory-server +login anonymous +app_update 1690800 validate +quit

App ID 1690800 is the dedicated build (listed under "Satisfactory Dedicated Server" on Steam). Once the download finishes, the folder contains FactoryServer.sh at the root.

Required ports and firewall rules

Satisfactory communicates over UDP only. Three ports matter for a working session:

Port	Protocol	Purpose
7777	UDP	Main game traffic between the client and the session
15000	UDP	Beacon port, used for connection negotiation
15777	UDP	Query port, used by the server browser and status checks

On a self-managed Linux box, open them with ufw before launching anything:

sudo ufw allow 7777/udp
sudo ufw allow 15000/udp
sudo ufw allow 15777/udp
sudo ufw reload

If you're running the process on Windows, allow the same three UDP ports through Windows Defender Firewall for FactoryServer.exe.

Launching and keeping the process alive

From the install folder, the basic launch command looks like this:

./FactoryServer.sh -unattended -nosteamclient -game -server -log -ServerQueryPort=15777 -BeaconPort=15000

To avoid losing the session every time the terminal closes or the machine reboots, wrap it in a systemd unit instead of running it in a raw terminal session:

[Unit]
Description=Satisfactory server process
After=network.target

[Service]
User=satisfactory
WorkingDirectory=/home/satisfactory/satisfactory-server
ExecStart=/home/satisfactory/satisfactory-server/FactoryServer.sh -unattended -nosteamclient -game -server
Restart=on-failure

[Install]
WantedBy=multi-user.target

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

This is also the kind of lifecycle automation a management panel handles for you automatically, including restarts, log access and file editing from a browser — which is what the Pterodactyl VPS option is built for if you already manage several game processes on the same machine.

Claiming Your Satisfactory Server and Co-op Setup

Once the process is listening, the first player needs to claim it before anyone can build. Open the regular game client, go to the main menu, and select Server Manager. Add a new connection using the machine's IP address and the game port, for example 203.0.113.10:7777.

On first connection, the session shows up as unclaimed. You'll be prompted to:

• Set an admin password for the session (keep this strong, it controls remote administration).
• Name the session.
• Choose or create the save that will be loaded.

Once claimed, that password is required for anyone connecting through Server Manager with administrative rights. Regular players only need the session's visibility set correctly — Friends Only works for most private groups, Public if you want the session discoverable in-game.

For co-op groups, it's worth adding every teammate's Epic or Steam friend list before the first session so the Friends Only visibility actually surfaces the game to them without sharing the raw IP and port combination in chat.

Save Management and ServerSettings Configuration

Where saves live

Save files sit inside the server's working directory, typically under:

FactoryGame/Saved/SaveGames/server/<SessionName>/

Each save grows as the factory expands, so it's worth checking file size periodically and keeping scheduled copies outside the working directory, in addition to whatever automated backup routine your setup already runs. A panel-managed instance typically handles this through scheduled automated backups accessible from the file manager, which saves you from writing your own cron job for it.

Tuning ServerSettings

From the Server Manager menu, selecting Advanced Game Settings on a claimed session exposes the ServerSettings that actually matter day to day:

• Autosave interval — how often the world is saved automatically, independent of manual saves.
• Autosave on disconnect — forces a save whenever the last player leaves, useful before planned restarts.
• Network Quality — adjusts replication detail, worth lowering on higher player counts to reduce desync on marginal connections.
• Disable Seasonal Events — toggles time-limited content outside its usual window.
• Crash Reporting — can be left on to help diagnose a persistent crash loop.

These values can also be set at launch through command-line arguments if you prefer scripting the configuration instead of clicking through the menu each time, which is handy when spinning up a fresh session from a template. Full argument syntax and every available flag are documented on the official Satisfactory wiki.

For anyone running several game processes side by side, keeping the same discipline — regular backups, a documented admin password, UDP ports locked down to what's actually needed — applies whether it's Satisfactory, Valheim server or any other title in the All our game servers catalog.

Getting a Satisfactory session running smoothly comes down to a handful of repeatable steps: pull the right build, open the three UDP ports, claim the session with a solid admin password, and keep ServerSettings and backups under control. Get that foundation right once, and the rest is just building bigger belts.

FAQ

Which ports absolutely need to be open for Satisfactory co-op to work?

UDP 7777 for game traffic, UDP 15000 for the beacon port, and UDP 15777 for the query port. All three need to be reachable from the internet or LAN depending on your visibility setting, and all three are UDP, not TCP.

I lost the admin password, can I still manage the session?

Not through Server Manager without it. The password is stored on the instance itself, so if you have file access to the working directory you can reset the session's save-tied admin credentials by editing the relevant save metadata, or simply start a fresh claim on a new save if recovery isn't critical.

Why does my save keep growing and slowing down autosaves?

Large factories with many foundations and belts naturally produce bigger save files, which take longer to write during autosave. Increasing the autosave interval slightly and making sure the storage behind the process is fast enough usually keeps autosave pauses short.