All

Server exited with code 1

Exit code 1 is Java's generic 'unhandled exception terminated the process'. It is not a specific error — dozens of different failures exit with 1. The diagnosis is never the code; it is the first Exception line printed above the exit message. Treat the exit code as a pointer, then read upward.

Fastest path: paste your crash report into the Crash Doctor — it identifies this pattern and 40+ others automatically. No signup.

How to fix it

  1. 1

    Find the first exception above the exit line

    Scroll up from 'exited with code 1' to the first 'Exception' or 'Error' line. That line — not the exit code — is your search term.

  2. 2

    Match it to a known signature

    UnsupportedClassVersionError, NoSuchMethodError, OutOfMemoryError, mixin failures and missing dependencies all exit with code 1. Each has a specific fix — check the related guides below.

  3. 3

    Check crash-reports/

    A folder beside the server jar holds full crash reports with timestamps. The newest file often contains the complete trace the console truncated.

  4. 4

    Verify the boring causes

    Java version for the pack, EULA accepted, mods folder matching the loader, configs parseable. Four checks catch the majority of exit-code-1 boots.

  5. 5

    Paste the log into Crash Doctor

    The free tool reads the whole log and names the pattern with a fix — faster than searching exception text by hand.

Alternative causes

These can produce the same error message — worth ruling out if the steps above don't resolve it.

A wrapper script masking the real output

Some startup scripts swallow the JVM's output and show only the exit code. Run the same command manually once to see what was hidden.

Frequently asked

Is exit code 1 always the same problem?

No — it is every problem except the ones with their own signal (like 137 for SIGKILL). The log, not the code, carries the diagnosis.

Why does the panel only show the code?

The exit code is the process result; the log is the process output. Panels show both — expand the console view around the crash timestamp.

Can I restart through exit code 1?

Restarting is safe but pointless until the cause changes — the same exception exits with 1 again. Fix one thing, then restart.

Want this auto-fixed on your server?

CoalHosting's Minecraft hosting runs the same pattern database against every crash and applies the known fix before your players notice. Free crash diagnosis works on any server, hosted or not.

Run Crash Doctor on your report →Get a server with auto-fix

Related crashes

java.lang.UnsupportedClassVersionError

Fix the Minecraft server UnsupportedClassVersionError crash — the Java runtime is newer or older than the mod …

Missing mod dependency (mod requires X which is not present)

Fix Minecraft 'mod requires X which is not present' errors — the loader found a mod but its required companion…

Server exited with code 137 (SIGKILL / OOM)

Exit code 137 means the OS killed the Java process — almost always host-level out-of-memory pressure, not a Mi…

Last reviewed 2026-09-06. If a step is wrong or out of date, tell us — we'll fix the article and the auto-pattern at the same time.