Don’t Starve Together Server Troubleshooting Guide

If your Don’t Starve Together (DST) dedicated server won’t start, keeps crashing, or won’t show up in the server list, this guide covers the most common causes and their fixes. You’ll learn how to diagnose connection issues, mod conflicts, world generation errors, and performance problems, with step-by-step solutions you can apply right away.

Before You Start: Check the Logs

Every DST server writes log files that tell you exactly what went wrong. The two most important files are log.txt and server_log.txt, located in the Documents/Klei/DoNotStarveTogether/ folder (on Windows) or ~/.klei/DoNotStarveTogether/ (on Linux). Open the most recent log.txt and look for lines starting with ERROR, WARNING, or FATAL. The error message usually points to the root cause—missing files, invalid mods, or port issues. If you’re unsure what a line means, copy it into a search engine; the DST community has likely seen it before.

Server Won’t Start: Common Causes and Fixes

1. Missing or corrupt world files – If you moved a world from a client to a server, the save folder might be incomplete. Delete the save folder in your server’s cluster directory and let it regenerate a fresh world.
2. Invalid cluster settings – A typo in cluster.ini (e.g., a wrong value for max_players or game_mode) can prevent startup. Validate your settings against a known-good example from the Klei forums.
3. Port already in use – Another process (or another DST server) may be using the same UDP ports. On Windows, run netstat -a -o to see which process holds the port; on Linux, use ss -ulpn. Change the ports in cluster.ini if needed.
4. Outdated server version – If your client is newer than the server, the server may refuse to start. Use the Steam client to update the dedicated server tool, or run steamcmd +app_update 343050 validate on Linux.

Server Crashes During Play: Memory and Mods

Random crashes mid-game are often caused by mods that conflict or leak memory. Disable all mods first by setting enabled_mods to empty in modoverrides.lua. If the server runs stable, re-enable mods one at a time. Also check the server_log.txt for a LUA_ERROR that names a specific mod. Another common culprit is the server running out of RAM—DST servers can use 2–4 GB with many players and mods. Monitor memory usage and consider reducing the number of players or disabling heavy mods like character mods with custom animations.

Players Can’t Connect: Port Forwarding and Firewall

If your server starts but friends can’t join, the issue is almost always network configuration. DST uses UDP ports 10999 (default) and 10998 (Steam). You must forward these ports on your router to the server’s local IP. Also add exceptions in your firewall (Windows Defender Firewall or iptables on Linux) for both UDP ports. After changing firewall rules, restart the server. To test if the port is open, use an online port checker while the server is running. If you’re on a college or office network, port forwarding may be blocked entirely—consider using a hosting service instead.

Server Not Showing in the Server List

Sometimes the server runs fine but doesn’t appear in the in-game browser. This happens when the server can’t reach the Klei master server. Check that your server can make outbound connections on port 80/443 (HTTP/HTTPS). If you’re behind a strict NAT, set offline_server = true in cluster.ini and share your IP directly—players can connect via the “Join by IPâ€� option. Also ensure your server’s clock is synchronized; a large time skew can cause authentication failures.

Performance and Lag: Tuning Your Server

Even on good hardware, DST servers can lag if the world is huge or many players are active. The most effective fixes are:

• Reduce max_players to 4–6 if you have fewer players.
• Set tick_rate in cluster.ini to 15 (default is 30) to halve CPU usage, but note this increases input lag slightly.
• Disable unused mods that run periodic checks.
• Set autosave_interval to a higher value (e.g., 8) to reduce disk I/O spikes.
• Use a dedicated machine or a VPS with at least 2 CPU cores and 4 GB RAM.

If lag persists, check the server’s CPU usage—if it’s pegged at 100%, the world may be too large for your hardware. Consider starting a new world with a smaller map size.

Mod-Specific Issues: Blacklists and Updates

Mods are a frequent source of trouble. If a mod update breaks your server, you can pin a specific version by editing modoverrides.lua to include the workshop ID and version number. Also, some mods are server-only and some are client-only; installing a client mod on the server can cause errors. Always check the mod’s workshop page for the correct installation instructions. If a mod causes a crash that prevents startup, you can temporarily disable it by renaming the modoverrides.lua file and starting the server without it.

Frequently Asked Questions

Why does my server say “Invalid Password� when I try to connect?

This usually means the password in cluster.ini has a typo, or the server is still loading. Wait for the “Sim Pausedâ€� message in the console. If it persists, reset the password to a simple one and try again.

Can I run a DST server on a home PC while playing on the same machine?

Yes, but it will use extra CPU and RAM. For 2–4 players, it’s fine on a modern PC. For more players, use a separate machine or VPS to avoid lag.

How do I update my dedicated server on Windows?

Open Steam, go to Library, filter by “Tools,â€� find “Don’t Starve Together Dedicated Server,â€� and click Update. If it doesn’t update automatically, right-click and select “Propertiesâ€� then “Updatesâ€� to force it.

Why do my players get disconnected every few minutes?

This is often a network issue—packet loss or a router that drops UDP connections. Try lowering the timeout value in cluster.ini to 30 seconds, but if the problem persists, check your router’s QoS settings or switch to a wired connection.

My server ran fine yesterday, but today it won’t start. What changed?

Check if a mod updated automatically. Also verify that the save folder isn’t corrupted—rename it to save_backup and try starting with a fresh world. If that works, your old world may be unrecoverable.

Is there a way to see who is connected to my server?

Yes, in the server console type c_listallplayers() or c_listplayers(). This works only if you have console access (i.e., you started the server with the console window open).

Related

• Python AI Agent Tracing: Build a Parent-Child Timeline
• Older Flagship vs Newer Midrange Chip: Which to Choose?
• Word AI Summarize: What It Does and How to Use It