My Server Won’t Start

Almost every startup failure explains itself in the last few lines of the Terminal tab (see Using the Terminal) — that’s the first place to look before trying anything below.

EULA Not Accepted

The most common one, especially right after first install. Minecraft refuses to start until you’ve agreed to Mojang’s EULA. Open eula.txt in the Files tab and change:

properties

eula=false

to:

properties

eula=true

Not Enough Memory Allocated

If the log ends with something like OutOfMemoryError or the process just dies with no clear error, your world size or plugin/mod list has likely outgrown your plan’s RAM. AtomicHost sizes the Java heap automatically from your plan’s memory (see Paper Setup Guide) rather than a flag you tune yourself, so the fix here is usually upgrading your plan rather than editing a startup flag.

A Plugin or Mod Is Crashing It

If the server gets partway through startup and then stops, scroll up from the bottom — the crash is usually a stack trace naming a specific plugin or mod. Move the suspect out of plugins//mods/ (rename the folder or the jar so it isn’t loaded) and start again to confirm.

Tip

Add mods/plugins one at a time when setting up a new server. If ten go in at once and something breaks, you’re stuck bisecting all ten instead of knowing immediately which one it was.

Corrupted World Data

A crash during a save (power loss, a kill instead of a graceful stop) can corrupt world files. If the log mentions a specific chunk or region file failing to load, restoring your most recent backup is usually faster than trying to repair it by hand.

Still Stuck?

Copy the last 20–30 lines of the console log and ask in Discord — that snippet is almost always enough for someone to spot the problem immediately.