Server Crash Recovery & Reading Crash Logs
Identify why your server is crashing and configure automatic restarts after an error.
Advanced6 min
1. Find the crash log file
When a server crashes, Java or the game engine usually generates a log. Look in your File Manager for files like 'hs_err_pid.log', or the most recent files in the 'logs' or 'crash-reports' folder.
2. Spot 'Out of Memory' (OOM) errors
One of the most common crash causes is running out of RAM. Search your logs for terms like 'OutOfMemoryError', 'Killing process' or 'Exit code 137'. This means your server needs more memory than your current plan has. Optimize your plugins or upgrade your plan.
3. Enable automatic restart
In the VylorNode panel under 'Schedules', you can create a task that checks if the server is offline and automatically starts/restarts it.
Still stuck?
Tell support what you already tried so we can help faster.