If your server won’t start or crashes immediately, this guide covers the most common causes and how to fix them.
Check the Console
The Console tab is your first stop. Look for red error messages near the bottom of the output. Common patterns:
1. “Error: Unable to access jarfile”
Cause: The server jar file was deleted or never installed.
Fix: Go to the Engines tab and reinstall your server engine.
2. “java.lang.OutOfMemoryError”
Cause: Your server needs more memory than your plan provides, usually from too many mods/plugins.
Fix: Remove unnecessary plugins/mods, or upgrade your plan for more RAM.
3. “Failed to bind to port”
Cause: The server port is already in use (often from a previous crash that didn’t clean up).
Fix: Click Kill in the console, wait 10 seconds, then Start again.
4. Plugin/Mod Crash
Cause: A plugin or mod is crashing during startup. The error will usually mention the plugin/mod name.
Fix: Remove the problematic .jar from the plugins/ or mods/ folder using the File Manager, then restart.
5. “EULA not accepted”
Cause: Minecraft’s EULA hasn’t been accepted.
Fix: Open eula.txt in the File Manager and change eula=false to eula=true. The panel usually handles this automatically.
Server Crashes After a Few Seconds
If the server starts but crashes within seconds:
- Check the Logs tab for the crash report
- Look for
latest.login thelogs/folder via File Manager - Search the error message online — most Minecraft errors are well-documented
Still Stuck?
If none of these solutions work:
The Logs page shows recent server logs with error highlighting.
Go to Submit a Ticket and include your server ID and the error message from the console.