DST Cluster Token Guide & Checker
A missing or invalid cluster token is the single most common reason a new DST server refuses to start. This guide walks you through generating, placing, and validating your token — and what to do when it expires.
What is the Cluster Token?
The cluster token is a credential that ties your dedicated server to your Klei account. Without it, the server cannot authenticate with Klei's backend and will silently fail to come online — no error in the main console, just an absent server listing. Every cluster directory needs exactly one cluster_token.txt file at its root.
How to Get Your Token
Open the Klei Account Portal
Go to accounts.klei.com/account/game/servers and sign in with the Klei account linked to your DST purchase.
Add a New Server
Click Add New Server, give it a name (any name — this is just for your reference in the portal), and click Add.
Copy the Token
The portal generates a token string starting with pds-g^. Copy the entire string — it is long (100+ characters).
Create cluster_token.txt
Paste the token as the sole content of a file named cluster_token.txt and place it in your cluster root — the same directory as cluster.ini.
~/.klei/DoNotStarveTogether/MyCluster/cluster_token.txt
# File contents (no quotes, no trailing newline):
pds-g^KU_XXXXXXXXXXXX^XXXXXXXXXXXXXXXXXX...
Token Format Validator
Paste your token below to verify it looks correct. Nothing is sent anywhere — all validation runs in your browser.
Token Expiry
DST cluster tokens expire after approximately 14 days of inactivity. If your server was offline for two weeks and refuses to start again, a stale token is the first thing to check.
Regenerate the token at accounts.klei.com, update cluster_token.txt, and restart both server processes.
Alternative: In-Game Console
If you have DST installed locally, you can generate the token in-game without visiting the portal:
TheNet:GenerateClusterToken()
The token is written to Documents/Klei/DoNotStarveTogether/cluster_token.txt on your local machine. Copy it to your server.
Security Checklist
- Never commit cluster_token.txt to a git repository.
- Add cluster_token.txt to your .gitignore.
- Use a separate token per cluster — don't reuse one token across multiple servers.
- Revoke and regenerate immediately if the token is exposed publicly.
- Restrict read access to cluster_token.txt on your server (chmod 600 on Linux).
- Check for token expiry if the server was offline for more than two weeks.
Run your own Don't Starve Together server.
Rent a private Don't Starve Together server on real hardware — full control-panel access, your mods, your configs, your rules. It's your server; run it your way.
Don't want to run it yourself? Our managed services & consulting team will set it up and keep it running for you — game servers, Windows, Linux, and cloud, from 10+ years of MSP work.