CAFORADocs
Troubleshooting

Server Crashes

Diagnose and fix Minecraft server crashes on your Cafora host.

Illustrated procedure

Screenshots show the current application with demonstration data. Use your own service details; click an image to inspect it at full size.

Check the console

Open Essentials → Console. Check the current state, startup output and errors before making changes. Wait for Done or your software’s ready message before joining.

Check the console
Check the console2026-11-11 · Current application interface · demonstration data · Open full-size image

Locate the file log

Under Files, double-click logs and locate latest.log. Check modification times. Preserve the relevant file before a restart replaces or rotates it.

Locate the file log
Locate the file log2026-11-11 · Current application interface · demonstration data · Open full-size image

Read the complete error context

Open the log in the editor and inspect the earliest relevant error and surrounding lines. Remove tokens, passwords and private player details before sharing. Do not diagnose from the last line alone.

Read the complete error context
Read the complete error context2026-11-11 · Current application interface · demonstration data · Open full-size image

Describe the request to support

Open a support ticket with the service or invoice ID and the requested action. For connection issues include time, error and MTR evidence. Never include passwords, tokens or card details.

Describe the request to support
Describe the request to support2026-11-11 · Public page · no private account data · Open full-size image

Retain evidence before restarting repeatedly

Open 文件 / Files → logs and save the relevant log before another restart rotates it. If a crash-reports directory exists, retain the report for the incident too; not every forced exit creates one. The screenshot identifies files without exposing their contents.

Record the exact time, panel state and recent changes. A Java exception, out-of-memory kill, watchdog stop and manual shutdown are different causes. Include the first relevant error and its context; a final disconnected line alone does not identify the cause. See log collection. Avoid repeated restarts or deleting world/plugin data until the evidence points to a specific repair.

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.


Service information · Backups · Support

On this page