Minecraft Server Crashes on Startup, Full Fix Guide

Reading the Crash Log

When your Minecraft server crashes on startup, the most important thing you can do is read the log. Open logs/latest.log and scroll to the bottom, the last 20-30 lines before the process exits contain the cause. If a crash report was generated, it will be in the crash-reports/ folder. A proper minecraft server crash on startup fix always starts with reading the error.

Look for lines containing ERROR, FATAL, Exception, or Could not. The Java stack trace points directly to the cause.

Cause 1: Java Version Mismatch

The most common startup crash is running the wrong Java version. If you see UnsupportedClassVersionError, your Java is too old. Minecraft 1.21+ requires Java 21. See our Java version errors guide for installation steps.

Cause 2: Plugin Crash

If the server started fine before you added or updated a plugin, the plugin is the culprit. The log will usually say something like:

[Server thread/ERROR]: Error occurred while enabling PluginName
java.lang.NullPointerException: ...

Fix:

1. Remove the plugin from plugins/ and restart.
2. If the server starts, the plugin is confirmed as the cause.
3. Check for an updated version or report the bug to the developer.
4. See plugin compatibility issues for deeper troubleshooting.

Cause 3: Corrupted World Data

If the crash occurs during world loading with NBT errors or region file errors, the world data is corrupted. The log may show:

net.minecraft.nbt.NbtFormatException: ...
java.io.IOException: Failed to read chunk ...

See our world corruption guide for repair steps. Quick test: rename the world folder and let the server create a fresh world. If it starts, the old world is the problem.

Cause 4: Port Already in Use

If another process is using port 25565, the server crashes with:

java.net.BindException: Address already in use

Find and stop the conflicting process:

sudo lsof -i :25565
# Kill the process or change the port in server.properties

Cause 5: Insufficient Memory

If the server crashes immediately with:

Error occurred during initialization of VM
Could not reserve enough space for object heap

Your -Xmx value exceeds available system RAM. Lower it or free up memory. Leave at least 1-2 GB for the operating system. If the crash happens after loading with OutOfMemoryError, see our OOM guide.

Cause 6: Missing EULA

The server will not proceed past startup if eula.txt contains eula=false. Open the file and change it to eula=true. This is not technically a crash but the server exits immediately, which looks like one.

Cause 7: Corrupted Server Jar

If the jar file is incomplete (bad download, disk error), you will see:

Error: Invalid or corrupt jarfile paper.jar

Re-download the jar from the official source (papermc.io for Paper). Verify the file size matches what is published.

Systematic Debugging Process

1. Read logs/latest.log, identify the specific error.
2. Check Java version: java -version.
3. Test with zero plugins: move plugins/ folder and restart.
4. Test with a fresh world: rename the world folder and restart.
5. Test with a fresh jar: download a new server jar.
6. Test with minimal flags: java -Xmx4G -jar paper.jar nogui.

Each step isolates one variable. If the server starts after any step, you have found the category of the problem. From there, narrow down to the specific file or plugin.

If the server starts but crashes later during gameplay, the cause is different, see Can't Keep Up troubleshooting and high CPU usage fixes for runtime crash diagnosis.

Want to just play without the headaches? Join Astroworld MC, IP play.astroworldmc.com, Java + Bedrock.