Troubleshooting
The most common problems on a Terraria server, and how to fix them. In every case, the panel Console is your first tool: read the last lines shown before the shutdown or error.
The server does not start
The console shows a world selection menu
If the console shows the list of worlds (with options such as n for a new world) and waits for input, the server did not find the world set in serverconfig.txt and does not know which one to create.
- Check that the
world=line points to an existing.wldfile, with the exact name (including capital letters) - Or set
autocreate(1,2or3) so the server creates the world automatically
See Configure serverconfig.txt and Importing a world.
The server created a new world instead of yours
The file set in world= did not exist (typo, wrong folder, capital letters), and since autocreate is set, the server generated a new one. Your world is not lost: stop the server, fix the name in world= and restart.
Error reading serverconfig.txt
A malformed line (spaces around the =, stray character) can make a setting invalid. Compare with your last working copy. If a value is reset on every start, it is probably defined in the Startup tab: see Startup tab parameters.
The world no longer loads
After a hard shutdown, a world can be damaged. Restore a backup from the Backups tab, or use the .wld.bak copy: see Restoring a backup. A world saved by a newer version of the game cannot be loaded by an older server.
A TShock plugin blocks startup
A plugin written for another TShock version often causes an error while loading. Stop the server, remove the last plugin added from the ServerPlugins/ folder, then restart. See Installing TShock plugins.
Players who cannot connect
| Symptom | Likely cause | Solution |
|---|---|---|
| Timeout / unable to connect | Wrong IP or port, server still loading | Use the IP and port shown in the panel with Join via IP, wait until loading is finished |
| Version mismatch message (not using the same version) | Client and server on different versions | Update the game, or the server (see below) |
| Refused with a Journey (or classic) character | Character and world in different modes | Journey character for a Journey world, classic character otherwise |
| Password refused | password changed without a restart, or set in TShock | Restart; on TShock, also check tshock/config.json |
| Server full | maxplayers (or MaxSlots on TShock) reached | Raise the value, keeping your plan in mind |
| Disconnected while loading (tModLoader) | Missing mods or different versions | See tModLoader mods |
| Player kicked straight away (TShock) | Player banned, or login required | Check /ban list and the RequireLogin setting |
| Player on console or mobile | Versions not compatible with a PC server | Our servers are built for PC players |
Opening the port is handled by YorkHost. Do not change the port= line of serverconfig.txt (nor the port in tshock/config.json): the server must listen on the port assigned by the panel. See Are all ports open? and Unable to connect to the server.
Client version different from the server
The game and the server must be on the same version. After a Terraria update on Steam, players may be refused until the server is updated.
- Vanilla: update the server using what the panel offers, or ask our support team. Back up first.
- TShock: TShock has to release a version compatible with each Terraria update, which can take a little time. Until then, players cannot join with the very latest game version. Update TShock as soon as a compatible version is available, and check your plugins.
- tModLoader: the server and players must use the same tModLoader version (same Steam branch, stable or beta).
tModLoader mods
| Symptom | Solution |
|---|---|
| A mod does not load, the console reports a missing dependency | Install the requested mod and add it to enabled.json |
| A mod is present but not loaded | Check that its name is in enabled.json, with no typo |
| The server stops while loading mods | Remove the last mod added from enabled.json, restart, then check its version and dependencies |
| Players are refused after a mod update | Update the server's .tmod to the same version as the players' |
| Players cannot download mods when joining | Have them subscribe to the same mods on the Workshop and enable them before joining |
See tModLoader: mods and Calamity.
Not enough memory
If the server stops abruptly while loading mods, generating a large world or mid-game, without a clear error, or if the console mentions a lack of memory (Out of memory), your plan's RAM is probably maxed out.
- Watch RAM usage on the server's page in the panel
- Remove the least useful mods, especially big content or music mods
- Move to a higher plan: Hallowed (6 GB) for Calamity or Thorium, Zenith (8 GB) for large modpacks. You can upgrade at any time from your client area.
A vanilla or TShock server, on the other hand, runs very well in 2 GB: if RAM is maxed out without mods, contact support.
Lag and desync
Terraria mostly uses a single core: the load of the world matters more than the number of players.
- Limit big farms and machines: automated mob farms, lots of wired statues, and water or lava constantly moving put a heavy load on the server. After big liquid works,
settlein the console settles the water. - Avoid piles of items on the ground: hundreds of dropped items weigh on the server.
- Trim the mod list on a tModLoader server.
- Restart the server regularly, for example every night, with an automatic restart from the Schedules tab.
- Check the player's connection: if only one player lags, the problem most likely comes from their connection.
To analyse resource usage, see also Performance debugging.
Still stuck?
Contact support 7 days a week on Discord or through your client area, including:
- your server's name and its mode (vanilla, tModLoader or TShock)
- what you changed just before the problem
- the last lines of the console at the time of the error