Startup Log Classifier
Paste a Minecraft startup log excerpt to classify Java mismatch, port conflicts, memory errors, plugin failures, dependency issues, and TPS overload.
Classify Startup Logs
Startup logs are noisy, but repeated phrases often point to a small set of causes. Paste a focused excerpt from latest.log or a crash report to choose the next troubleshooting path.
What to Paste
Paste the first error block, not the entire log. Include the Caused by lines and the plugin name if one appears.
Useful excerpts often include:
- The first
Exception. - The first
Caused by. - A plugin name near an error.
- Java version mismatch text.
- Port binding text.
- Memory or heap errors.
What to Do With the Result
Use the classification to pick the next checklist: Java version, port binding, memory, plugin compatibility, or performance profiling.
For startup crashes, continue with the exit code 1 guide. For plugin compatibility, use the plugin version mismatch guide. For lag after startup, use the TPS drops guide.
Privacy Note
The classifier runs in the browser. Still, avoid pasting database passwords, panel tokens, IP allowlists, or private player data into any diagnostic tool unless you have reviewed the text first.
FAQ
Does this upload my log?
No. The classifier runs in your browser and checks the text you paste against local patterns.
Can it replace reading the full log?
No. It is a quick triage tool. The first full exception and surrounding lines still matter.
What part of the log should I paste?
Paste the first error block, including Caused by lines and plugin names. The final shutdown lines are usually less useful.
Related Tools
Plugin Conflict Auditor
Paste a Minecraft plugin list to flag common dependency, compatibility, ProtocolLib, LuckPerms, ViaVersion, and proxy risk areas.
Minecraft JVM Flag Generator
Generate practical Minecraft server JVM flags for Paper, Purpur, Forge, Fabric, and Velocity with sensible heap sizing and GC reminders.
Console Error Explainer
Paste Minecraft console errors to identify likely Java, YAML, plugin dependency, port binding, memory, database, watchdog, and EULA problems.
Related Articles
Fix Minecraft Server Exit Code 1
Troubleshoot Minecraft server exit code 1 by reading the first exception, checking Java, plugin versions, startup flags, configs, and host panels.
How to Fix Can't Keep Up Is the Server Overloaded
Fix Minecraft Can't Keep Up server overloaded warnings by checking TPS, MSPT, Spark profiles, chunks, entities, plugins, world saves, and hosting limits.
Minecraft Server Keeps Disconnecting Players
Troubleshoot a Minecraft server that keeps disconnecting players by checking network drops, proxies, timeouts, plugins, server load, and client errors.