Common Minecraft Errors and How to Fix Them

❌ 1. OutOfMemoryError: Java heap space

What it means: The server ran out of RAM.
Solution: Upgrade your plan or, if you already have plenty of RAM, check for memory leaks in plugins. Review the console to see which plugin or process was active just before the crash. You can also use optimization plugins like Spark to identify the problem.

⚠️ 2. Can't keep up! Low TPS

What it means: The server processes the game slower than normal (it should run at 20 TPS; below 15, players notice lag).
Solution:

• Install the Spark plugin and run /spark profiler to see what's consuming the most.
• Reduce the view distance in server.properties: view-distance=6.
• Disable or configure heavy plugins (real-time maps like Dynmap, very large farms).
• Limit the number of mobs with plugins like MobLimiter.

🔴 3. Failed to bind port

What it means: The server can't open the port because it's already in use.
Solution: Restart the server from the panel. If the error persists, open a technical support ticket — we manage port allocation on our side.

🌐 4. Connection timed out

What it means: The player can't connect to the server.
Solution:

• Check you're using the correct address and port (you can see them in the panel).
• Make sure the server is on in the panel (green status).
• If you use a custom domain, it can take up to 48h to propagate.

🔐 5. Invalid session (Please try again)

What it means: Mojang's authentication servers didn't verify your account.
Solution: Restart the server. If the error persists for multiple players, it may be a temporary outage of Mojang's servers — check status.mojang.com. To bypass this on private servers you can set online-mode=false in server.properties, but beware: this lets anyone join with any username.

⚡ 6. The server crashes when installing a plugin

Solution: Go to the panel → Files → /plugins folder → rename the plugin's .jar to plugin.jar.disabled. Restart the server. If it starts, that plugin was the culprit. Read the console (Crash Reports tab or the latest logs) to see the exact error.