keepcalculator

06 Numbers and Powers

Run Satisfactory Server in Docker on a VPS

Card No. 06·73683 · Updated · Standard formula, shown below

This guide walks you through setting up a dedicated Satisfactory server inside a Docker container on a VPS (Virtual Private Server). You’ll end up with a persistent, always-on game server that you and your friends can join anytime, without needing your PC to stay on. We’ll cover the initial setup, configuration, common pitfalls, and how to troubleshoot issues.

What You’ll Need

  • A VPS with at least 4 CPU cores, 8 GB of RAM, and 20 GB of free storage (Satisfactory is resource-hungry, especially with multiple players).
  • Ubuntu 22.04 or 24.04 (or another modern Linux distribution) installed on the VPS.
  • Root or sudo access to the VPS.
  • A basic familiarity with the Linux command line.
  • Docker and Docker Compose installed on your VPS. If you don’t have them, install them first using your distribution’s package manager.
  • SteamCMD access (the Docker image you’ll use handles this automatically).
  • Your Steam account credentials (the server requires them to download the game files).

Step-by-Step

  1. Install Docker and Docker Compose (if not already installed). On Ubuntu, run:
    sudo apt update && sudo apt install docker.io docker-compose-v2 -y

    Enable Docker to start on boot: sudo systemctl enable --now docker.

  2. Create a directory for the server files. For example: mkdir ~/satisfactory-server && cd ~/satisfactory-server.
  3. Create a docker-compose.yml file in that directory. Use a text editor (like nano or vim) and paste the following configuration:
    version: '3.8'
    services:
      satisfactory:
        image: wolveix/satisfactory-server:latest
        container_name: satisfactory
        restart: unless-stopped
        ports:
          - "7777:7777/udp"
          - "15777:15777/udp"
          - "15000:15000/udp"
        environment:
          - MAXPLAYERS=4
          - STEAMUSERNAME=your_steam_username
          - STEAMPASSWORD=your_steam_password
          - SERVERPASSWORD=your_server_password
          - ADMINPASSWORD=your_admin_password
          - AUTOSAVEONTERMINATE=true
          - AUTOSAVEINTERVAL=300
        volumes:
          - ./satisfactory-data:/home/steam/.config/Epic/FactoryGame/Saved/SaveGames/server
        

    Replace the environment variables with your actual Steam credentials and desired passwords. The SERVERPASSWORD is what players will need to join; ADMINPASSWORD is for in-game admin commands.

  4. Start the server. Run docker compose up -d. The first time you run this, Docker will pull the image and the server will download the game files—this can take several minutes.
  5. Check the logs to see if the server started successfully: docker logs -f satisfactory. Wait until you see a message like “Server started” or “HTTP server listening”.
  6. Connect to the server. In Satisfactory, open the Session Manager, click on “Server”, and enter your VPS’s IP address. The default port is 15777 for the server browser, but the game uses 7777 for actual gameplay—the compose file maps both.
  7. Set up port forwarding (if your VPS has a firewall). Open UDP ports 7777, 15777, and 15000. On a typical Ubuntu VPS with UFW, run:
    sudo ufw allow 7777/udp && sudo ufw allow 15777/udp && sudo ufw allow 15000/udp
  8. Save your game. The server auto-saves by default, but you can also trigger a save by running docker exec -it satisfactory save (if the image supports it) or by using the in-game admin command SaveGame.

Common Mistakes

  • Using the wrong Steam credentials—the server will fail to download the game if the username or password is incorrect. Make sure you’re using the correct account that owns Satisfactory.
  • Not opening UDP ports—Satisfactory uses UDP, not TCP. Opening TCP only will not work.
  • Insufficient RAM—Satisfactory servers can easily use 4-6 GB of RAM, especially with multiple players. If your VPS has less, the server may crash or run very slowly.
  • Forgetting to set restart: unless-stopped—without this, the server won’t restart automatically after a reboot or crash.
  • Not using a volume for save data—if you don’t mount a volume, your save files will be lost when the container is removed.

Tips

  • Use a dedicated Steam account for the server if possible, to avoid conflicts with your personal account.
  • Set a strong admin password—anyone with it can change game settings or kick players.
  • Adjust the autosave interval to your preference. The default is 300 seconds (5 minutes). Lower it if you’re worried about losing progress, but note that saving can cause brief lag.
  • Monitor resource usage with docker stats satisfactory to see if you need to upgrade your VPS.
  • Keep the server updated by pulling the latest image periodically: docker compose pull && docker compose up -d.
  • Back up your save files regularly by copying the satisfactory-data folder to another location.

Troubleshooting

  • Server won’t start—Check the logs with docker logs satisfactory. If you see a Steam authentication error, double-check your credentials. If it’s a disk space issue, free up space.
  • Can’t see the server in the in-game browser—Verify that the ports are open and that you’re using the correct IP. Try connecting directly via IP:15777 in the game’s server browser.
  • Server crashes on load—This often happens when the save file is corrupted or the world is too large. Try starting a new world to see if that works. If it does, restore a backup.
  • Players can’t join—Ensure the server password is correct and that the ports are open. Also, check that your VPS’s firewall isn’t blocking incoming UDP traffic.
  • High latency or lag—Check CPU and RAM usage. If the VPS is overloaded, consider upgrading or reducing the max player count.
  • Container keeps restarting—Run docker logs satisfactory to see the error. Common causes include invalid environment variables or missing game files. Try removing the container and recreating it with docker compose down && docker compose up -d.

Frequently Asked Questions

Do I need to own Satisfactory to run a server?

Yes, you need a Steam account that owns Satisfactory. The server downloads the game files through SteamCMD, which requires a valid license.

Can I run the server on Windows?

Yes, but this guide is for Linux VPS. Docker works on Windows, but the commands and setup differ slightly. The same Docker image should work, but you’ll need to adapt the volume paths and firewall settings.

How many players can I host?

It depends on your VPS resources. A 4-core, 8 GB RAM VPS can typically handle 4-8 players. More players require more CPU and RAM. You can set the MAXPLAYERS environment variable, but the server may struggle if you exceed its capacity.

Can I use mods on my server?

Yes, but it’s more complex. You’ll need to manually add mod files to the server’s installation directory. The Docker image used here doesn’t include mod support out of the box, so you may need to modify the container or use a different image.

How do I update the server to the latest version?

Run docker compose pull && docker compose up -d. This will fetch the latest image and recreate the container. Your save files will be preserved as long as the volume is mounted correctly.

What are the default ports for Satisfactory?

The game uses UDP port 7777 for gameplay, 15777 for the server browser, and 15000 for Steam networking. Make sure all three are open in your firewall.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →