MinecraftMinecraft

Why My Minecraft Server Won't Start

Back

Why My Minecraft Server Won't Start

Join the discord

When your server won't start, crashes, or behaves strangely, the latest.log file is the first thing to check.

This guide lists the most common errors and their simple solutions, even if you're a beginner.

Where to find the logs?

From the server panel, create an FTP access, then go to the /minecraft/logs/ folder and download the latest.log file****Crash Reports: If the server crashes, a file is generated in /minecraft/crash-reports/

The latest.log file contains all the useful information for starting the server. It's the key to understanding the errors.

Common Errors and Solutions

1. Wrong version of Forge / Fabric / NeoForge

Log:

Mod File 'examplemod.jar' requires Minecraft 1.20.1 and modloader Forge 47.x

Solution:

  • Check the version selected in the *panel
  • Request on Discord or by ticket if the version is missing

2. Missing dependency

Log:

Mod [examplemod] requires [cloth-config] to be installed.

Solution:

  • Add the required mod in /mods via FTP

3. Server "freeze" - Tick too long / Watchdog

**Log: **[Server Watchdog/FATAL]: A single server tick took 60.00 seconds (should be max 0.05)

Solution:

  • Modify the server.properties file:

max-tick-time=-1

  • This error is related to a server tick being too long, setting the value to -1 disables the server's auto-crash when the tick is too long

  • Check that a factory is not producing too many entities that remain on the ground

  • Check in the crash report that an entity is not responsible for the crash, see the Entity field

4. Incompatible or broken mod

Log:

Exception in thread "main" java.lang.NoClassDefFoundError

Solution:

  • Remove the problematic mod

  • Check version/modloader compatibility

5. Client mod installed on the server

Log:

Mod [xxxxxxx] is marked as client-side only

Solution:

  • Remove from the server's /mods folder

Client mods to avoid on server:

  • OptiFine, Sodium, Iris, BetterF3, ReplayMod, Xaero's Minimap, Inventory HUD, etc.

6. Graphical crash (Blaze3D) - client or server

Client:

Blaze3D error: Invalid framebuffer operation

  • Shader problems or outdated drivers

  • Disable shaders, update drivers

Server:

Exception caught during firing event: net.minecraft.client.gui.screen.Screen

  • A client mod that modifies the interface was put on the server

  • Remove all client-side mods

Quick Tips

  • Search in the log: ERROR, Exception, client, missing, tick took

  • Use https://mclo.gs to share logs

Need help?

You can open a support ticket from the panel or join our Discord for help with the latest.log file