Cafora Docs
Troubleshooting

Server Crashes

Diagnose and fix Minecraft server crashes on your Cafora host.

Server crashes interrupt gameplay and can lead to data loss. This guide helps you find the cause and fix crashes.

Finding Crash Information

Console Output

The Pterodactyl Panel console shows the last messages before a crash. Look for stack traces (lines of Java code starting with at).

Crash Reports

Check the crash-reports/ folder in your server files for detailed crash dumps.

Log Files

Review logs/latest.log for events leading up to the crash.

Common Crash Causes

Out of Memory

See Out of Memory errors.

Plugin/Mod Conflict

  • Two plugins doing incompatible things
  • Mod version mismatch with server software
  • Missing required dependencies

Corrupted World Data

  • Corrupted chunk causing crash on load
  • Fix with region fixer tools or restore from backup

Invalid Configuration

  • Malformed YAML/JSON config files
  • JVM flags with invalid values
  • server.properties with impossible settings

Diagnostic Process

Read the crash report to identify the specific error.
Search the error message for known causes.
If a plugin is mentioned, temporarily disable it.
If world corruption is suspected, try loading without the world.
Restore from a backup if needed.
Contact Cafora Support with the crash report if unresolved.

On this page