Transcript
The full narration, chapter by chapter. Click a time to play the video from there.
Intro
Game server won't start, or stuck on installing? The console almost always tells you why. Here's how to read it, and fix it.
Stuck on installing
Stuck on installing? The install runs in a temporary container. Open the console, and read the install output. Usually it's a download that failed, a wrong setting, or a full disk. Fix it, then press Reinstall in Settings.
Back up first
Careful: reinstalling can replace your files, so take a backup first.
Exited with code
If the server starts and then stops with "exited with code", scroll up in the console. The most common causes: the startup file name doesn't match, like the wrong jar, there isn't enough RAM, the wrong Java version, or the EULA isn't accepted.
Java version
For the Java version, open Startup and pick the Docker image that matches the game version. Newer Minecraft needs a newer Java.
Port in use
And if you see "address already in use", the port is taken. Every server needs its own free port, in the Network tab.
Recap
Quick recap: read the console, fix the startup, RAM, Java or port, and back up before you reinstall. On ESAGAMES, we watch the nodes for you.


