Capture the useful context
- Record the game, server type and exact version.
- Note what changed immediately before the failure.
- Open the latest console/crash log and find the first relevant error around the failure.
- Check Server Health in your panel. It lists recognized problems from recent console lines, such as a memory limit, a mod mismatch or a full disk, with a suggested fix for each.
- Check whether memory, disk or CPU pressure was visible near the incident.
- Record the latest successful backup before attempting a destructive repair.
Common patterns
Version mismatch errors often point to an incompatible plugin, mod, loader or runtime. Missing dependency errors usually identify another package the failing component expects. Out-of-memory failures should be separated from CPU stalls or infinite restart loops.
A later stack trace can be a symptom of the first error, so start near the beginning of the failure rather than copying thousands of unrelated log lines.
When opening support
Attach only the relevant excerpt and describe what changed. Include the game, server version and the time the problem started. Support can then check your allocation, recent resource use and backup status alongside the log. Remove passwords, tokens and other secrets before sharing any log.