Safe Minecraft Server Version Update on GlassHosting

Why version updates break communities

A Minecraft version bump looks like a single jar swap. In practice it is a coordinated change across world format, server software (Vanilla, Paper, Spigot), and every plugin or mod that expects a specific API. Communities break when one piece moves and the others do not: a Paper build that no longer loads yesterday’s economy plugin, a world that converted silently and cannot go back, or a Forge/Fabric loader that refuses the new game jar.

On GlassHosting (Glass Gaming — powered by GlassHosting), updates are deliberate: named backup first, inventory what you run, stop cleanly, change only what the target version requires, then smoke-test before you invite the whole SMP back in. Treat the update like a change window, not a click-and-hope.

Named panel backup before anything

Open your Minecraft service in panel.glasshosting.com and create a named backup before you touch jars, plugins, or configs. Name it with the current version and intent—for example pre-1.21.4-to-1.21.5—so rollback is obvious under stress.

Do not rely on “there is probably an auto backup somewhere.” A named restore point is the difference between a ten-minute recovery and a griefed world folder. Related: backups before mods.

Inventory: know what you are leaving

Write down (ticket note, Discord pin, or a simple text file) the current state:

Game version shown in console on boot or in the panel software selector.
Server software: Vanilla, Paper, Spigot, or a modded stack (Forge / Fabric / NeoForge).
Plugin list for Paper/Spigot—especially economy, permissions, and world-protection plugins that pin to Minecraft API versions.
Mod list and loader version if you are modded; client and server must agree after the bump.
World names and whether you use multiple dimensions or custom world folders.

If you are choosing Paper vs Spigot for the new line, see Paper vs Spigot vs Vanilla. For file moves, keep SFTP mods and plugins handy.

Stop cleanly — do not update while running

Stop the server from the panel and wait until the process is fully down. Updating jars or plugins while Minecraft is writing chunks risks half-written worlds and corrupted plugin data. A clean stop is part of the change, not optional polish.

If players are online, give a short console notice and stop at a quiet moment. Do not yank power mid-autosave.

Update path: jar/build first, world stays

Replace the server jar or select the new Paper/build in the panel for the target Minecraft version. Prefer official Paper builds for the exact game version you want.
Leave server.properties, world folders, and whitelist/ops files alone unless the new version documents a required change.
Bump plugins only when required for the new Minecraft version. Prefer upstream releases that explicitly list your target game version. Do not mass-update every jar “while you are in there.”
For modded servers, update the loader and mods as a matched set—never the game jar alone.
Upload via the panel file manager or SFTP; confirm filenames and that old jars are removed or renamed so the wrong build cannot load.

Keep the world. Version upgrades should not require deleting world, world_nether, or world_the_end. If someone tells you to wipe the world to “fix” a failed start, restore the named backup instead.

Start, watch console, smoke-test

Start the server and watch the console for the full boot. Note any plugin that fails to enable, version mismatch warnings, or world conversion messages.
Join with a trusted account. Walk spawn, open inventories that matter (shops, claims), and run a quick OP check if you use operators—see make yourself OP.
Check TPS and error spam after a few minutes of normal activity. Related: fix low TPS.
Only then reopen the server to the wider community.

If boot fails or critical plugins will not load, stop again and roll back—do not keep restarting hoping the world will heal.

Rollback without wiping the world

Restore the named panel backup you took before the change. Confirm the restore completed, start the server, and verify you are back on the previous version and plugin set.

Do not delete world folders in panic. Do not mix a new jar with an old world that already converted forward without a restore plan. If you uploaded a custom world recently, keep that workflow separate: upload your Minecraft world.

After a successful rollback, schedule a quieter window, fix the mismatched plugins or choose a nearer target version, and try again with a fresh named backup.

Related guides

MSP note

GlassHosting keeps Minecraft always-on in a datacenter so version work is panel, files, and console—not fighting home CGNAT mid-update. Plan the bump, name the backup, change one layer at a time, and restore when load fails. Order or manage plans at billing.glasshosting.com; run the server day-to-day at panel.glasshosting.com.