How to Fix a Minecraft Server That Will Not Start
Fix a Minecraft server that refuses to start. Covers Java errors, EULA acceptance, port conflicts, corrupt files, and startup script debugging for 1.21+.
How to Fix a Minecraft Server That Will Not Start
The Problem
Server process exits immediately after starting
Console shows errors and the server never reaches "Done!"
Server starts but immediately shuts down
A Minecraft server that refuses to start can be caused by dozens of different issues. The key to fixing it is reading the console output or log file, which always contains the specific error. This guide covers the most common startup failures.
Quick Fix
Check the console output or logs/latest.log for the first error message. The most common causes are: EULA not accepted, wrong Java version, port already in use, or a corrupt server jar.
Step-by-Step Diagnosis
- Accept the EULA. On the very first start, the server generates
eula.txtand shuts down. Openeula.txtand changeeula=falsetoeula=true. Restart the server. - Check Java version. Run
java -version. Minecraft 1.21+ requires Java 21. If you see Java 8 or 17, install Java 21 and update your start script to use the correct path. - Read the log. Open
logs/latest.logor check the console output. Search for "ERROR", "Exception", or "FATAL". The first error is usually the root cause. - Check port conflicts. If you see "Failed to bind to port", another process is using port 25565. Kill it or change the port in
server.properties. See our Failed to Bind guide. - Verify the server jar. Re-download the server jar from the official source (papermc.io, spigotmc.org, etc.). Corrupt or incomplete downloads fail silently with "Error: Invalid or corrupt jarfile".
- Check the start script. Your start command should look like:
java -Xms4G -Xmx4G -jar server.jar nogui. Common mistakes: missing-jarflag, wrong jar filename, invalid JVM flags, missingnogui(not required but recommended). - Test with zero plugins. Move the
plugins/folder and restart. If the server starts, a plugin is causing the crash. Add plugins back in groups to find the offender. - Test with a fresh world. Rename the world folder and restart. If the server starts with a new world, the original world is corrupted.
- Check disk space. Run
df -h(Linux) or check disk properties (Windows). A full disk prevents the server from writing world data, logs, and temp files.
Common Startup Errors
You need to agree to the EULA- Editeula.txtand seteula=true.Unsupported Java version- Install the correct Java version for your Minecraft version.Failed to bind to port- Another process is using the port. Kill it or change ports.Invalid or corrupt jarfile- Re-download the server jar.Error occurred during initialization of VM- JVM flags are invalid. Common cause: allocating more RAM than the system has (-Xmx32Gon a machine with 16 GB).Could not reserve enough space for object heap- Same as above. Reduce-Xmxor use a 64-bit Java installation.Exception in server tick loop- A plugin or the world caused a crash during startup. Check which plugin or try a fresh world.
Common Causes
- EULA not accepted. The server generates eula.txt on first run and shuts down. You must edit the file manually.
- Wrong Java version. Each Minecraft version has a minimum Java requirement. Using an older Java produces immediate errors.
- Corrupt server jar. Interrupted downloads or disk errors produce unusable jars.
- Insufficient RAM. Requesting more RAM than available causes the JVM to refuse to start.
- Plugin crash. A faulty plugin throws an exception during initialization, crashing the server before it finishes loading.
FAQ
The server started before but now refuses. What changed?
Check what changed: a new plugin, a world edit, a config modification, or a Java update. Revert the most recent change and test.
How do I start a server without a GUI?
Add nogui to the end of your start command: java -Xmx4G -jar server.jar nogui. This is required on headless servers (VPS, dedicated hosts).
Can I recover a server that crashes instantly?
Yes. Start by removing all plugins and using a fresh world. If the server starts, add components back until you find the crash source. The log always tells you what went wrong.
Need a server that handles all this? Astroworld Hosting, NVMe SSDs, Pterodactyl panel, DDoS protection on every plan.