Don't Starve Together Updated April 27, 2026

Installing Don't Starve Together Dedicated Server

Step-by-step guide to installing a DST dedicated server via SteamCMD on a Pterodactyl panel.

Don't Starve TogetherinstallationSteamCMDsetup

Overview

Don't Starve Together dedicated servers are installed via SteamCMD using AppID 343050. The server runs a headless Linux binary and requires 32-bit compatibility libraries. This guide covers the full install process assuming you are working inside a Pterodactyl/WISP panel egg.

System Requirements

Before installing, confirm your node meets minimum requirements:

  • Disk: ~500 MB for the base server files
  • RAM: 300–400 MB per shard (Master-only servers; add another 300–400 MB if running Caves)
  • OS: Linux (64-bit host with 32-bit lib support)
  • Libraries: lib32gcc-s1 and lib32stdc++6 must be installed on the host node

If your panel egg is missing these libraries, the binary will fail to start with a missing shared object error. Contact your node administrator if you cannot install them yourself.

SteamCMD Install Command

Your panel egg should run the following SteamCMD command to download the server files:

./steamcmd.sh \
  +force_install_dir ./dst \
  +login anonymous \
  +app_update 343050 validate \
  +quit

The validate flag checksums all downloaded files and re-downloads any that are corrupt or missing. Always include it on first install and after updates.

Server Binary

Once SteamCMD completes, the server binary is located at:

./dst/bin/dontstarve_dedicated_server_nullrenderer

This is the headless renderer binary used for dedicated servers. There is no graphical output. If the panel egg uses a startup command, it should reference this binary directly.

Panel Startup Command

A typical startup command for a single-shard (Master-only) server looks like:

./bin/dontstarve_dedicated_server_nullrenderer \
  -cluster Cluster_1 \
  -shard Master \
  -persistent_storage_root /home/container

The -persistent_storage_root flag points to where your cluster folder lives. Adjust this to match your panel's working directory layout.

First-Boot Checklist

Before starting the server for the first time, confirm the following files exist:

  1. cluster_token.txt — contains your Klei server token (see the token guide)
  2. cluster.ini — cluster-level configuration
  3. Cluster_1/Master/server.ini — shard configuration for the Master shard
  4. Cluster_1/Master/modoverrides.lua — even if empty, this file should exist

Without cluster_token.txt, the server starts but will not appear in the public server browser. Without cluster.ini, the server will not start at all.

Verifying the Install

After first boot, watch the console output for these lines to confirm a successful start:

[00:00:02]: Connecting to Klei...
[00:00:05]: Connected
[00:00:05]: Sim Paused

If you see Failed to authenticate with cluster token, your token file is malformed or expired. Refer to the Klei server token guide.

Back to Knowledgebase
Need help? Submit a Ticket →