Skip to content
Back to the knowledge base

Server won't start

Find the cause in the console and fix the most common problems that stop a server right after it starts.

When a server won't start or stops shortly after starting, the cause is almost always written in the console. This guide shows how to read it and covers the most common cases.

Find the cause

The client panel is available in Polish only, so this article gives its labels in Polish with a translation the first time they appear.

  1. Open the console

    In the client panel, open your server, go to the Konsola (Console) tab and click Uruchom (Start).

  2. Read the last lines before the crash

    When the server stops, the panel adds a block starting with Detected server process in a crashed state!. The cause is in the lines right above it, usually in a line with Error, Exception or FATAL.

  3. Check for a message in the panel

    For some errors, the panel shows a window describing the problem with a button that fixes it. Read it before you close it.

The panel's block also tells you how the server ended:

LineWhat it means
Exit code: 1The server ended with an error. The cause is higher up in the console.
Out of memory: trueThe server ran out of RAM.
Aborting automatic restart, last crash occurred less than 60 seconds ago.The panel tried to start the server again once and stopped because the crash repeated. Fix the cause and start the server yourself.

Most common causes

A licence that wasn't accepted

Some games require you to accept a licence on the first start. The panel then shows a window with the licence. Accept it and start the server again.

Changed startup parameters

If the server stopped working after a change in the Parametry startowe (Startup parameters) tab, restore the previous value. A common mistake is the name of a file that isn't on the server, or an environment version that doesn't match the game version. See Startup parameters for more.

Missing or damaged server files

When the console shows an error about a missing or damaged startup file, reinstall the server. A reinstall downloads the startup files again and keeps your data.

Not enough RAM

When the panel shows Out of memory: true or the Pamięć RAM (RAM) bar in the Przegląd (Overview) tab reaches the end, the server needs more memory. Turn off some plugins or mods, or move to a bigger plan with Zmień pakiet (Change plan) in the Przegląd tab.

A full disk

When the Dysk (Disk) bar in the Przegląd tab is full, the server can't save files. Delete files you don't need in the Pliki (Files) tab, such as old logs, world copies or archives.

A recent change to the files

If the server stopped working after you added a plugin or mod or changed the configuration, undo that change: remove the new file or restore the previous version. If you don't know what changed, restore a backup from before the problem.

Common problems

You don't know what the error in the console means

Write to us through the contact form. Paste the last lines from the console, from the line with the error to Aborting automatic restart, and tell us what changed on the server before the crash.