The crash message in your console tells you that your server crashed, not why. The real cause is almost always in the console lines printed just before it. Not sure where to start? Server Won’t Start or Keeps Crashing? walks through the checks in order.
A typical crash message looks like this:
[WinterNode] Server marked as OFF
[WinterNode] ---------- Detected server process in a crashed state! ----------
[WinterNode] Exit code: 1
[WinterNode] Out of Memory: falseQuick Fix: Read the Lines Above the Crash Message
- Log in to the Game Control Panel
- Select your server
- In the sidebar, click Console
- Scroll up from the Detected server process in a crashed state! line
- Find the last lines that mention
Error,Exception,Caused by, orFatal - Fix what that error names (a mod, a setting, a version)
- Click Start
Your server should now start and stay Online. If it crashes again with the same error, the fix didn’t take. If the error changed, repeat these steps for the new one.
What the Crash Message Lines Mean
- Exit code: the number the server program returned when it stopped. See the table below.
- Out of Memory: if
true, the server ran out of its RAM allocation. Go to Out of Memory (OOM) Crashes. Iffalse, look for a different error in the console first. aborting_reboot_crash_loop(shown as Aborting automatic reboot due to crash within the last 60 seconds): the server crashed again within a minute of its last crash, so the panel stopped restarting it. Fix the error in the console, then click Start.- Crash logs uploaded: some crashes print a link to the uploaded log. Copy it. Support can read it directly.
[MC-WRAPPER] Server exited with code 1: the same exit code, reported by the Minecraft launcher. It means the same thing asExit code: 1.
Common Exit Codes
Exit codes are general. The same code can come from many different problems, so use this table to narrow your search, not to diagnose.
| Exit code | What it means | Where to look next |
|---|---|---|
| 0 | The program closed itself normally | Something asked it to stop (a stop command, a schedule, or the game shutting down on its own). Check the console for why. |
| 1 | General error. The program hit an error and quit | The error lines just above the crash message |
| 133 | Stopped by a trap signal (signal 5) | A crash inside the game server program. Check the lines before the crash message, and recent game updates or mods |
| 137 | Force-killed (signal 9), usually for running out of RAM | Out of Memory (OOM) Crashes |
| 139 | Invalid memory access (signal 11, a segmentation fault) | A crash inside the game or Java itself. The console usually prints a crash report with the details |
Codes above 128 follow a standard pattern: the code minus 128 is the signal number that stopped the process. For example, 137 minus 128 is 9.
Common Causes by Error Type
Wrong Java Version (Minecraft)
If your Minecraft server crashes with exit code 1 right after you changed the Minecraft version or mod loader, check the Java version first. Look for UnsupportedClassVersionError or class file version in the console. See Changing the Java Version.
Out of Memory
If the crash message shows Out of Memory: true or exit code 137, the server used all its RAM. Check the Memory graph below the console. See Out of Memory (OOM) Crashes.
A Mod or Plugin
If the error lines name a mod, plugin, or a Java package from one, that add-on is the likely cause. Update or remove it. If you can’t tell which one, see Find Which Mod or Plugin Is Causing Problems.
Game-Specific Crashes
Some games have their own crash guides. For an example, see Troubleshooting Crashes on Your Windrose Server.
Still Not Working?
If you can’t find the error or the fix doesn’t work, contact our support team with:
- Your Server UUID
- The last 50 lines of console output before the crash message. Click Upload logs beside the console for a shareable link, or send the Crash logs uploaded link if one appeared
- The full crash message, including the exit code and the Out of Memory line
- What you changed before the crashes started (version, mods, settings) and roughly when they started
Frequently Asked Questions
The server program stopped because of an error. Code 1 is a general error code, so it doesn't say which error. The cause is in the console lines printed just before the crash message.
It means the crash was not recorded as an out-of-memory kill, so look at the console error first. If it says true, follow the Out of Memory (OOM) Crashes article.
137 means the process was force-killed (signal 9). On a game server this is usually because it ran out of its RAM allocation. See the Out of Memory (OOM) Crashes article.
133 means the program stopped on a trap signal (signal 5). It points to a crash inside the game server program itself. The console lines before the crash message usually show where it happened.