Minecraft Log & Crash Analyzer
Analyze Minecraft server logs and crash reports. Identify errors, get solutions, and fix issues fast.
Paste Log or Crash Report
Tips
- •Find logs in your server's
logs/folder - •Crash reports are in
crash-reports/ - •For large logs, paste only the section with errors to avoid memory issues
- •Works with vanilla, Forge, Fabric, Paper, and Spigot servers
Analysis Results
Paste a log or crash report and click "Analyze Log" to see results
Why Use Our Log Analyzer?
100% Private
Analysis runs entirely in your browser using WebAssembly. Your server logs never leave your device.
Instant Results
No upload or processing time. Get instant error detection and solutions in milliseconds.
Smart Solutions
Get actionable solutions for common Minecraft errors, mod conflicts, and configuration issues.
Need Help With Your Server?
Get managed Minecraft hosting with 24/7 support. We'll help you troubleshoot issues and keep your server running smoothly.
Understanding Minecraft Server Logs and Crash Reports
Server Logs (latest.log)
Server logs record everything that happens on your Minecraft server. They include player connections, chat messages, commands, errors, and warnings. When troubleshooting, always check the latest.log file first. Look for lines marked [WARN] or [ERROR] as these indicate potential issues.
Common Log Locations:
- • Vanilla/Paper/Spigot:
logs/latest.log - • Forge:
logs/latest.logorlogs/debug.log - • Fabric:
logs/latest.log
Crash Reports
Crash reports are generated when the server encounters a fatal error. They contain detailed information about what caused the crash, including the Java stack trace, system details, and the state of the game at the time of the crash.
Crash Report Sections:
- • Description: Brief summary of the crash
- • Stack Trace: Detailed error location
- • System Details: Java version, OS, memory
- • Affected Level: World information at crash time
Frequently Asked Questions
Is my log data safe?
Yes! All analysis happens locally in your browser using WebAssembly. Your logs are never uploaded to any server.
What types of logs are supported?
We support vanilla Minecraft, Forge, Fabric, Paper, Spigot, and BungeeCord logs. Both server logs and crash reports are analyzed.
Why wasn't my error detected?
The analyzer matches against known error patterns. If your error is new or uncommon, it may not be in the database. Try searching the error message online.
Can I analyze client-side crashes?
Yes! The analyzer works with both client and server crash reports. Client crash reports are typically found in the .minecraft folder.
Common Minecraft Server Errors and How to Fix Them
java.lang.OutOfMemoryError
Your server ran out of allocated RAM. This is one of the most common Minecraft server errors.
Fix: Increase memory allocation in your startup script using -Xmx and -Xms flags, or reduce view distance and entity limits.
NoClassDefFoundError
A required class file is missing. Usually caused by incompatible mod or plugin versions.
Fix: Update all mods/plugins to versions compatible with your Minecraft and server software version.
UnknownDependencyException
A plugin requires another plugin that isn't installed on your server.
Fix: Install the required dependency plugin. Common dependencies include Vault, ProtocolLib, and PlaceholderAPI.
SocketException: Address already in use
Another process is using the port your server is trying to use.
Fix: Stop the other process using that port, or change your server port in server.properties.
InvalidPluginException
The plugin JAR file is corrupted or built for a different server version.
Fix: Re-download the plugin from a trusted source. Ensure it's compatible with your server software (Spigot, Paper, etc.).
ConcurrentModificationException
A plugin is modifying a collection while it's being iterated. This is a plugin bug.
Fix: Update the problematic plugin or report the bug to the developer. Check the stack trace to identify which plugin is causing it.
Analyzing Logs by Server Type
Forge Server Logs
Forge logs contain mod loading information, including which mods loaded successfully and which failed. Look for [FML] or [Forge] prefixes to identify Forge-specific messages. Common issues include mod version mismatches and missing dependencies.
- • Crash reports:
crash-reports/crash-*.txt - • Debug log:
logs/debug.log - • Mod loading errors: Check for "Failed to load mod" messages
Fabric Server Logs
Fabric uses a lightweight mod loader with detailed error messages. Mixin errors are common when mods conflict. Look for [Fabric] or[Mixin] prefixes in the logs.
- • Mixin errors: Usually indicate mod conflicts
- • Missing entrypoint: Mod isn't properly configured
- • Fabric API: Many mods require Fabric API as a dependency
Paper/Spigot Server Logs
Paper and Spigot servers run Bukkit plugins. Plugin errors usually show which plugin caused the issue. Look for [PluginName] prefixes to identify the source.
- • Plugin enable errors: Check plugin dependencies
- • Command errors: Usually show which plugin's command failed
- • Timings report: Use
/timings reportfor performance issues
Vanilla Server Logs
Vanilla Minecraft server logs are simpler but still contain valuable debugging information. World corruption and chunk loading errors are common issues.
- • World errors: Check for chunk corruption messages
- • Connection issues: Look for "disconnected" messages
- • Performance: Watch for "Can't keep up!" warnings
How to Use the Minecraft Log & Crash Analyzer
Find Your Log
Locate your server's logs/latest.log or crash report file
Paste or Upload
Copy the log contents and paste them, or use the upload button to select the file
Analyze
Click "Analyze Log" to scan for Java exceptions, errors, and warnings
Fix Issues
Review detected errors, expand stack traces, and follow the suggested solutions