☰

Server Exited with Code 0

Your panel reports the process exited with code 0. Unlike code 1, code 0 means the server shut down cleanly, on purpose. The puzzle is usually why it stopped, not a crash, since nothing actually errored.

What does this error mean?
Exit code 0 is the success code: the JVM ended normally. If the panel treats that as a crash, the server was told to stop (a /stop, a script that finished, or an immediate shutdown) rather than failing. 
Process exited with code 0
Most Common Causes
  • Someone ran the /stop command or stopped it from the panel.
  • The start script ran once and ended instead of staying attached.
  • The server started and immediately stopped (e.g. a one-shot command).
  • A scheduled restart task triggered.
  • The console received an end-of-input/EOF and treated it as 'stop'.
How To Diagnose
  1. Check the log end for a 'Stopping server' / 'Saving worlds' message (clean stop).
  2. Confirm whether anyone issued /stop or a panel stop.
  3. Inspect your start script, it should keep the server running, not exit after launch.
  4. Look for a scheduler/cron restarting or stopping it.
Recommended Fixes
  • Check who stopped it
    A clean stop usually came from /stop, the panel, or a scheduled task, not a bug.
  • Fix the start script
    Ensure the script launches the server in the foreground and does not exit immediately.
  • Keep the console attached
    Avoid sending EOF/closing the terminal, which the server reads as a stop.
  • Review scheduled tasks
    Disable or adjust any auto-stop/restart job firing unexpectedly.
Analyze My Log
Frequently Asked Questions

No, it is a clean exit. The server stopped on purpose rather than failing.

Panels flag any exit as a stop. With code 0 the server was simply told to shut down.

Use a start script/loop that relaunches on stop only if intended, and avoid closing the console.