Colony Survival Dedicated Server Setup Guide (2026)

A Colony Survival world often outgrows local hosting before it outgrows its player list. Expanding colonies, mods, backups, and reliable access can quickly turn one player’s PC into a bottleneck.

A dedicated server runs the authoritative world independently, keeping it available while the server process remains online. The official free server tool uses Steam App ID 748090, while the main game uses App ID 366090, and supports 64-bit Windows and Linux.

In version 0.17, SteamOnline uses Steam P2P relay for normal internet joins, so router port forwarding is generally unnecessary. Port 27005 remains active, and the simulation pauses when the server is empty by default.

Verified against server version 0.17.0.3 on July 23, 2026, this guide covers Steam Tools, SteamCMD, Docker, and LinuxGSM. It also explains configuration, networking, backups, updates, RCON, mods, migration, performance monitoring, and troubleshooting.

Colony Survival Dedicated Server: Quick Facts

What Changed in Colony Survival 0.17

Colony Survival 0.17 is live, and this guide was tested with dedicated server version 0.17.0.3. Version 0.17 introduced Steam P2P relay, reworked public server discovery, removed automatic UPnP handling, and removed ServerQueryPort.

Colony Survival Multiplayer in Practice (What Actually Works in 2026)

Colony Survival supports online multiplayer, and dedicated hosting can make sessions more reliable when ports, config, versions, and mods are handled correctly.

You can build colonies with friends, either working on a shared settlement or running separate colonies within the same world.

The experience depends on the host hardware, network, configuration, and world load. Local hosting can become less convenient as colonies and uptime expectations grow, while a dedicated server separates hosting from the player’s PC.

• Player Limits: The server config includes MaxPlayerCount, with 10 used in current examples. You can change this setting, but practical capacity depends on CPU, RAM, network quality, world size, and mods.
• Persistence: The authoritative world lives on the server. Players can reconnect whenever the server process is online, although the simulation pauses when the server is empty by default.
• Save Handling: Saves are automatic and stored server-side. The server holds the authoritative live world, but administrators can copy the complete world folder between compatible client and dedicated installations.
• Sync Behavior: The server handles all game logic. If it lags, everyone feels it. One player’s poor connection is less damaging than server-side lag, but it can still cause rubberbanding, disconnects, or support issues for that player.

Common Multiplayer Misconceptions (Still Circulating)

• “It’s LAN-only.” False. The game uses Steam networking and supports full online multiplayer.
• “Only four players can join.” Usually wrong. Player capacity depends on MaxPlayerCount, hardware, network quality, world size, and mods.
• “Everyone has their own save.” No. The server holds the authoritative world used by connected players.

What’s Still True

• The game pauses when no one is online (unless you disable that).
• Keep the server and clients on compatible game versions, and follow each mod’s client and server installation requirements.
• Local hosting is more likely to lag as colonies grow, especially if the host PC is also running the game client or other apps.

Colony Survival Dedicated Server Requirements

Colony Survival server performance depends mainly on CPU capability, available memory, storage speed, and world complexity.

CPU

Colony Survival benefits from strong per-core performance, but worker and pathfinding tasks can also use multiple threads. Choose a modern CPU with fast cores instead of assuming the server is strictly single-threaded. For consistent high-clock performance in simulation-heavy workloads, compare RedSwitches AMD Ryzen dedicated servers.

Health Check: Run /tps in-game with the required permission. The current server settings target 30 ticks per second, so sustained readings materially below that target indicate simulation lag.

GPU: The dedicated server runs headlessly and does not require a dedicated GPU.

RAM

Community guidance places a basic server near 2 GB of RAM, but Pipliz does not publish a formal dedicated-server sizing table. Memory use can rise with world growth, colonists, and mods.

• 2 GB: community-reported baseline for a basic server
• 4–6 GB: practical planning range for growing private worlds
• 8 GB+: practical starting point for heavily modded or long-running worlds

Storage

Slow or heavily contended storage can lengthen saves and loading, especially as world data grows.

• SSD: Recommended baseline
• NVMe: Provides faster world, log, and backup I/O

Network & Latency

Upload Matters More Than Download

The server sends world and player-state data to connected players, so stable upload capacity, low packet loss, and consistent latency matter. Pipliz does not publish a verified per-player bandwidth requirement.

Wired > Wi-Fi

Wi-Fi can introduce variable latency and packet loss. Use wired Ethernet where possible for more consistent connectivity.

Simulation Load vs. Network Latency

Large zombie attacks and pathfinding can raise simulation load, while an unstable connection can cause delayed updates for individual players. Monitor server TPS separately from client latency and packet loss.

SteamOnline and Direct Access

SteamOnline registers the server and uses Steam P2P networking for normal internet joins. Firewall rules and Docker mappings remain relevant for container exposure, direct connections, LAN access, and RCON.

• If the server is not visible, first check Steam initialization, NetworkType, ServerListPublicly, and the server log.
• Check for CGNAT only when troubleshooting direct-IP access because Steam P2P relay can normally operate without a public inbound route.

Persistence, Pausing, and Backups

Pause-When-Empty Is On by Default

If no players are online, the simulation pauses by default. To change this behavior, open gamedata/settings/server.json, locate UseServerPausing inside the Time section, and change its existing value from true to false. Back up the file first because validation or game updates may restore packaged settings.

Backups Protect Long-Running Worlds

Interrupted writes, incompatible mods, administrative mistakes, or failed updates can damage a world or make it unloadable.

• Backup daily
• Always before updates or mod installs
• Test your restore path regularly

How to Set Up a Colony Survival Dedicated Server

Use Dedicated Server App ID 748090 rather than the main game App ID 366090 when installing through SteamCMD.

Windows Dedicated Server (Steam Tool)

The Windows dedicated server is available directly through Steam under:

Steam → Library → Tools → Colony Survival Dedicated Server

When This Method Makes Sense

• Convenient way to test multiplayer on Windows
• Runs headlessly because the former dedicated-server GUI is no longer available
• Suitable for short sessions, small private servers, and manual hosting

Where It Breaks Down

• No built-in automation for backups or restarts
• Server stops if the PC sleeps, reboots, or updates
• Less ideal for unattended 24/7 uptime unless restart, update, and sleep settings are configured properly
• Modded servers require careful testing after game and mod updates

Important Windows Note

Allow the Colony Survival server executable through Windows Defender Firewall, particularly if you use direct connections, LAN discovery, or RCON.

Quick Start (Windows Headless Server)

1. Open Steam → Library → Tools
2. Install Colony Survival Dedicated Server
3. Open the dedicated server installation folder
4. Copy gamedata/help/hosting_docker/server.config.json into the server root, then set the world and server names
5. Set NetworkType to SteamOnline and configure the listing options
6. Run colonyserver.exe -batchmode -nographics +server.config "C:\Path\To\server.config.json"

For long-term hosting, an automated Linux service, Docker container, or configured LinuxGSM installation is easier to maintain than a manually started server.

Linux Dedicated Server (SteamCMD)

Create a dedicated user before installing the server files:

sudo useradd -m -s /bin/bash colonyserver

Some manual SteamCMD installations require 32-bit compatibility libraries even though the Colony Survival server is 64-bit. On Ubuntu or Debian, install them from an account with sudo access:

sudo apt-get update && sudo apt-get install -y lib32gcc-s1 lib32stdc++6

Switch to the dedicated user:

sudo -iu colonyserver

Use Valve’s SteamCMD command-line tool with the dedicated server App ID:

steamcmd +force_install_dir /home/colonyserver/server +login anonymous +app_update 748090 validate +quit

Copy the current configuration template:

cp /home/colonyserver/server/gamedata/help/hosting_docker/server.config.json /home/colonyserver/server/server.config.json

Start the server with:

/home/colonyserver/server/colonyserver.x86_64 -batchmode -nographics +server.config /home/colonyserver/server/server.config.json

Linux provides a lightweight, scriptable environment for VPS, dedicated servers, and persistent worlds. It is well suited to automated updates, backups, monitoring, and service management. An unmanaged dedicated server is a practical option for administrators who want full control over SteamCMD, Docker, service scripts, updates, and backups.

Why Administrators Choose Linux

• Greater control over update and reboot scheduling
• Headless operation by default
• Easy scripting for backups and restarts
• Straightforward process limits and resource monitoring
• Standard platform for production game servers

Common Pitfalls and Fixes

Steam API Initialization FailureIf the log reports a missing steamclient.so file, update or validate the SteamCMD installation first. If initialization still fails, use the official Docker image or copy the correct 64-bit Steam library from a verified SteamCMD installation.

Keep the Server Running After SSH Disconnect (Critical)

If you start the server manually in SSH, the server can stop when the session closes unless you use tmux, screen, systemd, Docker, or LinuxGSM.

# Using tmux (recommended)

tmux new -s colony

/home/colonyserver/server/colonyserver.x86_64 -batchmode -nographics +server.config /home/colonyserver/server/server.config.json

# Detach: Ctrl+b then d

# Reattach later:

tmux attach -t colony

Running the process inside a persistent session prevents it from stopping when the SSH connection closes. See the official tmux getting-started guide for additional session commands.

LinuxGSM (Automation Option)

LinuxGSM provides commands for updates, restarts, monitoring, and backups, but administrators must configure the required schedules and settings.

When to Use LinuxGSM

• Public or long-running servers
• Modded worlds
• VPS or dedicated hosting
• Admins who want minimal manual maintenance

Core Commands

./colserver start

./colserver stop

./colserver update

./colserver monitor

Review the generated LinuxGSM configuration before launch because older defaults may still reference the removed 27004 query port or ServerSteamPort.

Updating a SteamCMD InstallationStop the server and back up the world before significant updates. Then run:steamcmd +force_install_dir /home/colonyserver/server +login anonymous +app_update 748090 +quitUse validate for the first installation or when repairing missing or corrupted files.

Docker Setup

Pipliz provides a Docker-based hosting path using pipliz/colony-survival-dedicated-server and server.config.json. This is a strong option for VPS, NAS, and dedicated server deployments.

• Current Docker port mappings:27005/tcp27005/udp

Mount server.config.json into the container and keep save data in a persistent Docker volume.

The packaged Compose example still sets SERVER_BRANCH to "0.16.1". Remove that value or set SERVER_BRANCH to an empty string so SteamCMD follows the current public branch.

services:

colony-survival:

image: pipliz/colony-survival-dedicated-server:latest

restart: unless-stopped

stop_grace_period: 2m

environment:

SERVER_BRANCH: ""

SERVER_CONFIG_PATH: /server/server.config.json

SERVER_SKIP_UPDATE: "false"

SERVER_VALIDATE: "false"

ports:

- "27005:27005/tcp"

- "27005:27005/udp"

volumes:

- steamcmd:/steamcmd

- server-install:/server

- ./server.config.json:/server/server.config.json:ro

volumes:

steamcmd:

server-install:

server.config.json Basics

The current config format uses NewOptions and ServerSettings.

NewOptions controls the world name, seed, difficulty, and world-generation options.

ServerSettings controls the server name, password, IP binding, game port, VAC setting, player limit, draw distance, network type, browser visibility, and RCON password.

Copy the complete template from gamedata/help/hosting_docker/server.config.json instead of building the file from an abbreviated example.

In the current template, confirm ServerGamePort is 27005, NetworkType is SteamOnline, and configure ServerListPublicly, ServerListLAN, ServerListFriends, and RCONPassword for the intended access method.

Important configuration fields:

• WorldName: Sets the save folder and world name.
• Seed: Accepts text or a number for world generation.
• DifficultyKey: Uses 0 for Peaceful, 1 for Low, 2 for Normal, 3 for High, or 4 for Very High.
• ServerName: Sets the name shown to players.
• ServerPassword: Restricts access to players with the password.
• ServerIP: Keep 0.0.0.0 unless the host has multiple network interfaces.
• ServerGamePort: Uses 27005 by default.
• MaxPlayerCount: Uses 10 in the current template.
• NetworkType: Use SteamOnline for normal internet hosting.
• ServerListPublicly: Set true to appear in the public server browser.
• ServerListLAN: Enables LAN discovery.
• ServerListFriends: Enables Steam friends discovery.
• RCONPassword: Leave blank when RCON is not required.

Networking Explained (Why “Connection Timed Out” Happens)

Colony Survival connection failures can involve Steam initialization, configuration, passwords, version compatibility, mods, or direct-network rules.

Current Networking and Port Use

Version 0.17 no longer includes ServerQueryPort. ServerGamePort defaults to 27005, while normal internet joins use Steam P2P relay without requiring router forwarding.

Firewall Configuration for Direct, LAN, and RCON Access

Direct connections, LAN access, and RCON can fail if the operating system firewall blocks the configured server port. Ubuntu administrators can use the official UFW firewall documentation to create, inspect, or remove port rules.

Linux (UFW)

sudo ufw allow 27005/tcp

sudo ufw allow 27005/udp

Windows

Allow Colony Survival through Windows Defender Firewall. Public server operators should restrict RCON access and consider DDoS-protected dedicated servers when exposing game services directly.

Verify Direct and SteamOnline Access

External Test

• For direct TCP access, test port 27005 from a device outside the server network. Test normal SteamOnline access through the in-game browser or a Steam invitation because Steam P2P does not require a publicly reachable game port.

Local Test

ss -lntup | grep 27005

If the server is not listening on its configured game port, check the startup command, JSON configuration, and server log before testing external access.

CGNAT Check

If your router WAN IP does not match your public IP, you may be behind carrier-grade NAT or another upstream NAT layer.

Effects:

• Direct inbound port forwarding may not work
• Direct-IP hosting may require a public inbound route
• Normal Steam P2P hosting can still operate through CGNAT

Solution:

• For direct-IP hosting, use a VPS or hosting provider with a public IP
• Or request a public IP from your ISP

RCON, Server Commands, and Permissions

Once the server is running, use RCON, in-game commands, and permission groups to manage players and administrative access.

Bundled RCON Commands

Colony Survival includes a custom RCON client rather than Valve Source RCON. Connect it using the configured server address, port, and RCONPassword. The bundled client supports:

connect {ip:port} {password}

players

chat {message}

quit_server

Run in-game slash commands through an authorized player account and verify their current syntax with the game’s command list.

Vanilla Command Limitations

Current permission files include save, backup, whitelist, and blacklist capabilities, but exact command syntax can change. Check the current in-game command list and permissiongroups.json before using a command.

Steam64 ID and Player Name Usage

Some administrative actions accept player names, while persistent whitelist and blacklist records use Steam IDs.

Obtain the player’s Steam ID from their profile, the server log, or a reputable Steam ID lookup service.

Setting Permissions

Use the current in-game command list to confirm permission-assignment syntax before changing a player’s group.

Permission Groups:

• Peasant: default players
• King: limited cheats
• God: full control (use sparingly)

The current packaged permissiongroups.json defines Peasant, King, and God. Check the world-specific permission file before assigning custom roles.

Backups and Restoration

Reliable backups protect world progress from failed mod updates, interrupted writes, and administrative mistakes.

What Must Be Backed Up

• Entire gamedata/savegames/{WorldName}/ folder
• server.config.json
• Stop the server before running the following backup commands to avoid copying a save while it is being written.

mkdir -p /home/colonyserver/backups

tar -czf "/home/colonyserver/backups/world-$(date +%Y%m%d-%H%M).tar.gz" -C /home/colonyserver/server/gamedata savegames/WorldName

cp /home/colonyserver/server/server.config.json "/home/colonyserver/backups/server.config-$(date +%Y%m%d-%H%M).json"

Replace WorldName in the archive command with the exact case-sensitive name of the world folder.

If the server uses mods, also copy the active mod files and record their Workshop IDs or versions in the backup directory.

Restoring from Backup

# Stop server

mv /home/colonyserver/server/gamedata/savegames/WorldName /home/colonyserver/server/gamedata/savegames/WorldName_broken

# Extract backup

tar -xzf /home/colonyserver/backups/world-TIMESTAMP.tar.gz -C /home/colonyserver/server/gamedata/

# Restart server

Version Mismatch Check

A client and server version mismatch is one possible cause of a failed connection.

• Server version is shown on startup
• Client version appears in the main menu
• Versions must match exactly

Performance Health Check

Run /tps in-game with the required permission.

TPS scale:

• Near the configured 30 TPS target: healthy
• Sustained readings materially below 30 TPS: investigate simulation load
• Severe sustained drops: inspect CPU, memory, logs, colony load, and mods
• Large colonies, pathfinding, combat activity, and some mods can increase simulation load.

Troubleshooting Guide

When a Dedicated Server Becomes Necessary

Local hosting may become inconvenient as the world grows and players begin expecting persistent access, scheduled backups, and reliable administration. The following signs can help you decide when to move the world to a dedicated server. A gaming dedicated server becomes a practical next step when local hosting can no longer provide the required uptime, performance, or administrative control.

Signs Local Hosting Is No Longer Viable

• Players lose access when the host closes the game, the PC sleeps, or the internet connection drops.
• Large zombie waves coincide with TPS drops, freezing, or delayed combat.
• The host PC reaches sustained CPU, memory, or storage limits while running both the client and server.
• Backups, mod updates, restarts, and administrative access are not being managed consistently.

These signs suggest that local hosting may no longer meet the group’s uptime, backup, and administration requirements.

Workloads to Monitor for Server Lag

• Large colonies with many colonists
• Continuous day/night cycles without pausing
• Active zombie waves + pathfinding running in parallel
• World saves growing large enough to slow backups, loading, or recovery
• Multiple players online while the host PC is also running the game client or other heavy apps

Player Count Scenarios

• 1–2 players: Local hosting is often convenient for casual sessions, provided the host PC and connection remain stable.
• 3–5 players: Monitor the host’s CPU, memory, latency, and world load instead of assuming player count alone will cause synchronization problems.
• 6+ players: Dedicated hosting becomes more convenient when the group expects persistent uptime, backups, moderation, and automated recovery.

Admin Workload Increases with Players

Once players expect uptime, backups, mod updates, and bug fixes, someone has to be the admin. And they need:

• Access to logs
• Save/version control
• Restart automation
• Crash recovery

A desktop PC can be automated, but power, sleep settings, residential networking, and shared resource use make unattended administration harder.

How to Transition Without Downtime

1. Back up your world from gamedata/savegames/{WorldName}/.
2. Move to a VPS or dedicated server. Keep the server and clients on compatible game versions, and preserve the required mod deployment.
3. Transfer save files and configs.
4. Start the server, check the logs, run /tps in-game with the required permission, confirm the save loads, and test one external Steam connection before going live.
5. Notify players and set a maintenance window if needed.

Running Colony Survival Servers on RedSwitches Infrastructure

Installing the Colony Survival Dedicated Server is only the first step. A dependable multiplayer world also needs consistent simulation performance, protected save data, controlled updates, and infrastructure that stays available when players want to return.

Local hosting can work well for small, casual sessions. As colonies expand, mods increase, and players begin expecting persistent access, the limits of a shared PC or residential connection become more noticeable.

Moving to dedicated hardware gives administrators greater control over CPU resources, storage performance, networking, backups, restarts, and recovery.

RedSwitches dedicated servers provide dedicated computing resources, root access, IPMI management, NVMe or SSD storage, high-speed networking, and DDoS protection.

You can deploy Colony Survival through SteamCMD, Docker, or LinuxGSM, automate routine maintenance, test mod updates safely, and recover the server remotely when problems occur.

The right infrastructure will not replace careful configuration or reliable backups, but it gives both the server and its administrators room to grow.

If your Colony Survival world has outgrown player-hosted hardware, RedSwitches provides a stable foundation for keeping the colony online, responsive, and ready for whatever your community builds next.