Minecraft Server Troubleshooting
Fix common Minecraft server issues: connection problems, crashes, lag, plugin errors, mod conflicts, and world corruption.
Minecraft Server Troubleshooting
Having issues with your Minecraft server? This guide covers the most common problems and how to fix them.
Connection Issues
"Can't Connect to Server" / "Connection Refused"
Check in order:
- Is the server running? Check the HostedGG dashboard — status should show "Running"
- Correct address? Copy the server address directly from your dashboard
- Server still starting? Wait 1-2 minutes after a restart for the world to load
- Correct port? If using a non-default port, include it:
server.example.com:25566 - Minecraft version match? Your client version must match the server version
"Outdated Client" / "Outdated Server"
Your Minecraft version doesn't match the server version.
Fix: Change your game version in the Minecraft launcher:
- Open the Minecraft Launcher
- Click Installations → New Installation
- Select the version matching your server
- Play using that installation
"Failed to Verify Username" / "Authentication Error"
This usually means Mojang's authentication servers are temporarily down.
Fix:
- Wait 5-10 minutes and try again
- Check Mojang Status for outages
- Restart your Minecraft client
- If using a cracked client — HostedGG requires legitimate Minecraft accounts
"Connection Timed Out"
Possible causes:
| Cause | Fix |
|---|---|
| Server is overloaded | Restart the server, reduce view distance |
| Your internet is slow | Test with a speed test, try a wired connection |
| Firewall blocking | Unlikely on HostedGG (ports are pre-configured) |
| Server is starting | Wait 2-3 minutes after restart |
"Disconnected: Internal Exception"
This is a generic crash-on-connect error:
- Update your client to the latest Minecraft version
- Remove client-side mods temporarily to test
- Check server console for error messages when you try to connect
- Reset your player data (ask an admin to delete your
.datfile fromworld/playerdata/)
Server Crashes
Server Crashes on Startup
Check the console log for RED text. Common causes:
| Error Message | Cause | Fix |
|---|---|---|
java.lang.OutOfMemoryError | Not enough RAM | Upgrade plan or remove mods/plugins |
Plugin X has been disabled | Plugin error | Update or remove the plugin |
Mod X requires Y | Missing dependency | Install the required mod/library |
Address already in use | Port conflict | Restart the server (clears stale process) |
Failed to bind to port | Port not available | Contact support |
Unsupported class version | Wrong Java version | HostedGG handles this automatically |
Server Crashes During Gameplay
- Check the crash report — found in
crash-reports/folder - Check latest.log — in
logs/folder, scroll to the bottom for the error - Common triggers:
- Entering a corrupted chunk → Delete the region file
- Plugin conflict → Remove recently added plugins
- Out of memory → Check RAM usage and upgrade if needed
Server Crashes After an Update
- Check plugin/mod compatibility with the new Minecraft version
- Update all plugins/mods to versions that support the new MC version
- Roll back if needed — restore from backup and wait for mod updates
Plugin Issues
Plugin Not Loading
- Check the console for error messages mentioning the plugin
- Version compatibility — does the plugin support your MC version?
- Missing dependency — many plugins require Vault, ProtocolLib, or PlaceholderAPI
- Wrong server type — plugins only work on Paper, Spigot, and Purpur (not Vanilla/Forge)
Plugin Causing Lag
Use Spark to identify which plugin is causing performance issues:
- Install Spark plugin
- Run
/spark profiler start - Wait 5-10 minutes
- Run
/spark profiler stop - The report shows which plugins use the most tick time
Common lag-causing scenarios:
- Dynmap during initial render — let it complete, then it's fine
- Chunky while pre-generating — expected, temporary
- Anti-cheat plugins — some are poorly optimized
- Custom enchant plugins — can cause lag with many entities
Plugin Commands Not Working
- Check permissions — use LuckPerms to verify the player has the right permission node
- Check the command exists —
/help <plugin>or/<plugin> help - Restart vs reload — some plugins need a full restart, not just
/reload - Config typo — YAML is sensitive to indentation. A single wrong space breaks configs
"Conflicts" Between Plugins
If two plugins conflict:
- Check both plugins' documentation for known incompatibilities
- If both modify the same mechanic (e.g., two economy plugins), remove one
- Try loading order changes (rename JARs to change alphabetical order)
- Ask in our Discord — we've seen most plugin conflicts before
Mod Issues (Forge/Fabric)
"Mod Requires Forge/Fabric X.X"
The mod expects a specific loader version:
- Update your server's Forge or Fabric version
- Or find a mod version compatible with your current loader
Crash with "Mixin" Errors
Mixin errors are usually mod conflicts:
- Check which mod is mentioned in the error
- Update that mod to the latest version
- If persistent, the mod may be incompatible with another installed mod
- Remove mods one at a time to find the conflict
Client Can't Join Modded Server
- Same mods required — client must have all server-side mods
- Same versions — mod versions must match exactly
- Same Forge/Fabric version — loader versions must match
- Use the same modpack launcher profile as the server uses
World Issues
Corrupted World / Chunks
Symptoms: Invisible blocks, chunks not loading, crash when entering an area
Fix Option 1: Reset corrupted chunks
- Identify the corrupted chunk coordinates from the crash log
- Use a tool like MCA Selector to delete specific chunks
- Upload the repaired region files
Fix Option 2: Restore from backup
- Go to Backups tab
- Choose a backup from before the corruption
- Click Restore
"Level is Too New" Error
Your world was saved in a newer Minecraft version than the server is running:
- Update the server to the newer version
- Or restore a backup from when the version matched
World Too Large / Disk Full
- Set a world border:
/worldborder set 20000 - Delete unused dimensions (Nether/End) if not needed
- Trim chunks outside the border with Chunky
- Upgrade your storage plan
Performance Issues
See our dedicated Performance Optimization Guide for in-depth solutions.
Quick Fixes
- Restart the server — clears memory leaks and entity buildup
- Reduce view distance to 6-8
- Kill excess entities:
/kill @e[type=!player,type=!villager] - Check for error spam in console (broken plugins cause lag)
- Disable the newest plugin/mod you installed
Console Errors
Decoding Common Errors
| Error | Meaning | Action |
|---|---|---|
[WARN] Can't keep up! | TPS dropping below 20 | Optimize server (see Performance guide) |
[ERROR] Plugin X exception | Plugin crashed | Update or remove plugin |
[WARN] Moved too quickly! | Anti-cheat trigger | Normal with high latency players |
[SEVERE] IOException | File read/write error | Restart, check disk space |
[ERROR] Chunk save failed | Disk issue | Check disk usage, contact support |
Reading Crash Reports
Crash reports are saved in crash-reports/. Key sections:
- Description — What happened
- Stacktrace — The technical error (look for mod/plugin names)
- System Details — Java version, RAM usage, plugin/mod list
- Affected Level — Which world/dimension crashed
Emergency Recovery
Complete Server Recovery
- Stop the server
- Create a backup of the current state
- Restore from the last known good backup
- Start the server
- If it works, gradually re-add plugins/mods
Nuclear Option (Clean Install)
If nothing else works:
- Download your world files from File Manager
- Reinstall the server from the dashboard
- Upload your world files back
- Carefully re-add plugins/mods one at a time
- Test after each addition
Still Need Help?
- Discord: discord.gg/xGn3D5drZt
- Support: HostedGG Contact
- Wiki guides: Setup • Performance • Plugins • Mods
Related Articles
Help verify this page
Tested this recently? Send a quick accuracy signal for editors.
Help improve HostedGG
Know this game? Join our community of contributors.
Discussion
Sign in to join the discussion.
Loading discussion...