Saltar al contenido
Clodo

What to do when your server crashes

Steps to read the crash card and console, inspect log files, restart your server, and check backups when your server crashes.

Principiante5 minActualizado:29 de octubre de 2026

1. Check the crash card and console#

When your server unexpectedly stops, a crash card appears in the panel summarizing the event. Switch to the console tab to review the latest error output. The final lines typically indicate whether the stoppage was caused by an out-of-memory error, missing dependency, or a failing plugin.

Console tab in the panel showing server status, live log output, and resource usage cards
In the Console tab, you can monitor server status, live log output, and resource usage.

2. Locating logs and crash reports#

1

Inspect latest.log

Open the File Manager and navigate to the logs folder. The latest.log file records all server operations right before the crash, including stack traces and 'Caused by' details.

2

Check the crash-reports folder

When the server halts due to a fatal exception, a crash-reports directory is generated in the root path. The dated crash-*.txt files pinpoint which plugin or thread caused the failure.

3. Restarting and checking backups#

Solución de problemas

Síntoma

Server crashes repeatedly during startup

Causa

A newly added incompatible plugin or broken configuration file

Solución

Remove the offending plugin from the plugins folder via the File Manager and restart the server

Síntoma

Crash occurs while loading world data

Causa

Corrupted chunk or region files caused by an abrupt power or process halt

Solución

Go to the Backups tab, select the most recent healthy backup taken before the incident, and restore it

¿Te ha resultado útil esta guía?

Los comentarios van directamente al equipo que mantiene esta guía.

¿No encontró una solución?

Puede abrir una solicitud al equipo de soporte desde el panel.

Abrir una solicitud