MINECRAFT HOSTING
GAME SERVERS
Game PanelAlmost every Minecraft server problem shows up as a line in the Console. Start there, then find your problem below. In the Console, click Errors to show only error lines, and read the last few lines before the server stopped. See How to use the console and run commands.
If you changed something just before the problem began, undo that first. It is the cause far more often than anything else.
The server will not start or stops straight away
| What you see | Cause | Fix |
|---|---|---|
| The server stops right after starting and the Console mentions the EULA | Mojang's End User License Agreement was not accepted. The Minecraft Wiki says the server shuts down at once without it. The panel normally accepts it for you at setup. | Open Files, then eula.txt. If it says eula=false, read Mojang's terms, change it to eula=true and save. If it keeps coming back, open a ticket. |
UnsupportedClassVersionError | A server, plugin or mod needs a newer Java than your server runs. The Paper documentation names this error as the sign of an outdated Java. | Install an older build of the plugin or mod (change the Minecraft version filter in the Modding tab, or upload an older jar by hand), or move to a Java that fits. Settings, then Launch Details shows the Java image your server uses and lets you choose another. The panel's own install message names the Java a plugin or mod needs. |
Failed to bind to port | The server was told to use a port or address it cannot have. The Minecraft Wiki says to leave server-ip empty. | Do not change the server port or address in the files. The panel sets them, and it normally empties server-ip for you at every start. If you changed them, open server.properties in Files, empty the server-ip line (the Server Properties (Java) page does not offer it) and restart. If it still fails, open a ticket. |
| The Console shows an error naming a setting or a file | A setting the game rejects, or a file with a typo | Put the last value back. See How to change your server settings |
| The server starts, then stops after loading, or stops with no error while players are on | It may have reached your plan's memory limit | Check Usage, then RAM, on Overview. See How much RAM does a Minecraft server need |
Server attempted to load chunk saved with newer version of minecraft! | The world was last saved by a newer Minecraft than the server runs. The Paper documentation says worlds cannot be downgraded. | Put the server on that version or a newer one, or restore a backup from before the upgrade. See How to change your Minecraft version or server type |
A single server tick took 60.00 seconds | The server froze, and its watchdog stopped it. The Minecraft Wiki describes this message. | Look at the lines before it for the plugin, mod or farm that froze it. Do not switch the Watchdog limit off to hide it. See How to reduce lag on your Minecraft server |
For the general checklist, including Kill for a server stuck on Starting, see How to fix a server that will not start.
Players cannot join
| What the player sees | Fix |
|---|---|
| Connection timed out, or cannot reach the server | The server must be Online. Copy the whole Server Address, with the port. See How to join your Minecraft server |
| Outdated client, or outdated server | The game and the server versions differ. The same article explains both messages. |
| You are not white-listed, or you are banned | See How to set up a whitelist and ban players |
| Invalid session, or failed to verify username | The player restarts the game and the launcher, and signs in again |
| The server is full | Your plan sets the player slots. See How to rename your server and change player slots |
| Missing or incompatible mods | The player needs the same loader, version and mods. See How to install mods on Forge, Fabric and NeoForge |
| A Bedrock player cannot join a Java server | See How to let Bedrock players join your Java server with Geyser |
