Server Will Not Start

Check the Console

Open the server panel and go to the Console tab. The error is usually the last thing in the output, and error lines are prefixed with [ERROR].

Check the badge in the console header first. "Live" means you are seeing output as it happens; "Reconnecting" means the stream dropped and what you are looking at may be incomplete. "Refresh" reloads the stored history.

Common causes: a config file edited into invalid syntax, a setting the game refuses, a corrupted save, a mod that needs a loader that is not installed, or a mod that does not match the game build after an update.

Note the exact error text — you will need it for support if you cannot fix it yourself.

Recent Changes

Did you recently edit a config file? A single typo will stop most games from starting. Open the file again in the File Manager and undo the change.

Did you install a mod? Remove it from the Mods tab and try starting again. If the game needs a mod loader, check the loader panel above the Installed and Browse tabs — a mod installed with no loader present does nothing, and a loader installed after the mods still needs a restart.

Did a game update land? A mod built for the previous build is the most common reason a server that worked yesterday does not start today. The build you are on is on the Admin tab.

Did you change a setting? Open the Settings tab and use the search box to find it. The panel refuses a value the game’s schema rejects, so a saved value is at least in range — but a legal value can still be wrong for your world.

Corrupted Save

If the console shows a save file error, the world save may be corrupt.

Go to the Backups tab and restore the most recent backup whose state is "verified". Every server is backed up daily, so there is usually one from before the problem.

If no backup works, delete the world folder itself in the File Manager with the server stopped, and start the server again to generate a fresh one. That is destructive — take a manual backup of the broken world first so support can still look at it.

Check & Repair Files

If the console fails before the game reaches its own configuration — a missing executable, a missing library, a start-up check the game itself refuses — press "Check & Repair" on the Admin tab. It is not a corruption scan: there is no per-file checksum for these games. What it establishes is whether your server is correctly assembled — that every game file it should be linking is present, that they all come from one build, that the install finished, that the game’s own start-up check passes, that the server program is reachable, and that your assigned port is in the file the game reads it from.

It repairs two of those itself: missing game files are put back from the host’s copy, and a wrong port is rewritten. Each check comes back as its own line with the host’s own wording, so you can see what was actually established rather than a single verdict.

If Check & Repair reports everything in order and the server still will not start, the problem is your world, your configuration or a mod — not the game files. Work back through the sections above.

If it reports a problem it could not repair, or reports that it could not establish anything, open a support ticket with your Service ID, the check list it printed and the console output.

"Reinstall Server Files" on the Overview tab is the stronger version of the same idea: it replaces every game file with the host’s own copy while leaving your world, settings and mods alone. It needs the server stopped, and it does not re-download anything from the publisher — for a build that is itself broken, the Game Updates card re-stages the server onto a build, which is the practical fix when a partial or interrupted update is the cause.