StarRupture Dedicated Server Setup (Linux, Docker & SteamCMD)

Running a StarRupture dedicated server keeps your factory online 24/7, even when you're offline. This guide covers Windows and Linux deployment with SteamCMD and Docker, plus networking and troubleshooting.

One high-friction detail deserves to be stated early: a dedicated server process can be healthy and still do nothing useful until you connect from the game client, open Manage Server, and either Start New Session or Load Session.

Build note: Official StarRupture support currently states that there is no Dedicated Server available for the Public Test Branch. Use the default public build for server hosting unless Creepy Jar announces PTB server support explicitly.

Trust boundary: Dedicated server packaging, launch behavior, and port expectations can change across patches. Use this guide as a live-baseline setup path, then verify launch flags, config output, and session behavior on your current build.

Update 2 note: Hotfix 0.3.5, released 2026-10-05, covers crashes, stability, pillar and platform calculations, and dedicated-server habitat cleanup. Setup steps below are unchanged. See the Update 2 status page.

Dedicated Server Setup: Pick the Right Path First

• Choose Windows + SteamCMD if you want the shortest path from install to joinable server.
• Choose Linux + Proton/Wine if you already manage Linux infrastructure and are comfortable reading prefixes, logs, and restart behavior.
• Choose Docker if reproducible deployment and easier restarts matter more than the simplest first-time setup.

If your real search query is "how do I get a StarRupture dedicated server online fast?", Windows is usually the lowest-friction answer. Linux and Docker are useful, but they are not the path of least troubleshooting.

Why Run a Dedicated Server?

The core value of a dedicated server in StarRupture is time compounding:

• Factories continue producing while you're away
• Mining drills keep extracting resources
• Enables large-scale resource stockpiling
• Supports multiplayer co-op gameplay

StarRupture Server Hosting Options (Self-Host vs Managed)

If you're searching for StarRupture server hosting, you generally have two routes:

Option 1: Self-Hosted Dedicated Server (Best value)

• Full control over saves, mods, and restart schedule
• Lower long-term cost if you already have hardware
• Best for advanced players comfortable with ports/logs

Option 2: Managed Game Server Hosting (Fast setup)

• Faster onboarding and no local network setup
• Provider handles uptime, backups, and hardware maintenance
• Usually higher monthly cost and less low-level control

If your goal is maximum flexibility and lower TCO, start with self-hosting using SteamCMD. If your goal is quickest multiplayer uptime, managed hosting can be worth it.

Need a practical provider scoring framework first? Read:

• StarRupture Server Hosting: Self-Host vs Managed

Hardware Requirements

Minimum Specifications

Pre-Flight Decision Check

Before you download anything, answer these:

1. Do you need a 24/7 world, or just a repeatable co-op session host?
2. Are you choosing Linux because you already trust that environment, or because it sounds more "server-like" than Windows?
3. Do you have a plan for backups, restarts, and log access before players join?

If you cannot answer those cleanly, start with the simplest SteamCMD route on the OS you already know best.

Deployment Method A: SteamCMD on Windows (Recommended)

This is the standard enterprise deployment method for headless servers.

Step 1: Install SteamCMD

Download SteamCMD from Valve's website and extract it.

Step 2: Create Update Script

Create a file called update_starrupture.bat:

steamcmd +force_install_dir C:\StarRuptureServer +login anonymous +app_update 3809400 validate +quit

Note: As of the official StarRupture support article (published February 13, 2026), SteamCMD dedicated server examples use AppID 3809400.

StarRupture Dedicated Server AppID FAQ

• AppID used in SteamCMD examples: 3809400
• If deployment fails, validate app updates first, then confirm launch parameters and server binary path.
• Always re-check the official game channel and patch notes for any server packaging changes.

Step 3: Run the Script

Execute the batch file to download server files.

Step 4: First Launch

Run the server with parameters to generate config files:

.\StarRuptureServer.exe -log -ServerName="MyIndustrialEmpire" -MaxPlayers=8

What "working" actually means

Do not stop at "the EXE stayed open." A real dedicated server baseline looks like this:

• config files generate successfully
• logs continue updating instead of crashing out immediately
• a client can reach Manage Server
• you can create a session/world and reconnect to it

If one of those fails, treat the setup as incomplete.

Deployment Method B: Steam Client (GUI Method)

For users unfamiliar with command line:

1. In Steam Library, filter by "Tools"
2. Search for "StarRupture Dedicated Server"
3. Download and launch directly from Steam

Deployment Method C: Linux via Proton/Wine

Official Linux server binaries are not yet available for StarRupture. The community-supported solution uses Proton (Steam's compatibility layer) to run the Windows server binary on Linux.

Requirements

• Linux distro with glibc 2.33+ (Ubuntu 22.04+, Debian 12+, Fedora 38+)
• Steam installed, or standalone Proton downloaded
• SteamCMD installed

Method C1: SteamCMD + Proton Prefix

# 1. Create a Proton prefix
mkdir -p ~/starrupture-prefix
export STEAM_COMPAT_DATA_PATH=~/starrupture-prefix
export STEAM_COMPAT_CLIENT_INSTALL_PATH=~/.steam/steam

# 2. Download Proton-GE (recommended over standard Proton for server use)
# https://github.com/GloriousEggroll/proton-ge-custom/releases
# Extract to ~/.steam/root/compatibilitytools.d/

# 3. Download StarRupture server via SteamCMD
steamcmd +force_install_dir ~/StarRuptureServer +login anonymous +app_update 3809400 validate +quit

# 4. Run server with Proton
~/.steam/root/compatibilitytools.d/GE-Proton9-*/proton run   ~/StarRuptureServer/StarRuptureServer.exe   -log -ServerName="LinuxServer" -MaxPlayers=8

Method C2: Wine Standalone (without Steam)

# Install Wine and winetricks
sudo apt install wine64 winetricks   # Ubuntu/Debian

# Install required Visual C++ runtime inside Wine prefix
winetricks vcrun2022

# Run the server executable
wine64 ~/StarRuptureServer/StarRuptureServer.exe   -log -ServerName="WineServer" -MaxPlayers=8

Linux-Specific Troubleshooting

Problem: Server fails with DXVK error or d3d11.dll missing Solution: Install DXVK inside your Wine/Proton prefix:

winetricks dxvk

Problem: Server binds to wrong IP (ZeroTier or VPN adapter) Solution: Force bind to your physical NIC:

wine64 StarRuptureServer.exe -MultiHome=192.168.1.X -Port=7777

Problem: Server crashes immediately on Linux Solution: Check that you have all required C++ redistributables:

winetricks vcrun2015 vcrun2017 vcrun2019 vcrun2022

Deployment Method D: Docker

Docker deployment is ideal for always-on VPS hosting. It containerizes the Wine environment for reproducible deployments.

docker-compose.yml Example

version: "3.9"
services:
  starrupture-server:
    image: cm2network/steamcmd:root   # community base image
    container_name: starrupture
    restart: unless-stopped
    environment:
      - STEAMAPPID=3809400
      - SERVERNAME=MyDockerServer
      - MAXPLAYERS=8
      - SERVERPASSWORD=
      - ADMINPASSWORD=changeme123
    ports:
      - "7777:7777/udp"
    volumes:
      - ./server-data:/home/steam/starrupture-server/Saved

# Deploy
docker compose up -d

# View logs
docker compose logs -f starrupture-server

# Stop
docker compose down

Note: Community Docker images for StarRupture are maintained on GitHub. Search starrupture-server docker for the latest maintained images that include Wine/Proton and auto-update scripts.

Docker Volume Setup

Mount ./server-data to persist saves between container restarts. Without this, your world will reset every time the container restarts.

Server Configuration: DSSettings.txt Reference

The DSSettings.txt file controls core server behavior. It is auto-generated in .../Saved/Config/WindowsServer/ on first launch.

Full Parameter Reference

Tip: To reset player access: delete PlayerPassword.json. To reset admin access: delete DSSettings.txt and relaunch — it will regenerate with a fresh prompt.

Port Forwarding Summary

You must open the same port you configured in launch arguments (official example uses UDP 7777):

Tip: If players cannot connect, confirm that launch parameter, firewall rule, router forwarding, and join target all use the same port value.

Initial Session Setup (Critical!)

This is where most users make mistakes. The server starting doesn't mean your world is ready.

Step 1: Manage Server from Client

1. With server running, open the game on your player PC
2. Click "Join Game" → "Dedicated Server"
3. Enter server IP and port (default example: 7777)
4. Click "Manage Server" button
5. Set admin password, server password
6. Click "Start New Session"

Important: The server is just a container. A "Session" is your actual save/world. This step remotely commands the server to create a new save.

Troubleshooting by Symptom First

Use the symptom first, not the install method, when something breaks:

Server process is up, but no real world exists

• confirm you completed Manage Server -> Start New Session
• verify you are editing the same config/save location the active server binary is using
• re-check password flow if the management UI refuses to initialize the session

Players can see the server, but cannot join reliably

• verify port, firewall rule, router forward, and join target all match
• force the bind IP with -MultiHome if the server prefers a VPN or virtual NIC
• try direct IP join before trusting browser visibility

Linux, Wine, or Docker setup feels unstable

• read the latest logs before restarting
• verify the prefix/container still points at the expected server files
• separate launch failures from networking failures before changing firewall rules

Troubleshooting

Windows Issues

Problem: Server crashes on startup, log shows DLL missing Solution: Install Visual C++ Redistributables (2015-2022) x64

Problem: Can't find server in browser list Solution: Ensure Epic Online Services (EOS) is installed. Even on Steam, the game may use EOS for NAT traversal. Also verify your configured server port is open and forwarded.

Problem: Stuck on loading screen when joining Solution: Check if using VPN (e.g., ZeroTier). The game may bind to the wrong virtual NIC IP. Force bind to physical IP using -MultiHome=YOUR.LOCAL.IP launch parameter.

Problem: Server runs but nobody can connect Solution:

1. Verify your configured server port is forwarded (official example: UDP 7777)
2. Check Windows Firewall allows the server executable and your configured UDP port (official example: 7777)
3. Try direct IP connection instead of server browser
4. Temporarily disable Windows Firewall to isolate the issue

Problem: Max players setting not applying Solution: Edit MaxPlayers in DSSettings.txt and restart the server. The in-game UI setting may not persist correctly — always verify in the config file.

Linux/Proton Issues

Problem: wine: cannot find '/home/user/StarRuptureServer/StarRuptureServer.exe' Solution: SteamCMD may have downloaded to a subdirectory. Check ~/StarRuptureServer/ subfolders or run find ~/StarRuptureServer -name "*.exe" | grep -i server

Problem: Server starts but immediately exits with no log output Solution: Add -log to your launch arguments. Logs write to Saved/Logs/StarRupture.log. Read the last 50 lines with: tail -50 Saved/Logs/StarRupture.log

Problem: Server runs but crashes after ~10 minutes on Linux Solution: This is often a memory allocation issue. Set ulimit -n 65536 before launching and ensure your host has at least 4GB free RAM.

Ongoing Maintenance and Honest Expectations

Dedicated server support is useful, but it should not be treated as permanently settled from old setup notes alone.

• validate your launch routine again after patches
• keep backups before changing slots, passwords, or ports
• expect Linux compatibility layers to need more hands-on verification than Windows
• verify community Docker images and older launch advice before adopting them unchanged

Best Practices for 24/7 Operation

Auto-Restart (Windows)

Use Windows Task Scheduler to create a task that runs StarRuptureServer.exe on system startup and on failure.

Auto-Restart (Linux systemd)

# /etc/systemd/system/starrupture.service
[Unit]
Description=StarRupture Dedicated Server
After=network.target

[Service]
Type=simple
User=steam
WorkingDirectory=/home/steam/StarRuptureServer
ExecStart=/usr/bin/wine64 StarRuptureServer.exe -log -ServerName=MyServer -MaxPlayers=8
Restart=on-failure
RestartSec=10s

[Install]
WantedBy=multi-user.target

sudo systemctl enable starrupture
sudo systemctl start starrupture
journalctl -u starrupture -f  # Live log stream

Performance Optimization

• Set auto-save interval to 5-10 minutes (AutoSaveInterval=300 in DSSettings.txt)
• Limit conveyor belt lengths where possible — long belts increase simulation overhead
• Use storage depots as buffers to break up item flow
• Monitor RAM usage: conveyor items in transit stay in memory. Factories with 500+ items in motion use 2-4GB RAM
• Consider using a UPS to prevent save file corruption during power outages

What To Open Next for Dedicated Servers

• Server Not Showing Fix — use this when the server runs but discovery or direct join is failing
• Server Lag Fix Guide — use this when players join successfully but rubberbanding or desync starts
• Linux Dedicated Server Guide — switch here if your real goal is Proton/Wine hosting rather than Windows SteamCMD
• Controller & Steam Deck Guide — useful for co-op players joining from couch or handheld setups