Minecraft server errors and how to fix them

By Tabi Cloud · Updated 17 November 2026

Find the message you see below. Most errors come from the server being offline, a wrong address, or a version mismatch.

"Connection refused: no further information"

Your game reached the address, but nothing answered on that port.

  1. Is the server running? Open the panel Console. It should say Done and not be stopped or still starting.
  2. Is the port right? Copy the address and port exactly from the panel. A server on port 25566 will refuse you on 25565.
  3. Did it crash on start? Scroll the console for an error, often a broken plugin or mod (see below).
  4. Home server: the port is not forwarded, the firewall blocks Java, or your internet uses CGNAT. See port forwarding.

"Connection timed out"

Nothing answered at all. The address is wrong, the server is offline, or your network blocks the connection. Try mobile data to rule out your Wi-Fi, and check the server address again.

"Outdated client" or "Outdated server"

You and the server are on different Minecraft versions. Join with the server's version (the launcher can pick older versions), or change the server version in the panel. Add the ViaVersion plugin to let newer clients join an older Paper server.

"Failed to verify username"

Minecraft's login servers could not confirm your account. Restart your game and launcher, and log in again. If it keeps happening for everyone, Mojang's login service may be down for a while. Do not turn off online-mode to get around it: that lets anyone join as anyone.

"You are not white-listed on this server"

The whitelist is on. In the console, run whitelist add PlayerName (Bedrock players with Floodgate: fwhitelist add .Name), or set white-list=false in server.properties.

The server will not start

  • EULA: set eula=true in eula.txt.
  • Wrong Java version: Minecraft 1.20.5 and newer need Java 21. Pick the right Java image in the Startup tab.
  • A plugin or mod crashes it: read the last error lines, then move the jar it names out of plugins or mods and try again.
  • Out of memory: the console shows OutOfMemoryError. Lower view-distance, remove heavy mods, or move to a bigger plan.
  • Corrupted world: restore the last backup.

The server lags

Type tps in the console on Paper. 20 is perfect; under 18 players notice. Lower simulation-distance, pre-generate the world with Chunky, limit huge mob farms, and run spark profiler (the spark plugin) to see what uses the CPU. If it is just too many players, see how much RAM you need.

Still stuck? Open a ticket on our Discord with a screenshot of the console.

Ready to start your server?

Join our Discord, open a ticket and our team sets everything up within minutes.