Minecraft Troubleshooting
“Incompatible version” or outdated server
Section titled ““Incompatible version” or outdated server”The client and server Minecraft versions differ. Select the matching server version or launch the matching client profile. Mod loaders must match too.
Mod loading failed
Section titled “Mod loading failed”Read the first ModLoadingException or dependency message.
- Match Minecraft, loader, and mod versions.
- Install required dependency mods.
- Remove client-only mods from the server.
- Add mods back in small groups if the failing file is unclear.
The server generated a new world
Section titled “The server generated a new world”Check that level-name exactly matches the uploaded world folder. Confirm the folder is not nested, for example world/world/level.dat.
“Failed to verify username” or authentication errors
Section titled ““Failed to verify username” or authentication errors”Keep online-mode=true. Sign out and back into the Minecraft launcher, verify Mojang/Microsoft services are available, and restart the client. Do not disable account verification as a workaround.
Players time out or see Connection refused
Section titled “Players time out or see Connection refused”Wait for Done in the console, use the complete panel address, and confirm the client is Java Edition. Bedrock clients require separately configured compatibility software.
Lag or overloaded warnings
Section titled “Lag or overloaded warnings”- Lower
view-distanceandsimulation-distance. - Remove or profile expensive plugins and mods.
- Reduce excessive entities, hoppers, chunk loaders, and redstone clocks.
- Pre-generate worlds before a large launch.
- Avoid judging performance during startup or world generation.
Crash-loop diagnosis
Section titled “Crash-loop diagnosis”Open the newest file in crash-reports and the end of logs/latest.log. The first exception and its Caused by section are more useful than the final exit code.