How to Fix “Dedicated Server Failed to Start” in Don’t Starve Together

If a Don’t Starve Together dedicated server will not start, open server_log.txt for both the Master and Caves shards first, then check whether antivirus or Windows Controlled Folder Access blocked the game. Those two checks are fast, reversible and match the main explanation in Klei’s support guidance. If security software is not responsible, verify cluster_token.txt, test with every mod disabled, and only then restore an older cluster backup.

Godlike.Host offers hosted Don't Starve Together servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.

The port values and console command in this guide come from community reports rather than a current, version-specific Klei manual. Confirm them against your own server.ini and game version. No reliable published data shows how often any individual cause occurs.

#	Preview	Product	Price
1		Don't Starve Together Standard - Nintendo Switch [Digital Code]	$14.99	Buy on Amazon
2		Don't Starve Together. MACRO-RAP	$1.29	Buy on Amazon
3		Title Theme "from Don't Starve Together" (Lo-Fi Remix)	$1.29	Buy on Amazon
4		Title Theme "from Don't Starve Together" (Lo-Fi Remix)	$1.29	Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

Start with the log, not a guess

A failed launch can be caused by a blocked executable, an invalid token, a mod, a shard configuration problem or a damaged save. The useful evidence is normally in the shard logs, not in the short message shown by the launcher or host panel.

Find the shard logs

1. Open the folder for your dedicated server cluster.
2. Open the Master shard folder and read server_log.txt.
3. Open the Caves shard folder and read its separate server_log.txt.
4. Look at the final lines written immediately before the process exits. Record which shard stopped first and any wording about access, a token, a workshop item, a port or a save.

Community documentation identifies server_log.txt as a per-shard file. On Windows, crash-related files have also been reported under DocumentsKleiDoNotStarveTogether. A log that ends before the world is created often points to a startup or permission problem; a log that reaches world loading and then stops gives you a narrower place to investigate.

#1 Best Overall

Don't Starve Together Standard - Nintendo Switch [Digital Code]

• Cooperate with your friends in a private game, or take your chances with strangers online. Work with other players to survive the harsh environment, or strike out on your own. Do whatever it takes, but most importantly, Don't Starve.

$14.99

Buy on Amazon

1. Remove antivirus and Windows folder-protection blocks

Klei’s support article for the “Dedicated Server Failed To Start” message describes the usual meaning as something on the computer preventing the game from completing startup. Its recommended direction is to allow the Don’t Starve Together executables in the game’s bin and bin64 folders. Community reports also describe Windows Defender stopping server creation until the process was excluded. Treat an exclusion as a targeted troubleshooting test, not a reason to turn protection off globally.

Allow the game files in antivirus software

1. Open the security product that reports the block and review its quarantine, protection-history or blocked-app list.
2. Add the Don’t Starve Together executable files located in the installation’s bin and bin64 directories to its allowed list. Klei’s guidance refers to four executables in those folders; use the files actually present in your installation rather than copying names from an unrelated game version.
3. Apply the change, close the server and start it again.
4. Check both shard logs after the restart. If the server now reaches world creation, the security block was the immediate cause.

Check Controlled Folder Access on Windows

Windows Ransomware Protection, specifically Controlled Folder Access, can stop a game process from writing its cluster or log files. Klei’s guidance calls out dontstarve_steam.exe when this feature is responsible.

1. Open Windows Security.
2. Choose Virus & threat protection, then Manage ransomware protection.
3. Open Allow an app through Controlled folder access.
4. Add the Don’t Starve Together dontstarve_steam.exe file, then retry the server.

Windows labels can vary slightly by release. If your security software offers a temporary audit or “allow once” action, use that first. Do not disable ransomware protection permanently simply because the server starts once; keep the exception limited to the genuine game executable and remove it if the log shows a different cause.

2. Check the cluster token and shard folders

A dedicated cluster needs a Klei authentication token. Third-party hosting guidance and community discussions report startup failures when the token is stale, missing, malformed or stored in the wrong directory. They also mention a shard that did not start and a conflicting Workshop mod as related failure conditions. These are community reports, not a current Klei guarantee, so use the log to confirm that a token is the issue.

Rank #2

Don't Starve Together. MACRO-RAP

$1.29

Buy on Amazon

Verify cluster_token.txt

1. Open the cluster’s Cluster_1 folder (or the numbered cluster folder you selected).
2. Confirm that a file named exactly cluster_token.txt is present there. Windows must not have silently added a second .txt extension.
3. Open the file in a plain-text editor. It should contain one token string, on one line, with no explanatory text, extra tokens or copied quotation marks.
4. Save it as plain text, close the editor and start the server again.

Do not paste the token into a shard-specific folder unless your server manager explicitly uses a different layout. The community guidance cited for this error places it in the cluster folder, alongside the shard directories.

Generate a replacement token in game

Community instructions provide this recovery path when the file is missing. It is not a version-confirmed official procedure, so follow the syntax exactly and check the resulting file before launching the dedicated server.

1. Start Don’t Starve Together and log in with the account that owns the server.
2. Open the in-game console with the backtick (`) key. On keyboards where that key is difficult to reach, use the key assigned to the console in your game settings.
3. Run TheNet:GenerateServerToken().
4. Exit the game cleanly and inspect the cluster folder for the newly created token file.
5. Ensure the file contains a single token string, then launch the dedicated server.

If the command does not create a usable file, do not keep generating tokens blindly. Return to server_log.txt, confirm that you are editing the cluster actually passed to the server launch command, and check whether your host panel stores credentials in a separate configuration area.

3. Test the server with all mods disabled

Mods can fail before the world finishes loading, especially after a game update or when a Workshop item has an invalid setting. Community troubleshooting treats disabling every mod as the standard diagnostic test. A Workshop discussion also reports a translation mod preventing startup until its language setting was changed; that is a single low-confidence anecdote, not a general rule about translation mods.

Rank #3

Title Theme "from Don't Starve Together" (Lo-Fi Remix)

$1.29

Buy on Amazon

Use a clean diagnostic launch

1. Back up the cluster configuration and save before changing anything.
2. Disable all server and world mods in the configuration or host panel. Do not merely unsubscribe from one item while leaving its configuration enabled.
3. Start the server with the same cluster and shard settings.
4. Read both shard logs. If the server starts without mods, stop it before making other changes.
5. Re-enable one mod, start the server and record the result. Repeat until the failing item is identified.

Re-enabling one item at a time matters because several mods can produce the same generic startup message. When a particular mod fails, check its Workshop page for an updated version and inspect its own settings. For a translation mod, verify that the selected language is valid for the installed release before concluding that the mod itself is unusable.

Interpret a successful no-mod launch

A clean launch proves only that the disabled set contains the conflict; it does not identify whether the problem is one mod, an interaction between two mods or a stale configuration value. Keep the working no-mod copy until the final culprit is known, and make changes to a duplicate configuration rather than your only copy.

4. Confirm the Master and Caves port assignments

Each shard on one machine needs its own server port. A community guide gives server_port = 10999 for the Master shard and server_port = 11000 for Caves. These are community defaults, not guaranteed values for every release or hosting environment. Read the active server.ini files and confirm that the ports are free and reachable through your firewall and host panel.

One community guide places a label for cluster_key next to port 10999; that appears to be a documentation error. Do not copy that label as a setting. Use the parameter names in your own configuration file.

Rank #4

Title Theme "from Don't Starve Together" (Lo-Fi Remix)

$1.29

Buy on Amazon

Diagnose a port collision

• If one shard starts and the other exits immediately, compare their server_port values first.
• If two separate clusters run on the same machine, give each server distinct authentication and master-server ports as well as distinct shard ports.
• If the log reports that a port is already in use, stop the other server process or assign an unused port, then update the corresponding firewall and host-panel rules.
• If the log contains no port error, do not change several ports at once; preserve a known-good value while testing tokens and mods.

5. Recover from a damaged cluster save

Community reports describe a damaged cluster file preventing startup and say that restoring an older backup, sometimes about a day old, allowed the server to launch. This is anecdotal and can discard progress, so it belongs after permissions, token, mod and port checks.

Make a safe rollback

1. Stop every Master and Caves process.
2. Copy the entire current cluster folder to a separate location and label it with the date. Keep this copy even if you suspect corruption.
3. Locate the newest backup that predates the first failed launch. If your host creates automatic backups, use its restore function; otherwise copy the selected backup into a separate working directory first.
4. Restore the backup as a new test cluster or replace the live cluster only after confirming the backup is complete.
5. Start with mods disabled and check both shard logs.

Do not overwrite your only save while experimenting. A rollback can fix a damaged file, but it cannot repair a missing token or an executable blocked by security software; those conditions still need to be addressed if the restored cluster fails.

Use the failure pattern to choose the next test

What not to do while troubleshooting

• Do not delete the cluster before making a complete backup.
• Do not paste multiple lines or comments into cluster_token.txt.
• Do not change token, mod, save and port settings simultaneously; you will lose the ability to identify the cause.
• Do not assume a port number is universal. The values above are community defaults and must be checked against your edition, host and other servers.
• Do not treat a single forum report as proof that every translation mod, antivirus product or backup is defective.

When to escalate to a host or Klei support

Contact the server host or Klei support after you have preserved the logs and can provide the exact cluster layout, game build, shard that exits, security-history result, mod state and the final log lines. State whether a no-mod launch works and whether an older backup changes the result. This information distinguishes a hosting-layer port or permission problem from a cluster-specific failure and avoids repeatedly resetting a working configuration.

The available official guidance for this message focuses on software blocking the game and allowing the relevant executables. The token, mod, port and save procedures above are community-derived and may need adjustment as Don’t Starve Together changes. Verify any version-specific instruction in the current game files and your host’s documentation before applying it to a production world.

Quick Recap

Bestseller No. 1

Don't Starve Together Standard - Nintendo Switch [Digital Code]

$14.99

Bestseller No. 2

Don't Starve Together. MACRO-RAP

$1.29

Bestseller No. 3

Title Theme "from Don't Starve Together" (Lo-Fi Remix)

$1.29

Bestseller No. 4

Title Theme "from Don't Starve Together" (Lo-Fi Remix)

$1.29

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.