How to Find and Share Your Minecraft Server Logs
Locate, read, and share Minecraft Java server logs via the panel Console, the logs folder, and mclo.gs for support tickets.
Server logs are the first place to look for any problem on a Minecraft server — startup errors, plugin crashes, player events, and warnings all live there. This guide shows you where to find them, how to read them, and how to share them properly when asking for help.
Where Logs Live
| File | Contains |
|---|---|
logs/latest.log | Current session's full log |
logs/YYYY-MM-DD-N.log.gz | Compressed previous sessions, numbered per day |
crash-reports/ | Detailed crash dumps (only created when the server actually crashes) |
View the Live Log
For real-time output, use the XGamingServer Panel Console in the sidebar — it streams the log as the server runs. This is the same content as latest.log, just live.
Download an Old Log
Open Files
Click Files in the panel sidebar.
Navigate to logs/
Open the logs/ folder.
Download the relevant log
- For the current session: download
latest.log - For an older session: download the
.log.gzfile matching the date
Decompress (.log.gz files)
.log.gz is gzip-compressed. Open it with:
- Windows: 7-Zip, WinRAR, or PeaZip
- Mac: double-click in Finder
- Linux:
gunzip filename.log.gz
Share Logs with mclo.gs
When asking for help in support or Discord, never paste 5,000 lines of log into chat. Use mclo.gs, the standard Minecraft log paste service.
Copy the log content
Open latest.log and copy the entire contents (or the relevant section if you can identify it).
Paste into mclo.gs
Go to mclo.gs, paste the log into the text area, and click Save.
Share the link
Copy the resulting URL (e.g., https://mclo.gs/abc1234) and paste it in support chat or our Discord.
mclo.gs automatically analyzes common errors and highlights them in the Analysis tab — sometimes it catches the issue before you even share the link.
What to Look For in a Log
| Pattern | Meaning | Severity |
|---|---|---|
[INFO] | Normal informational message | None |
[WARN] | Potential issue, server still running | Low–Medium |
[ERROR] / [SEVERE] | Something failed | High |
Exception in thread | Java exception (read the next ~20 lines) | High |
Caused by: | Root cause of a stack trace — always check this | Critical |
Could not load | Plugin/mod failed to load | High |
Disabling plugin | Plugin was unloaded due to error | High |
OutOfMemoryError | Ran out of RAM | Critical |
Watchdog Thread | Server hung — restart required | Critical |
Done (X.XXXs)! | Server finished starting successfully | None |
Read the FIRST error, not the last. Later errors in a log are usually side effects of the first one. Start at the top of the failure and work down.
Filter the Noise
latest.log can be thousands of lines. To narrow down:
- Look for
[ERROR]or[SEVERE]— Ctrl+F in any text editor - Find
Caused by:— that's the actual root cause - Identify the timestamp of when the issue started
- Cross-reference with player reports — match player chat lines to the time of the issue
Common Mistakes
| Mistake | Fix |
|---|---|
| Pasting raw log into Discord | Use mclo.gs — Discord truncates long messages |
| Sharing only the last 10 lines | Share the full log so the first error is visible |
Ignoring .log.gz files | They contain the same useful info — decompress to read |
| Reading only Console without saving | Console scrolls away. Download latest.log for permanent reference |
| Sharing logs that don't include the issue | Verify the timestamps match your problem before sharing |
Related Guides
How is this guide?
How to Find and Read Minecraft Server Crash Reports
Locate Minecraft Java server crash reports, decode the stack trace, identify the offending plugin or mod, and share the report for help.
How to Fix 'Connection Refused' on Your Minecraft Server
Diagnose and fix Connection Refused errors on your Minecraft Java server — server offline, wrong port, crashed at startup, or full.