Exit code 137 or killed during startup

The console says the server stopped with exit code 137.

The server used more memory than the plan allows and was stopped by the system.

Before you start: Access to Startup.

Step by step

1. Open Startup and remove any -Xmx/-Xms values you added; the plan's memory is applied for you with room for overhead.
2. Remove heavy mods or plugins added recently.
3. For large modpacks, upgrade to the RAM the pack recommends.
4. Restart and watch memory in Statistics during startup.
5. Check Startup has not been changed to a different jar or Java image that needs more memory.
6. If it still happens with no changes and a light setup, send support the server ID and the time it stopped.

Check it worked: The server starts and stays running.

Why it happens: Java's heap (-Xmx) plus its overhead exceeded the container's memory, often from custom startup flags or a heavy modpack.

More guides on Crashes, startup failures, and errors:

• Find and read crash reports and logs
• Server stuck in a restart loop or will not start after an update
• Java version errors
• Failed to bind to port or unable to access jarfile
• Crash or error caused by a plugin
• Crash caused by a mod