A server that crashes every few hours is more frustrating than one that does not start at all. The cause is almost always in the crash log, but those are hard to read if you do not know where to look. Below are the seven most common causes, how to recognize them and what to do.
Finding crash logs
Minecraft writes crash logs to two places:
crash-reports/: detailed reports with timestamp, error message and an overview of loaded plugins and mods.logs/latest.log: the server log. On a crash, the error is at the bottom, just before the line "Stopping server".
Upload the crash report to mclo.gs for a readable version with automatic analysis.
1. Not enough RAM (OutOfMemoryError)
The most common crash. The log reads: java.lang.OutOfMemoryError: Java heap space. The server needs more memory than is allocated.
Fix: increase memory via the game panel or upgrade your plan. Never give Minecraft more than 75% of available system memory if you run on a VPS.
2. Plugin incompatibility
A plugin that is not compatible with your Minecraft version crashes the server on load or on a specific action. The log shows the plugin name followed by NoSuchMethodError or ClassNotFoundException.
Fix: remove the plugin and check on SpigotMC or Hangar whether an update is available for your version.
3. Wrong Java version
Minecraft 26.x requires Java 25. Running Java 21 means the server either does not start or crashes on specific features. The error reads: UnsupportedClassVersionError or class file version 69.
Fix: set the correct Java version in the Startup tab. Java 25 for 26.x, Java 21 for 1.20.5 to 1.21.11, Java 17 for 1.18 to 1.20.4.
4. Corrupt chunks
A chunk that got corrupted (from an unexpected shutdown or a bug) crashes the server every time that chunk loads. The error contains ChunkLoadException or refers to specific coordinates.
Fix: delete the damaged region file from world/region/. The file is named r.X.Z.mca where X and Z are the region coordinates. The server regenerates the area. Always make a backup first.
5. Infinite loop in a plugin or datapack
A plugin that causes an infinite loop hangs the server until the watchdog timer kills it. The message reads: The server has not responded for 60 seconds followed by a thread dump.
Fix: the thread dump shows which plugin is blocking the thread. Remove or update that plugin.
6. Storage full
When the disk is full, the server cannot save the world and crashes. The error message contains IOException or No space left on device.
Fix: delete old backups, unnecessary logs or unused worlds. The Files tab in the game panel shows your disk usage.
7. Network or host timeout
Not a real crash, but the server appears offline. The game panel shows "offline" while the container is still running. This happens during heavy chunk generation or a DDoS attack.
Fix: check the console. If the server still responds but is slow, wait for the operation to finish. During a DDoS you see thousands of connection attempts; contact support.
At HostValues, the game panel monitors your server automatically and restarts it on a crash. For help with crash logs, open a ticket.
My server crashes without an error message
If there is no crash report and latest.log stops abruptly, the operating system probably OOM-killed the process. The kernel terminates it without giving Java a chance to write a report. Lower -Xmx or upgrade memory.
Can crash logs be analyzed automatically?
Upload them to mclo.gs. The site recognizes common errors and provides a readable analysis. For complex problems, share the link in a support ticket.
Does reinstalling the server help?
Rarely. Most crashes come from configuration, plugins or the world, not from the server files themselves. A reinstall without fixing the problem means the crash returns as soon as you restore the same plugins and world.
