How to reinstall your server without losing your data
A reinstall is the reset button: it puts the server back to a clean starting state. It fixes tangled configurations and corrupted game files, and it is also the easiest way to lose a world you have spent months on. The difference between a smooth reset and a disaster is preparation. This guide shows what a reinstall typically does, how to protect your data first and how to restore things in the right order.
What a reinstall usually does
Details depend on your panel and the game, so read the confirmation text before you agree. In general, a reinstall:
- Re-downloads or restores the base game server files.
- May overwrite files in the server folder, and in some setups removes everything.
- Can reset configuration files to defaults.
- Usually leaves your account, plan and address unchanged.
Treat any reinstall as something that may delete everything in the server folder, unless the panel clearly says otherwise. Plan as if it will.
When a reinstall is the right tool
- The server is stuck in a crash loop after a bad update, and rolling back did not work.
- Game files are corrupted, and verifying them does not help.
- You want to start a different game or a different server type on the same plan.
- You want a fresh world and settings.
When it is not
- A single plugin or mod is the problem: remove it instead. See Mod hygiene for game servers.
- A configuration mistake: restore the file from backup. See Edit config files without breaking them.
- A world corruption: follow How to repair a corrupted Minecraft world.
- Lag: reinstalling will not make a slow server fast. See How to fix server lag.
Reinstalling is a heavy hammer, so make sure the problem really needs it.
Step 1: stop the server
Stop it cleanly from the panel so the world is saved to disk. See Start, stop and restart your server.
Step 2: back up everything that matters
Decide what you cannot afford to lose. For a Minecraft server, that is usually:
| Item | Where |
|---|---|
| World folders | world, world_nether, world_the_end, or your custom names |
| Plugin data and settings | plugins folder |
| Mod configs | config folder |
| Whitelist, ops, bans | whitelist.json, ops.json, banned-players.json |
| Server settings | server.properties |
| Player data and stats | inside the world folders |
Use the panel's backup tool, then download a copy to your own computer. A backup stored only on the server may be removed by the reinstall. See Creating and restoring backups and The 3-2-1 backup rule. For large folders, compress first. See How to compress and extract files.
Step 3: write down your settings
Note your game version, server type, Java version, startup settings and any custom flags. After a reinstall you may need to enter them again. What the startup settings on a game server do explains the fields.
Step 4: check the backup before you continue
Open the downloaded archive and look inside. Confirm the world folders are there, and check the size is sensible. A backup you cannot open is no backup. Do not skip this step.
Step 5: reinstall
Read the panel's warning, then confirm. Wait for the process to finish, and look at the console for progress. If you are changing the game or version at the same time, change one thing at once where you can, so you can find the cause if problems return.
Step 6: restore in a careful order
- Start the fresh server once and let it generate default files. Then stop it.
- Check the version and Java match what you need. See Fix Java version errors.
- Upload the world to the correct folder. See Upload a Minecraft world.
- Restore settings one file at a time, such as
server.properties. Do not simply paste all old configs over new defaults if the version changed, because formats can differ. - Add plugins and mods back gradually, not all at once. Start the server after each batch and read the console. This isolates any plugin that caused the original problem.
- Restore permissions, whitelist and bans.
- Start the server and test by joining yourself before announcing it.
Common mistakes
- Reinstalling before downloading a backup. The most expensive mistake.
- Copying old config files from a different version and breaking the new install.
- Putting the world in a nested folder so the server generates a new world instead of loading yours.
- Forgetting the world name in
server.properties(level-name), which must match the folder. - Restoring everything at once, bringing the original fault straight back.
- Not telling your players about downtime.
If something goes wrong
If the world does not load, check the console for the first error, and confirm the folder name and structure. If data is missing and you did not keep a copy, contact support quickly, and avoid making more changes. Include your Server ID, the time of the reinstall and what you did. How to write a support request lists what to send.
After the reinstall
Set up automatic backups again and test a restore, so you are not exposed in the same way next time. See Schedule automatic restarts and backups.
Still stuck? Open a ticket on Discord - run /ticket in any channel, pick a department, and include your Server ID or Invoice ID so we can jump straight in.