Minecraft server errors, and how to fix them

Updated 29 Sep 2026 · 3 min read

The short answer

Each page here takes one error message players and server owners search for: the exact words, what causes them, and the fix. Every cause was checked on a real server, and each page says how. Find the words from the screen or the log below.

1Errors, by what you see

Players can't connect, or get dropped

  • Connection refused, as io.netty's AnnotatedConnectException: nothing takes connections at that address and port. The same page covers connection timed out.
  • Timed out: a player in the game and the server stopped hearing from each other.

Players are turned away

The server lags

The server crashes while it runs

The server won't start

The world is damaged

  • World files may be corrupted: the server can read neither level.dat nor level.dat_old, or a chunk comes back as new land after Failed to load chunk.

2Where the whole message is

  • A player's screen shows the errors from joining: "Failed to connect to the server", then the reason.
  • The server's log, logs/latest.log, has everything the server printed since it started. In Playkeeper it's the Console tab.
  • Crash reports go in the server's crash-reports folder, one file for each crash, with the error's stack trace.

3What Playkeeper explains by itself

When a server stops by itself, Playkeeper reads its log and names the cause on the server's Overview, with a button for the fix where there is one. It knows these:

  • The port is already in use, or the server couldn't open its port.
  • The server ran out of memory, of memory for code, or hit its thread limit.
  • The disk is full.
  • The Minecraft EULA hasn't been accepted.
  • The server needs a different Java.
  • The world is already open somewhere else, its level.dat file is damaged, or part of it may be damaged. From 0.4.8, it can make a new level.dat that keeps every build.
  • From 0.4.8: one mob, cart or block crashes the server each time the game runs it. It names which and where, and removes just that one.
  • The server froze, or was stopped abruptly.
  • A data pack stopped the world from loading.
  • The server isn't allowed to use its own files.
  • A mod needs another mod or a different version of one, clashes with another, or can't load. From 0.4.8, also a mod that only runs in players' games.

Questions

Where is the Minecraft server log?

In the logs folder next to the server, as latest.log; older logs are compressed beside it. In Playkeeper, the Console tab shows it as it's written.

What does Failed to connect to the server mean?

The game couldn't reach a Minecraft server at that address and port. The line under it says why, like Connection refused or connection timed out.

A server that tells you what went wrong.

Free and open source. Playkeeper reads a crashed server's log and names the cause, with the fix.

curl -fsSL https://playkeeper.io/install | sudo sh
Try the live demo