Skip to content
Clodo

Reading Minecraft Logs and Common Server Errors

A guide to analyzing server console and logs/latest.log output, understanding stack traces, and fixing common server errors.

Intermediate7 minUpdated:26 October 2026

In brief

  • Monitor active output in the console or inspect historical records in the logs/latest.log file via the file manager.
  • Read stack traces top-down to identify the root exception and the responsible plugin.
  • Resolve errors such as OutOfMemoryError, port binding conflicts, and Java version mismatches using correct configurations.

What you need

  • Access to the console and file manager in the panel
  • Log records in the logs/latest.log or crash-reports directory
On this page
On this page
Minecraft & Game Servers guides

Accessing the Console and latest.log#

You can monitor all runtime server events live via the console tab in the panel. If the server crashes or restarts, the console screen history might be cleared. To view full historical records, navigate to the file manager in the panel, open the 'logs' folder, and inspect the 'latest.log' file.

Reading Stack Traces Top-Down#

When a Java exception occurs, the log records a multi-line stack trace. Start reading the stack trace from the very top. The first line indicates the exception type (such as NullPointerException or ClassNotFoundException). Further down, lines starting with 'Caused by:' reveal the root cause and identify the specific plugin package triggering the error.

latest.log
[14:22:05 ERROR]: Error occurred while enabling ExamplePlugin v1.0.0
java.lang.NoClassDefFoundError: net/milkbowl/vault/economy/Economy
    at com.example.plugin.Main.onEnable(Main.java:42) ~[ExamplePlugin.jar:?]
    at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:264) ~[paper-1.21.jar:?]
Caused by: java.lang.ClassNotFoundException: net.milkbowl.vault.economy.Economy
    ... 15 more

Common Server Errors and Solutions#

  • java.lang.OutOfMemoryError: Indicates that the server has exhausted its allocated RAM limit. Remove leaking plugins, lower the view-distance, or restrict entity counts.
  • Failed to bind to port: Occurs when the assigned port is already occupied or the server attempts to bind to an unauthorized address. Ensure previous server processes are stopped and verify that the server-port matches the assigned panel port.
  • Can't keep up: Indicates that the server tick duration exceeded 50 ms and ticks were skipped. Overcrowded mob farms, intensive redstone clocks, or heavy plugins are typical causes.
  • Could not load 'plugins/...jar' in folder 'plugins': Means the plugin jar file is corrupted, missing a required dependency plugin, or incompatible with the current server API version.
  • UnsupportedClassVersionError: Indicates that the plugin or server jar was compiled with a newer Java version than the active runtime (e.g. attempting to run a Java 21 plugin on Java 17).

What to Attach When Opening a Support Ticket#

If the issue cannot be resolved through these steps or hardware malfunction is suspected, you can submit a support ticket. To expedite investigation, attach the logs/latest.log file from the file manager and any recent crash report (crash-*.txt) found in the crash-reports folder. Additionally, describe what action directly preceded the error, such as installing a new plugin or importing a world.

Was this guide helpful?

Feedback goes straight to the team that maintains this guide.

Could not find a solution?

You can open a request with our support team from the panel.

Open a support request
All guides in this topic →