Unturned Dedicated Server Troubleshooting

Unturned Dedicated Server Troubleshooting

Server Not Appearing in Server Browser

Symptom: Server runs without errors but is not found in the Unturned server browser.

Checklist:

• Confirm Login_Token in Commands.dat is set to a valid GSLT from https://steamcommunity.com/dev/managegameservers.
• Verify ports 27015 and 27016 (UDP) are open through your firewall and router.
• Wait 2–5 minutes after startup — Steam registration takes time.
• Try searching for the server by direct IP in the Unturned client (Play → Connect).
• Confirm the server is using the correct AppID 1110390 (not 304930) — mismatched installs sometimes fail Steam registration.

GSLT Error: "Game server login token was rejected"

• The GSLT may be associated with the wrong game. Generate a new token at Steam's game server page with App ID 304930.
• GSLTs expire if a server hasn't connected to Steam in 30 days. Regenerate the token if necessary.
• One GSLT can only be used by one server at a time. If you copied a token from another server, generate a new one.

Workshop Mods Fail to Download

Symptom: Server starts but mods or maps listed in WorkshopDownloadConfig.json are missing.

• Check that the Workshop item IDs in File_IDs are correct integers (not quoted strings).
• Verify the items are publicly available on Steam Workshop — private or deleted items cannot be downloaded.
• Check server logs for Steam API error messages.
• Delete the Workshop/ cache folder and restart:

  rm -rf Servers/<ServerName>/Workshop/
  

• Increase Max_Query_Retries to 5 for unstable connections.

Server Crashes on Map Load

Symptom: Server starts, begins loading the map, then crashes.

• Verify the Map value in Commands.dat exactly matches the map's internal name (case-sensitive).
• If using a curated/Workshop map, confirm its Workshop ID is in WorkshopDownloadConfig.json and was successfully downloaded.
• Check available RAM — large maps (Russia, Washington) require 3–4 GB free RAM.
• Re-run app_update 1110390 validate in SteamCMD to repair corrupt server files.

Admin Commands Not Working

Symptom: Admin player types /kick or other commands but nothing happens.

• Confirm the admin's Steam64 ID is in Adminlist.dat OR they are listed as Owner in Commands.dat.
• Check that the Steam64 ID is correct — copy it exactly from steamid.io. A single wrong digit causes silent failure.
• Some commands (like /item, /god) require Cheats to be present in Commands.dat.

Players Cannot Connect / Connection Timeout

• Verify both port 27015 and 27016 (UDP) are open on the firewall and router.
• Check MaxPlayers in Commands.dat — if the server is full, players receive a timeout-style error.
• Confirm there is no IP ban for the player in Blacklist.dat.
• If Whitelisted is set in Commands.dat, the player must be in Whitelist.dat.

High CPU Usage / Server Lag

• Reduce MaxPlayers — more players means more zombie and loot entity simulation.
• Switch to a smaller or medium map: PEI and Yukon are lighter than Russia or Washington.
• Disable Workshop mods that add many entities or run expensive logic.
• Set up a daily restart via systemd timer to clear accumulated memory.

Commands.dat Changes Not Taking Effect

• Commands.dat is read only at server startup. Stop the server, edit the file, and restart.
• Adminlist.dat and Blacklist.dat changes also require a restart, except for runtime console commands (@admin, @ban, @permit) which take effect immediately.

Getting More Help

• Official Unturned documentation: docs.smartlydressedgames.com
• Steam Discussions: Unturned Dedicated Servers
• Check the server console output for startup errors — most issues are reported clearly in the startup log.