Skip to content

Reinstalling

Reinstalling replaces your server files with a fresh copy from its template. Use it when an installation is damaged beyond easy repair — corrupted jars, mangled configs after a bad edit, or a version jump you would rather do cleanly.

  1. Create a backup and wait for it to finish.
  2. Download anything the backup might not cover that you care about (or verify the backup completed — do not skip this).
  3. Tell your players: the server will be offline and the world may reset.

You need the server.reinstall permission (the server owner has it by default).

  1. Stop the server. Reinstall stays disabled while the server is running.
  2. Open the server’s Settings tab and find the Maintenance row.
  3. Select Reinstall.
  4. Confirm the Reinstall server? dialog — it warns that every file in the server directory is deleted. Select Reinstall to proceed.
  5. Watch the install output in the console until it finishes.
  6. Start the server again with power controls. A Minecraft server shows a Minecraft EULA dialog on the next start — scroll to the bottom and select I Agree to let it boot, or Decline to stop it.
  7. Re-apply anything the template install does not restore (configs, plugins, and so on).

A server stuck in the installing state shows a Cancel install button next to Reinstall. It kills the stuck installer and resets the server to stopped so you can try again; partial install files are kept.

  • One broken config? Revert that file instead of wiping everything.
  • Boot loop after a variable change? Revert the variable (startup).
  • Install script out of date but files fine? The Admin tab’s Container section has Rebuild (needs server.rebuild): it re-runs the install command and keeps existing files instead of deleting them. Administrators reinstall from the same section.
  • Just want a second server with the same setup? Clone it instead of starting from scratch — a configuration clone installs fresh, a full clone copies the world too.