How to Update a Rust Server Safely
Rust forces frequent updates, and most update problems come from Oxide/uMod lagging behind the new binary, not Rust itself. Here's the safe sequence.
Start with a restore point
Back up your map and save files before the forced update window — Rust updates weekly, typically Thursdays.
Update in the right order
- Update RustDedicated via SteamCMD first.
- Wait for an Oxide/uMod compatibility release before re-enabling plugins — running old Oxide against the new binary is the most common post-update crash.
- Re-test any custom plugins individually once Oxide catches up, since plugin APIs can also shift.
Verify before you reopen the server
Confirm the server reaches a stable, playable state and RCON responds before announcing it's back.
FAQ
Why does my server break every Thursday?+
Rust's weekly forced update often lands before Oxide/uMod's compatible rebuild — that's the gap where plugin-heavy servers break.
Should I update Oxide and Rust at the same time?+
Update Rust first via SteamCMD, then wait specifically for the Oxide team's compatibility release before re-enabling plugins.
What should I back up before an update?+
Your map and save files at minimum; plugin configs too if you've customized them heavily.
Run Rust updates without the Thursday scramble
CoalHost waits for confirmed Oxide/uMod compatibility before auto-updating plugin-heavy Rust servers.
View Rust Hosting →