Fix: Minecraft Server Won't Start
Diagnose and fix common reasons why your Minecraft server fails to start.
If your server won't start or immediately crashes, work through this checklist to identify the issue.
Diagnostic Checklist
Check the Console
Access the XGamingServer panel and read the Console output. The error message will tell you what's wrong.
EULA Not Accepted
If you see "You need to agree to the EULA", go to Files, open eula.txt, and change eula=false to eula=true. See Accept the EULA.
Wrong Java Version
Different Minecraft versions require specific Java versions:
| Minecraft Version | Required Java |
|---|---|
| 1.17+ | Java 16+ |
| 1.18+ | Java 17+ |
| 1.20.5+ | Java 21+ |
| 1.16 and below | Java 8 or 11 |
Check your Java version in Startup and change it if needed.
Corrupted Server JAR
If the JAR file is corrupted (incomplete download), go to Dashboard and click Reinstall Server.
Port Already in Use
The console will show "Address already in use" if another process is using the port. This is rare on hosted servers — contact support if you see this.
Incompatible Mods or Plugins
If the server started before adding mods/plugins, the new addition is likely the problem. Remove the last thing you added via Files and try again.
Out of Memory
If you see "OutOfMemoryError" or exit code 137, your server needs more RAM. Check Startup to increase memory allocation. See How Much RAM.
Corrupted World
If the console mentions "Session lock" or "level.dat", your world may be corrupted. Try restoring from Backups or deleting session.lock from the world folder.
💡 Tip: Always read the first error in the console, not the last. Later errors are often caused by the first one.
See also: Troubleshooting | Java Exit Codes
If you need help, join our Discord.
How is this guide?
