Find the first useful error
Open the Purpify console and 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. Copy the error before changing anything. Remove passwords, tokens, private addresses, and player information before sharing it.Undo the latest change
Use the branch that matches what changed immediately before the failure:The EULA has not been accepted
The EULA has not been accepted
Open the server in the Purpify panel and select Accept EULA. Start the server again and watch the console until startup completes.
You uploaded a world
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.You installed or updated an add-on
You installed or updated an add-on
Restore the backup made before installation. Then follow Troubleshoot Bedrock add-on errors to verify packs, dependencies, experiments, and versions.
You installed or updated a plugin
You installed or updated a plugin
Leave the server stopped and follow Troubleshoot Java plugin errors. Check the first named plugin, its dependencies, and compatibility.
You changed mods or the mod loader
You changed mods or the mod loader
Compare the Minecraft version, loader family, loader version, mods, and dependencies. Follow Troubleshoot Java mod-loader mismatches.
You edited a configuration file
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
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
Nothing changed
Check the Purpify service status, disk usage, 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.