Read the console first
Almost every failure prints a clear cause in Pterodactyl Console.
Common causes
| Symptom | Likely fix |
|---|---|
| You need to agree to the EULA | eula=true |
| OutOfMemoryError | More RAM or lighter pack |
| Mod/plugin version mismatch | Align jar versions |
| Unknown/corrupt chunk | Restore world backup |
| Port already in use | Wrong allocation / duplicate process |
Checklist
- Scroll to the first ERROR/Exception in the boot log.
- Confirm Java version vs server jar requirements.
- Remove the last plugin/mod you added; retry.
- Restore
world/from backup if region files are damaged. - Open a ticket with the console snippet if stuck — client login.
Related guides
Frequently Asked Questions
Console stops at EULA?
Set eula=true in eula.txt and restart.
UnsupportedClassVersionError?
Wrong Java version for the jar — adjust the egg/Java or jar.
World corrupt?
Restore from backup; do not delete world/ until you have a copy.
Need help?
If you are stuck after following this guide, open a ticket from the Chapter22 client area with the exact error, the port or DNS change you made, and whether the service listens locally (ss / Resource Monitor) but fails externally.
Build the server. Grow the community. Start your next chapter.