How to Read Your Server Console and Identify Errors

Why the Console Matters

The server console is the most important diagnostic tool you have. When something goes wrong, the console tells you exactly what happened. Learning to read it saves time and often lets you fix issues without contacting support.

Where to Find the Console

Log into your game panel, select your server, and go to the Console tab. The console shows live server output.

Normal Startup Messages

When a server starts normally, you will see messages like:

• Loading configuration files
• Loading world or map data
• Loading plugins or mods
• A "Done" or "Ready" message when the server is fully started

If the server stops outputting text before showing a ready message, something went wrong.

How to Identify Errors

Look for these keywords in the console output:

• ERROR or FATAL — Something broke. Read the message after it
• Exception or Traceback — A code error. The first line usually tells you the cause
• OutOfMemoryError — Server ran out of RAM
• Failed to bind — Port conflict
• Could not find or File not found — A required file is missing
• A mod or plugin name followed by an error — That specific mod/plugin is the problem

What to Do When You See an Error

1. Copy the full error message — select the relevant lines from the console
2. Search for the error — paste the key part into Google or the game community forums. Most errors have known solutions
3. Check recent changes — did you add a mod, change a setting, or update something? That is likely the cause
4. Contact support — if you cannot resolve it, open a ticket and include the full error text. This helps us diagnose the issue much faster than a description of the symptoms

Important: Do Not Restart Blindly

If your server crashes, read the console before restarting. Restarting clears the console output and you lose the error message. Copy it first, then restart.