Skip to content

Your Minecraft server will not start

← Back to docs index

Work down this list. It is ordered by how often each one is the answer, and the first four cover most of them.

1. Read the last twenty lines, not the first

Section titled “1. Read the last twenty lines, not the first”

Scroll to the end of the log. A Java stack trace is printed innermost first, so the top of the wall of text is the least interesting part. What you want is the last Caused by: line and whatever follows it. That single line usually names the problem.

Two shapes tell you where you are:

  • Exception in thread "main" or a crash report path near the end means the game itself failed.
  • The log simply stopping mid-line, with no exception at all, means something killed the process from outside. Jump to point 3.

2. UnsupportedClassVersionError means the wrong Java

Section titled “2. UnsupportedClassVersionError means the wrong Java”
java.lang.UnsupportedClassVersionError: net/minecraft/server/Main has been compiled
by a more recent version of the Java Runtime (class file version 65.0)

Class file 52 is Java 8, 60 is 16, 61 is 17, 65 is 21, 69 is 25. The message means the server needs a newer Java than it is running on; the reverse, an old pack on new Java, usually fails with a mixin or reflection error instead.

Minecraft version Java
1.16.5 and earlier 8
1.17 16
1.18 and 1.19 17
1.20 to 1.20.4 17
1.20.5 to 1.21.x 21
26.1 and later 25

Old packs genuinely need Java 8. Newer is not better here.

The log stops mid-sentence, there is no crash report, and the container reports 137. That is an out-of-memory kill: the process asked for memory the machine did not have, so it was terminated.

Almost always the Java heap was set to the same number as the machine’s memory. The heap needs the machine’s memory minus the JVM’s own overhead, which is 0.5 to 1.5 GB on a modded server. Drop the heap, or raise the machine. How much RAM a server needs has the numbers.

Two classics with one-line fixes:

  • You need to agree to the EULA in order to run the server. Set eula=true, in eula.txt or with the environment variable your setup uses.
  • Address already in use or FAILED TO BIND TO PORT. Something else holds 25565, often a previous copy of the same server that never fully stopped. Find it and stop it rather than changing the port, or you will end up with two.
Mod X requires mod Y, which is missing
Fabric API is not installed

Fabric mods overwhelmingly need the Fabric API as a separate file. Forge and NeoForge mods list their dependencies in the error itself. Install the named version, not the newest one: “requires 0.91.x” means that line, and 0.92 will fail the same check.

Sometimes the missing dependency is the loader itself:

Mod X requires forge 47.4.14 or above
Mod ID: 'forge', Requested by: 'x', Expected range: '[47.4.14,)', Actual version: '47.4.10'

The fix is a newer loader build, not a different mod. “47.4.14 or above” means any build from there up, and Forge does not publish every number, so the build to install may be the next one along. On a modpack, update the pack first: a pack whose own loader version is too old for its mods is a bug for its author to fix.

6. A mod is for the wrong loader or version

Section titled “6. A mod is for the wrong loader or version”

A jar for a different loader does not fail politely. Expect a mixin error, a NoClassDefFoundError, or a crash inside a class you have never heard of. Check the jar’s page: the loader and the Minecraft version both have to match exactly. 1.20.1 and 1.20.4 are different games as far as mods are concerned.

This world was created by a newer version of Minecraft

Worlds upgrade forwards and never backwards. Restore the backup from before the upgrade, or run the version the world expects. There is no downgrade path that keeps the chunks intact.

When it crashed after running fine for weeks

Section titled “When it crashed after running fine for weeks”

Different question, usually a different answer:

  • It crashed under load, with timings showing long pauses: garbage collection, so look at heap size before mods.
  • It crashed at the same point in the world: a corrupt chunk or a broken entity. The crash report usually names coordinates.
  • It crashed right after an update: the mod that updated is the suspect, even if the trace points elsewhere. Roll it back and see.
  • It crashed on restart, having been fine before: check the disk. A full disk produces spectacular and misleading errors.

Post the whole log, not the last line, and say what you changed before it broke. Paste it somewhere designed for it, such as mclo.gs, rather than into chat. Include the Minecraft version, the loader, the pack and its version, and how much heap the server has. A report with those four facts gets answered in one reply; without them it takes five.

Crashes are detected from the container’s own exit, so a server that dies at three in the morning is recorded with its log excerpt rather than found the next day. The usual suspects on this page (the EULA, the wrong Java, a world from a newer version, a port already in use, Java running out of memory) are recognized in that log and named in the history entry with what to do about them, and auto-restart leaves those alone, since restarting will not fix them. Crash reports are parsed on arrival: the exception is highlighted, the stack is collapsible, and mods that appear in the trace are listed as suspects.

Any report can be shared to mclo.gs from its card when you need help (after a confirmation, since the paste is public), and the console’s Download menu has every log file as one zip, so “post the whole log” is a download rather than an archaeology project. An out-of-memory kill is recorded as an out-of-memory kill, which saves the usual hour of blaming a mod. If something else genuinely needs the port, the Game Port card on Settings → Configuration moves the server to a free one.

A loader that is too old is changed from the server’s Versions tab, which checks the build exists and takes a backup before it rebuilds the server (changing the mod loader version).

Related: how much RAM a server needs, choosing a loader, creating and managing servers.