Troubleshoot a Server That Will Not Start

When a Minecraft server will not start, find the first useful console error and undo the most recent change. World uploads, add-ons, configuration edits, version changes, and an unaccepted EULA are common causes.

Find the First Useful Error

1. Open the console — Log in to the NolimitHost Game Panel at https://panel.nolimithost.cc/, select your Minecraft server, and open the Console tab.
2. Start the server once — Read the output from the start of that attempt. The last line may only report that the process stopped; the useful error often appears several lines earlier.
3. Copy the error before changing anything — Remove passwords, tokens, private addresses, and player information before sharing it.

Undo the Latest Change

Check the section that matches what changed immediately before the failure:

The EULA has not been accepted

Open the server in the NolimitHost Game Panel and accept the EULA if prompted. Start the server again and watch the console until startup completes.

You uploaded a world

Confirm that the world folder directly contains level.dat and that the configured world name exactly matches the folder. Restore the previous world when the uploaded world is damaged or incompatible. See the Upload a Java World guide.

You installed or updated an add-on

Restore the backup made before installation. Then verify the packs, dependencies, experiments, and versions are compatible with your server before trying again.

You installed or updated a plugin

Leave the server stopped and follow the Troubleshoot Java Plugin Errors guide. Check the first named plugin, its dependencies, and compatibility.

You changed mods or the mod loader

Compare the Minecraft version, loader family, loader version, mods, and dependencies. Follow the Troubleshoot Java Mod-Loader Mismatches guide.

You edited a configuration file

Restore the last known working file. Check the edited value's spelling, allowed format, and quotation marks before applying the change again.

You changed the server version

Restore a backup created before the version change. Confirm that the world and add-ons support the target version before trying again.

Nothing changed

Check the NolimitHost service status page, your server's disk usage and backups, and resource usage, then retry one normal start. Avoid repeated restart loops because they can overwrite useful logs.

Restore Service Safely

1. Stop automatic restarts — Leave the server stopped while you inspect files and logs.
2. Preserve evidence — Save the relevant console output and note the exact time of the failed start.
3. Restore the last working state — Restore a known-good backup or reverse only the latest change.
4. Start once and test — Watch the complete startup. When the server remains running, join it and verify the affected feature.

Information to Send Support

Send the server name or account-visible server ID, the failure time and time zone, the complete relevant console error, and the last change made. Never send your account password.