Server Keeps Crashing

Server won't stay running? Let's diagnose and fix the issue.

Quick Diagnosis

Common Crash Causes

1. Not Enough RAM

Symptoms:

• Server freezes or crashes during gameplay
• Console shows "OutOfMemoryError"
• RAM graph always at 100%

Solution:

• Check your plan's RAM allocation
• Large modpacks need 8GB+ RAM
• Consider upgrading your plan if consistently maxing out

2. Mod/Plugin Conflicts

Symptoms:

• Crash immediately on start
• Console shows mod name in error
• Started crashing after adding something new

Solution:

1. Check console for which mod/plugin caused the error
2. Go to Files → mods or plugins
3. Remove the problematic file
4. Try starting again

3. Corrupted World

Symptoms:

• Crash when loading world
• Console shows "Failed to read chunk" or region file errors
• Crash happens at specific coordinates

Solutions:

• Restore a backup - Best option if you have one (see Backups)
• Delete corrupted region - Advanced, only if you know the coordinates
• Create new world - Last resort, delete the world folder and restart

4. Wrong Java Version

Symptoms:

• Crash on start with "Unsupported class version" error
• "Java version X required" message

Solution:

Go to Startup and change the Docker Image to match your Minecraft version:

5. Missing Dependencies

Symptoms:

• Console says "Missing required mod: X"
• Error mentions "Fabric API" or similar

Solution:

1. Read the error message - it tells you what's missing
2. Download the required mod/library
3. Add it to your mods folder

Common dependencies:

• Fabric API - Required by most Fabric mods
• Architectury - Required by many cross-platform mods
• Cloth Config - Config library for many mods
• Kotlin for Forge - Required by some Forge mods

6. EULA Not Accepted

Symptoms:

• Server stops immediately after starting
• Console says "You need to agree to the EULA"

Solution:

1. Go to Files
2. Open eula.txt
3. Change eula=false to eula=true
4. Save and start the server

Reading Crash Logs

Crash logs tell you exactly what went wrong. Here's how to read them:

Key things to look for:

• Error message - Usually near the top, describes the problem
• Mod name - Look for mod IDs in the stack trace
• "Caused by:" - The actual error that triggered the crash
• Line numbers - Help identify exactly where it broke

Find crash logs:

• Files → crash-reports/ - Detailed crash reports
• Files → logs/latest.log - Most recent server log
• Console - Shows errors in real-time

Emergency Recovery

If nothing works, try these steps in order:

1. Restore a backup if available
2. Remove recently added mods/plugins
3. Delete the world folder to start fresh (losing progress)
4. Reinstall the server via Settings → Reinstall

Still Crashing?

If you can't figure it out, join our Discord and share:

• Your server name or email
• The crash log or console error
• What you were doing when it crashed
• Any mods/plugins you recently added

We'll help you get back online!