Server won't start
1. Read the console
The last lines of the console tell you almost everything. Look for one of these.
| Console says | Fix |
|---|---|
You need to agree to the EULA | Set eula=true in eula.txt |
Unsupported class file major version | Wrong Java version — pick the right one in Startup |
No such file: server.jar | Wrong JAR selected under Startup |
Can't keep up then crash | Out of RAM — upgrade the plan |
Address already in use | Another instance uses the port — open a ticket |
2. Check resources
Panel graphs: if RAM is pinned at 100%, the JVM is being OOM-killed. Reduce mods/plugins or add RAM.
3. Reinstall or repair
Still stuck?
- Stop.
- Take a backup first.
- Panel → Settings → Reinstall Server (this wipes files — you were warned).
- Restore the backup.
4. Watch the boot
Start and stay on the Console. A server that exits within seconds is usually a config/JAR problem; one that dies after minutes is usually resources.
INFO
Changing the server version? Update your plugins/mods to matching versions, or the server will crash in a loop.