"Detected server process in a crashed state" / won't turn on — how do I fix it?

The message "Detected server process in a crashed state" simply means the server exited unexpectedly. It's a status, not the cause — the real reason is in the Console, just above that line.

What it means

The panel noticed the server process stopped when it shouldn't have. To find out why, you need to look at what happened right before it crashed.

How to fix it

1. Open the Console and scroll up to the real error before the crash line.
2. Address that error — common causes are the wrong Java version, a bad mod or plugin, a corrupted world, or running out of RAM.
3. Press Start again and watch it boot.

If it crashes instantly every time

If there's no clear log and it dies immediately on every attempt, check the Startup RAM variables — an Xms above Xmx crashes the server instantly. Then use "Share logs via mclo.gs" and open a ticket so we can help.

Tip: The crashed-state line is never the whole story. Always scroll up to the error that came before it — that's what tells you what to fix.

Frequently asked questions

Why does it crash instantly with no log? That pattern usually points to the RAM variables — Xms set above Xmx crashes immediately. Fix that in the Startup tab.

Where do I find the underlying error? In the Console, just above the "crashed state" message. Share it via mclo.gs if you'd like us to read it with you.