Rust server troubleshooting: crashes, wipes, plugin breakage

Walk through the common Rust server faults: long first boot, Oxide lagging a Rust patch, plugin breakage, wipe day lag, and players who cannot connect.

Rust server troubleshooting usually breaks down into five buckets: it won't start, Oxide is behind a patch, a plugin broke, wipe day is lagging, or a player can't get in. Work through them in that order and you'll catch most things before opening a ticket.

First boot takes 10 minutes (not a bug)

On a fresh order, the container has to SteamCMD-validate the Rust files, overlay Carbon, install plugins if any, generate the procedural map, then write the savefile. That's about 10 minutes on a default 3500 map; bigger maps take longer. The dashboard milestones tick through it: Setting up, Verifying game files, Loading map, Generating savefile, Ready.

If you ordered, came back five minutes later, and it still says Loading map, give it the full ten. Restart-time on subsequent boots is much quicker because the savefile is already there.

Server won't start after a Rust update

Facepunch ship Rust patches on Thursdays (Force Wipe, the first Thursday of the month, is the big one). When a patch lands, Oxide always lags by a few hours, sometimes longer for breaking changes. Symptom: server starts SteamCMD-validating, pulls the new Rust files, then either:

  • Fails to load Oxide and falls back to vanilla, or
  • Loads Oxide but every plugin throws "is for an older version" on boot.

Fix: wait for Oxide to publish a build for the new Rust version, then restart. The dashboard image picks up new Oxide builds automatically once they're out. Carbon updates on its own timeline and is usually faster than Oxide on Force Wipe day, sometimes slower; if your server runs Carbon, check carbonmod.gg for the patch status.

If you absolutely need the server up before Oxide updates, you can run vanilla temporarily by disabling the plugin loader; expect plugin configs to need a reload check once you flip it back.

A plugin won't load after an update

A single broken plugin can take down your boot. Open the dashboard console and watch the load logs; you'll see something like:

Failed to compile: oxide/plugins/SomePlugin.cs(42,17): error CS1061

That's your culprit. Two paths: pull the latest version of that plugin from uMod (most authors push fixes within a day or two of a Rust update), or remove it from oxide/plugins/ if it's abandoned. To audit load times and find slow plugins under load:

oxide.show plugins

Run that from RCON. It lists every loaded plugin with hook times. Anything sitting at multiple milliseconds per hook in a tight loop is suspect.

Lag during high pop

Wipe day or a populated evening, tick rate drops, players rubber-band. Usual suspects, in the order to check:

  • Entity caps: old decay structures, twig spam, dropped item piles. Rust's decay is meant to handle this, but plugins can interfere. Check server.entityCount in RCON; if it's climbing forever, something's not despawning.
  • A greedy plugin loop: oxide.show plugins shows hook times. A plugin doing world scans every tick is the classic case.
  • Map size vs RAM: a 4500 procedural map on a 10 GB Standard plan with a big plugin stack is asking too much. Either drop the map size in server.cfg, trim plugins, or move to Pro or Elite. See picking your Rust server plan for the tier guidance.
  • Real hardware headroom: if RAM is at 95% sustained and CPU is pegged at peak, no amount of plugin tuning saves you; upgrade.

A wipe didn't run on schedule

Open Settings → Wipe schedule and check three things:

  • Cadence isn't set to "none" by accident. Easy to do during dashboard fiddling.
  • wipeDayOfWeek is correct (0 = Sunday, 4 = Thursday). The most common surprise is setting "Thursday" mentally but having the field on a different number.
  • wipeHourUtc is the time you actually want, in UTC, not your local timezone. Wipes run in UTC; in BST/CEST/EDT, your local clock will be off from UTC by an hour or more.

If all three look right and the wipe still didn't fire, check lastMapWipeAt on the server record; sometimes a wipe ran successfully but at a different UTC hour than you expected, and your local Discord ping made it look like it didn't run. See the wipe scheduler doc for the full cadence breakdown.

Players can't connect

Symptom: you're in fine, your community isn't. A few things to check:

  • Modded vs vanilla filter in their server browser. If they've ticked "Vanilla only", a server running Oxide or Carbon won't appear. Tell them to flip to Modded or Community.
  • Query port mismatch on stat trackers. BattleMetrics, Rustservers.gg, and Steam favourites use the query port (game port +1). If they pasted the game port into the favourites box, Steam won't see the server as up even though it's live. Use the query port for favourites and the game port for client.connect; both numbers are on the dashboard's Connect tab.
  • Region: if your hostname resolves to an EU node and they're filtering by region, ask them to clear the region filter or use F1 client.connect directly.
  • Banned: check server.users.cfg and the Players tab. We've all forgotten about a ban from last wipe.

Where to go next

Last updated 2026-05-20. Notice a mistake? Tell us.

Cookies

We use a few cookies that are strictly necessary to sign you in and keep your account secure. We do not load any advertising or third-party trackers. We would also like to run our own cookieless analytics so we can understand which pages are useful. See our Cookie Policy for the full list.