Updating Your Minecraft Server
Update your server to the latest Minecraft version safely and without losing your world.
By Lodgichost Team · Last updated: August 19, 2026
Updating your Minecraft server keeps your world compatible with the newest features, bug fixes, and security patches — but it is also the most common moment for things to go wrong. The good news is that with a simple pre-update routine, updates are nearly always painless. This guide walks you through how version types differ, how to update safely through the Lodgichost portal, and exactly what to check afterwards. From our own roll outs, the two steps that save the most pain are a verified backup taken minutes before the update and a fresh test of plugin/mod compatibility before telling your community the update is live — a backup you cannot restore is not a backup.
Understand the Version You're Jumping To
Not all Minecraft releases are the same. Knowing which kind of release you are installing tells you how carefully to prepare:
- Full releases (e.g. 1.21): Stable versions that most plugins and mods target. Safe to install with a backup.
- Pre-releases and release candidates: Test versions shipped shortly before a full launch. Mechanics are mostly final, but some plugins may not have caught up yet.
- Snapshots: Weekly experimental builds with brand-new content and frequent breaking changes. Not appropriate for a production server you care about.
- Modded vs vanilla: Mod loaders (Fabric/Forge/NeoForge) and servers like Paper ship their own builds. Always update to a build that matches both the Minecraft version and your server software, not just the game version.
Before You Update
Always create a full backup before updating your server version. Navigate to the Backups section in your portal and create a manual backup of your world and settings. This ensures you can roll back if the update causes any issues.
A genuinely useful backup is one you have verified. In our testing we restore-test every manual backup before an update: you can check the backup is non-empty and, if in doubt, download it and confirm your world folder is inside. Do this before the update, not after — the whole point is that the restore path is already proven the moment something breaks.
Updating Through the Portal
In the Lodgichost portal, navigate to your server settings and click "Change Version". Select the new Minecraft version from the dropdown and confirm. The system will automatically download the new server jar and migrate your world files. Your server will restart with the updated version.
Because the portal handles the jar swap and world files for you, the main thing you control is timing. From our experience, updating in a low-traffic window and announcing a brief maintenance window avoids players hitting a server that is mid-restart. The actual restart after a version change typically takes one to three minutes, so a single short announcement before you click is enough for most communities.
Post-Update Checklist
- Verify that your server starts successfully and loads your world.
- Check that all plugins and mods are compatible with the new version.
- Test core gameplay mechanics like block breaking, inventory, and mob spawning.
- Update any server-side resource packs to match the new version.
- Notify your players about the update and any changes to the gameplay experience.
Rolling Back
If something goes wrong, restore your server from the backup you created before the update. Go to the Backups section in the portal, select your pre-update backup, and click Restore. Your server will be reverted to its previous state.
Troubleshooting
- Server fails to start after update: Check server logs for version incompatibility.
- Plugins not working: Update all plugins to versions compatible with the new Minecraft release.
- World corruption: Restore from your backup and try the update again with fresh world files.
Frequently Asked Questions
Will updating lose my world?
No. World files are forward-compatible; un-generated chunks simply generate with the new version's features. As long as you back up before the update, your build is safe.
How long does a version change take through the portal?
A version change downloads the new server jar and restarts your server, which usually takes between one and three minutes depending on the size of your world.
My plugins broke after updating. What now?
Check the plugins folder in-game with /plugins. Update each plugin to a build that supports the new version, then restart. If a plugin has no compatible build yet, remove it until it does.
Should I update on the release day?
For vanilla servers with few plugins, release-day updates are usually fine. For modded or heavily plugin-loaded servers, wait one to two weeks for loaders and plugins to release compatible builds.
What if the new version has a game-breaking bug?
You are not forced to stay on the newest version. If a release has issues that affect your players, roll back from your backup and wait for the next patch.
Upgrade Paths
- Minor version (e.g., 1.20 → 1.21): Usually safe with most plugins and worlds.
- Major version (e.g., 1.19 → 1.20): Test thoroughly on a copy before updating your live server.
- Snapshot/Pre-release: Not recommended for production servers — use a separate test server.
Related Guides
- Automated Backups and Restores — back up before every update
- Server Properties Guide — configure version-specific settings
- Installing and Managing Plugins — update plugins after updating