Español
English
Français
Português
💾 java.lang.OutOfMemoryError: Java heap space
The server has filled all the memory it was given and shuts down. It usually happens with large modpacks, many players, or a mod or plugin that keeps piling up data. Check real usage in the panel and compare it with how much RAM a Minecraft server needs; if it truly doesn't fit, you need a plan with more memory.🧮 Invalid maximum heap size · Could not reserve enough space for object heap
These show up at startup, before the server loads anything, almost always on a home PC. There are three causes:- The parameter is mistyped. It's
-Xmx4G, all together;-Xmx 4Gand-Xmx=4Gboth fail. - 32-bit Java. It can't reserve several gigabytes. Install 64-bit Java;
java -versiontells you which one you have. - You're asking for more memory than the machine has free. Lower the value.
🐢 Can't keep up! Is the server overloaded?
The server is running behind: it can't get through its 20 ticks per second. It isn't a failure but an overload warning, and it has several possible causes. We go through them one by one in what "Can't keep up!" means and how to fix it.🔌 **** FAILED TO BIND TO PORT!
The server couldn't open its port. The clue is in the line just above:Address already in use: another process holds that port, usually a copy of the server that never closed. Close it or restart the machine.Cannot assign requested address: inserver.properties,server-ipis set to an IP that doesn't belong to that machine. Leave it empty.
🧩 Mod … requires forge 47.2.0 or above
The numbers vary from case to case. The mod needs a newer Forge than the one installed. Update Forge to that version or later, within the same Minecraft version, or use an older release of the mod. On ZentexNode the version is changed from the panel: how to change the server version without losing data.💥 The server closes on startup after adding a plugin or mod
Rename the.jar you just added to .jar.disabled and start again. If it works now, that was the one: check it's built for your Minecraft version and your server type. The exact reason is at the end of logs/latest.log or in the crash-reports folder.⏱️ Connection timed out: no further information
The game gets no answer from that address: the IP or port is mistyped, a firewall is in the way or, if the server runs in someone's home, the ports aren't open on the router.If the message is
Connection refused: no further information, the address answers but nothing is listening on that port: the server is off, still starting, or the port is wrong.🔐 Failed to login: Invalid session (Try restarting your game and the launcher)
Your account session has expired or couldn't be validated. Close the game and the launcher completely, sign in again and reconnect. If every player gets it at once, the likely cause is an incident with Minecraft's sign-in services, and all you can do is wait.You'll see advice to set
online-mode=false in server.properties. Don't: the server then stops checking accounts and anyone can join under any name, including an administrator's.📦 Internal Exception: io.netty.handler.codec.DecoderException
It usually comes with text such asIndex 26 out of bounds for length 5 or Badly compressed packet. The game received a packet from the server that it can't read. On modded servers, the usual reason is that the player and the server don't have exactly the same mods at the same versions: make the modpack match on both sides.⌨️ Incorrect argument for command
The command is mistyped. The<--[HERE] marker shows where the game stopped understanding it: check what comes right before. Watch out after updating, because some commands change between versions. For example, since Minecraft 1.21.11 the keepInventory rule is written keep_inventory.