The server stops: crashes and their causes

When the server stops with an error, the panel saves the last 500 lines of the console from that moment and tries to recognise the cause. You do not need to catch the error live.

Where to see it

Panel → Servers → server → Event log: the crash is marked together with the recognised cause. Click it to see the saved console.

The most common causes

• EULA not accepted: accept it when starting the server or set eula=true in eula.txt.
• Wrong Java version: change the Java image in Server settings → Startup. New game versions need newer Java.
• No server file (.jar): install an engine in Add-ons → Engine.
• Port in use: server-port in server.properties must match the server's port in the panel.
• Not enough RAM: use fewer mods and plugins or move to a bigger package in Extend.
• World error: restore the last good backup.
• Plugin or mod error: the saved console shows which one failed to load. Update or remove it.

Crash notifications

We can tell you about a crash right away:

• by a direct message on Discord or by e-mail: choose it in Your profile → Notifications;
• on a channel of your Discord server through a webhook: set it in Server settings → Notifications.

If the server crashes again and again, direct messages and e-mails about it come at most once every half hour, not as a flood.