Server won't start: find and fix the cause

Your game server won't start or stops right away? How to find the cause in console and logs — the most common errors and how to fix them.

Last updated July 20, 2026 · RespawnHost

On this page

If your server won’t start, the cause is almost always visible in the console: open the Console tab in the panel and read the last lines before the crash — that’s where the server logs why it shut down. The most common causes are insufficient RAM, broken mods/plugins, or a faulty configuration file.

Where do I see why the server won’t start?

  1. Open the console — the connection runs automatically via WebSocket and shows the server’s live output.
  2. Start the server and watch the output: the decisive error message is usually in the last 10–20 lines before the server stops again.
  3. Older logs are in the file manager in the logs/ folder — the console only shows the current session.

Tip

Search the log output for keywords like ERROR, Exception, FATAL or OutOfMemory — they almost always mark the actual cause.

The most common causes

Not enough RAM (out of memory)

Messages like OutOfMemoryError or a crash right after world loading point to insufficient memory. This typically happens after installing mods/modpacks or with grown worlds. Solution: upgrade the RAM plan in the panel — RAM recommendations per game are in the respective game guides.

Broken or incompatible mods

If the server no longer starts after installing a mod, the log usually names the responsible mod during loading. Remove the most recently installed mod via the Marketplace (“Installed” tab) or the file manager (mods/ folder) and restart. More in the guide Mods not loading.

Faulty configuration file

A typo in a config (e.g. invalid JSON/XML/INI) makes many servers crash immediately. The log names the file and often even the line. Open the file in the file manager and fix the error — or restore a backup from before the change (Backups tab).

Corrupted world/save data

After a crash, the world file can be corrupted. Restore the world from a backup. As a rule, create a backup before major changes (updates, mod installations, wipes).

Warning

Never delete files "on suspicion" in the file manager when facing start problems. Read the log first, then act deliberately — and create a backup beforehand.

Still offline?

If the console shows no usable error message or you’re stuck: open a support ticket with the affected server name and the last log lines — we’ll look at the server directly.

Frequently asked questions

Why does my server stop again right after starting? The server crashes during initialization — the cause is in the console in the last lines before the stop. Most common triggers: too little RAM, a broken mod, or a faulty configuration file.

Does a server that won’t start still cost money? Costs only accrue while the server is running. A server in Offline status causes no running costs.

Where do I find older logs? In the file manager in your server’s logs/ folder. The console itself only shows logs of the current session.

Does restarting the server help? For one-off hangs, yes. But if the server reproducibly fails to come up, there’s a real cause — and you’ll only find it in the log.