Skip to content

Enshrouded 1.0 is out! 🎉 Get 25% OFF your next Enshrouded Server today!

Fix a Minecraft server that will not start

Read the Console for the first real error, match the message to a fix, and undo your last change in the safe order, from add-ons to backups.

Updated 5 min read

When a server will not start, the Console is the first place to look. Find the first real error, not the lines after it. This guide shows where to look, lists the messages we see most with what they mean, and gives the safe order for undoing a change that broke the server.

Checked against Minecraft 26.3's own server files and the OpenJDK 25 launcher, October 2026.

Read the Console first

  1. Open the Console tab and click Start.
  2. Scroll to the first error after the start. Start with that line, not the ones after it.
  3. To save the recent log, click Download Log and choose Last hour, or Earlier boots (7 days) for a start before the last restart.

A healthy start ends with a line like Done (4.2s)! For help, type "help". The panel counts the server as started when it sees )! For help, type in the log. Before that, a line reading Preparing level means the world is loading.

Match the message to the fix

The Console saysWhat it means and what to do
You need to agree to the EULA in order to run the server.The EULA was not accepted. Click Start and accept the Accept the Minecraft EULA prompt, which writes eula=true. Or open eula.txt in the File Manager, change the line to eula=true and click Save.
Failed to load datapacks, can't proceed with server load.A data pack is broken. Open Datapacks under Content, click Installed and Disable the newest one. The message suggests a --safeMode flag, but you cannot change the startup command here, so disabling the pack is the way.
Failed to load world data followed by World files may be corrupted.On 26.3 the line reads Failed to load world data. World files may be corrupted. Shutting down. On 1.20.4 and 1.21.11 the same message adds the file paths: Failed to load world data from ... and ... World files may be corrupted. The 1.16.5 and 1.17.1 servers we scanned do not contain it. Fix No key dimensions in MapLike (level.dat) and Fix corrupted chunks and region files cover the details, and Undo your last change below covers restoring a backup.
This world was created by an incompatible version.On 26.3 the server compares a version series name saved in the world with its own, and the two differ. The 1.16.5 and 1.17.1 servers we scanned do not contain this text. Set the version in the JAR Manager to the one the world came from.
**** FAILED TO BIND TO PORT!Something else holds the server's port. See Fix "Failed to bind to port" on Minecraft.
already locked (possibly by other Minecraft instance?) or Failed to check session lock, abortingThe world's session.lock file could not be used. On 1.16.5 and newer the first message means another process holds it. On 1.12.2 to 1.15.2 the second means the file could not be read or written. See Fix "Failed to check session.lock" error.
Error: Unable to access jarfile, Invalid or corrupt jarfile or zip END header not foundA jar is missing or damaged. See Fix "ZIP END header not found" jar errors.
java.lang.OutOfMemoryError: Java heap spaceThe server ran out of memory. See the next section.
A plugin or mod name next to the errorAn add-on failed. See Fix mod and plugin errors on Minecraft.

If the last line is only Failed to start the minecraft server, the real cause is a few lines above it. Find Minecraft server logs and crash reports and Minecraft server exit codes 1, 137 and 143 help with the rest.

Out of memory

Your plan's RAM is fixed, and the panel sets the Java heap from it at every start, so you cannot raise it by editing a flag. Take load off instead: remove the newest add-ons, lower View distance (chunks) and Simulation distance (chunks) under Performance in Config Editor, or choose a larger plan with Change plan in Settings. How much RAM does my Minecraft server need? gives sizes.

Undo your last change

Start by undoing the last thing you changed, in this order:

  1. A new plugin or mod: open Plugins or Mods, click Installed and Disable it, then Start the server.
  2. A software or version change: open the JAR Manager. If a Previous jar kept. card is there, stop the server and click Restore previous jar.
  3. Anything else: open Backups and restore the last backup that worked.
Warning

Restoring a backup overwrites the current server files with the ones in the backup, and the panel says this cannot be undone. It stops the server first and starts it again afterwards. Take a new backup first if the server can run at all.

Last resort

Reinstall under Danger zone in Settings runs the installer again. The panel warns that files may be overwritten or removed, so make a backup first. Use it only when the steps above did not work.

If the server still will not start, send support the downloaded log through Contact support and open a ticket.

Was this guide helpful?

Still stuck?

Talk to a real person, we answer fast.

  • Open a ticket

    Paste the exact error and name your server, so we can look at it from our side.

  • Ask on Discord

    Chat with the team and other server owners.

  • Browse the Help Centre

    Versions, mods, plugins, backups and RAM sizing, all in plain English.

Ready to launch your Minecraft server?

Aussie hardware, NVMe disks and DDoS protection, with the version and mod loader yours to change whenever you like.