Roast my server: free Minecraft crash log analyzer
Paste a Minecraft crash log, mclo.gs link or spark profile. Roastd names what broke, which mod caused it, and the exact fix. Free, no account.
Your logs get stripped of addresses, tokens and passwords before anything is saved. Raw pastes are deleted on a timer. The shared report never contains them.
What Roastd checks in a Minecraft crash report
Roastd runs your paste through a hundred-signature library built from the one we use on our own fleet.
Crashes. Out of memory in every flavour, including the exit code 137 kill. Java version mismatches, down to the release you need. Mixin and mod conflicts, with the mod named from the stack trace. Dependency failures, missing registries, corrupt worlds, full disks, port clashes, watchdog stalls.
Plugins and proxies. Unknown dependencies, wrong API versions, async abuse. BungeeCord and Velocity forwarding, Geyser and Floodgate setup, ViaVersion breakage.
Config. Add server.properties, your mod list and specs and it checks RAM headroom, view and simulation distance, spawn protection, watchdog settings, client-only mods and duplicates.
It knows what it's reading. Paper, Forge, NeoForge, Fabric, proxy and client logs each get the right checks. When one fault caused another it says so instead of listing symptoms. If nothing matches, it tells you rather than guessing.
Every Minecraft server error Roastd knows
135 findings, each with the exact line it matches, what causes it and how to fix it. Recognise yours? Open the page. Not sure? Paste the whole log above and let Roastd pick.
Start-up and world
- A mod is for a different Minecraft version
- A mod is incompatible
- A mod is missing a dependency
- Datapacks stopped the world from loading
- Duplicate mods in the pack
- Not enough RAM to start
- That file is not a runnable server
- The disk is full
- The Minecraft EULA has not been accepted
- The server port is already in use
- The world could not be opened
- The world references mods that are no longer installed
Memory
Java version
Java runtime
Launch and install
Modpack install
Mods
Mod conflicts
Mod dependencies
Mod data
Mixin noise
Pack recipes
Plugin loading
- A file in the plugins folder is not a plugin
- A plugin failed to load
- A plugin is missing another plugin it depends on
- A plugin is still scheduling work after being disabled
- A plugin needs a newer Java than the server runs
- A plugin was built for a newer server version
- An ancient plugin is running in legacy mode
- Two copies of the same plugin are installed
- Wrong file for this server type
Plugin crashes
Plugin compatibility
Plugin config
World data
World generation
Restarts
Shutdown
Authentication
Network protocol
- A login arrived with an impossible username
- Packets are arriving in a shape the server cannot read
- Packets are arriving malformed
- Players time out while logging in
- Reconnecting players are being throttled
- Scattered connection resets are normal
- The network layer was shut down while the server was still running
Proxies
- Geyser and Floodgate are using different keys
- Geyser could not open its Bedrock port
- Geyser is behind the current game version
- Older clients are being turned away
- The backend is not set up for the proxy
- The proxy and backend disagree on forwarding mode
- The proxy is being flooded with connections
- Velocity and the backend do not share the same secret
- ViaVersion failed to translate a packet
Players turned away
- A banned player keeps knocking
- Players are being kicked for flying
- Players are being turned away for not running the server’s mod loader
- Players are being turned away for running a different game version
- Players are bouncing off a full server
- Players are timing out mid-session
- Players have updated past the server
- The same account is logging in twice
- The whitelist is turning players away
Client: graphics
Client: content
Client: connection
Client: interface
Logging
Config files
Why does my Minecraft server keep crashing?
Most repeat crashes come down to one of four things: the heap is too small or sized past the machine's physical RAM, the Java version does not match the Minecraft version, a mod is patching game code that is not there in this build, or a mod is missing a dependency it needs to load. A crash log names which one it is. Paste yours above and Roastd reads the stack trace and tells you which of those you are looking at, and which mod is responsible.
How do I read a Minecraft crash report?
Start at the top. The description line says what the server was doing when it died. The first exception under it is the real fault; everything below is the call stack that led there. Further down, the System Details block gives the Minecraft version, the Java version, the JVM flags and the physical memory, which is where heap and Java mismatches show up. The mod list at the bottom tells you what was loaded. Roastd reads all of that and reports the fault rather than the symptoms.
Analyse a crash log in Discord
Most crash logs get pasted into a support channel long before anyone thinks to open a website. Add the bot and your helpers can diagnose one on the spot: /roast with the file attached, or right-click any message and pick Roast this message.
Run a community? Add the Roastd bot and anyone can roast a crash log right in your support channel: /roast, or right-click a message.
Add the Roastd bot