Troubleshooting a Crash

If your server just cut out or won't start, don't panic. The answer is almost always hidden in the logs, and usually, it's just a single mod or setting that needs a quick tweak. Mission Control gives you a real-time Console and access to a logs/ folder to help you find the culprit.

1. Read the Console

When a server crashes, the last few lines in the console usually tell you exactly what happened. Look for these red flags:

OutOfMemoryError: Your server is hitting its limit. You might need to upgrade to a higher Tier (more RAM).
Mod loading error: A mod is missing a required dependency or you’re running the wrong version for your loader.
EULA not accepted: We usually handle this for you, but if the server stops, double-check that you've accepted the Minecraft EULA.

2. Hunting the Crash Report

If the console doesn't make sense, look in the crash-reports/ folder in your File Manager.

Open the most recent .txt file.
Look for the "Description" line. This is the plain-english summary of the crash.
Check the "Stacktrace". If you see a specific mod name (like worldedit or twilightforest) appearing over and over, that mod is likely causing the issue.

3. Quick Fixes That Usually Work

Double Check Versions: Make sure your Minecraft client version (like 1.20.1) exactly matches what the server is running.
Fix Your Configs: If you just edited a file and the server broke, you probably have a YAML syntax error. Use an online validator to check your spacing!
Mod Conflicts: Sometimes two mods just don't get along. Try removing the one you most recently added. See our Conflict Guide for a systematic way to find the troublemaker.

Not a fan of reading log traces? Copy the text and paste it into our Discord's #support channel. Our community is great at spotting issues.