How to Fix Minecraft Exit Code 1, 137, & 143
Understand exactly why your Minecraft server stopped running. Step-by-step diagnostic workflows to cure mod conflicts, Java runtime mismatches, and memory crashes.
1. What Are Container Exit Codes?
When a Docker container terminates, the Linux kernel passes an exit status code back to Pterodactyl Wings. This single numeric value tells you whether the shutdown was an intentional user action, an unhandled Java exception, or a hard kernel kill.
2. Exit Code 1: Mod & Startup Configuration Errors
What it means: The Java virtual machine booted, encountered an unrecoverable exception, and terminated intentionally.
Top 3 Causes & Solutions:
- Unaccepted EULA: The console says
You need to agree to the EULA in order to run the server. Openeula.txtand seteula=true. - Incompatible Java Version: Running Minecraft 1.21 on Java 17 results in
has been compiled by a more recent version of the Java Runtime. Change your Docker Image toJava 21in the Startup tab. - Corrupted Mod or Duplicate Jar: Check
logs/latest.logorcrash-reports/. Remove any duplicate or mismatched mod jars frommods/.
3. Exit Code 137: Out of Memory (OOM Killer)
What it means: Exit Code 137 indicates the container was terminated by signal SIGKILL (128 + 9) issued by the Linux Out-of-Memory (OOM) killer. Your server requested more RAM than your plan’s physical allocation limit.
Diagnosis & Immediate Fix
Look in your server console log. If the server suddenly halts without writing a crash report, it was OOM killed.
- Lower Simulation Distance: In
server.properties, setsimulation-distance=4. - Remove Memory-Heavy Plugins: Heavy plugins like Dynmap (full rendering) can consume 4GB+ RAM.
- Upgrade Server RAM: If hosting 30+ players or heavy modpacks, upgrade your plan via the Client Portal under Actions → Upgrade/Downgrade.
4. Exit Code 143: Graceful SIGTERM vs Timeout
What it means: Exit code 143 corresponds to signal SIGTERM (128 + 15). This happens when:
- You clicked the red Stop button in the panel.
- A scheduled restart cron job sent a graceful shutdown command.
- The server froze during world save, exceeding Pterodactyl’s 60-second stop timeout.
5. Fast 5-Step Crash Resolution Checklist
- Open
logs/latest.logand scroll to the bottom 50 lines. - Check for unaccepted EULA (
eula=false). - Verify your Java version in the Startup tab matches your Minecraft jar.
- Check if your RAM graph spiked to 100% right before the crash.
- If still stuck, take a screenshot of the log and open a ticket under Technical Support.