Rust Server Management Tips for Admins: Setup, Security, Updates, and Recovery

Reliable Rust administration comes from treating the server as a layered system: define a stable identity and resource budget, keep startup and persistent settings separate, lock down ports and RCON, stage every update, and rehearse restores before a wipe or outage. The steps below follow Facepunch’s current documentation and plugin rules, including the March 4, 2026 guidance for modded community servers.

Godlike.Host offers hosted Rust servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.

Plan the server before you install it

Write down the decisions that affect every later operation: the server.identity name, map level and seed, world size, maximum players, region, and whether the instance will be vanilla, a policy-compliant Community server, or a private/hidden server. An identity gets its own saves, configuration, and player data, so naming it clearly makes backups and incident recovery safer. Facepunch documents the complete creation process in Creating a server.

#	Preview	Product	Price
1		Rust Key Cards, Rust Red Key Card, Cobalt Restricted Access Cards, Rust Gift For Gamers, Blue Key...	$25.00	Buy on Amazon
2		Rust Video Game Notebook	$15.00	Buy on Amazon
3		Rust Game Props Large Furnace (S)	$14.99	Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

Match world size and player cap to hardware

• World-size values in the documented range run from 1000 to 6000. Larger worlds consume more disk space and memory.
• Higher player caps require more CPU capacity. Set the cap from the hardware you can sustain, not from a marketing maximum.
• Record the seed and level settings with the identity name. Recreating the same map later depends on those values and the corresponding save files.
• Choose a region close to most players and confirm that your provider can supply DDoS protection and change the server IP quickly if an attack requires migration.

Install Rust and use a deliberate configuration hierarchy

Facepunch’s setup guide uses SteamCMD to install the dedicated server. Keep the installation itself separate from the data for each instance. A typical identity path is rust/server/server.identity/. You can run several servers from one installation by assigning each a different identity, which isolates maps, saves, configurations, and player data while avoiding duplicate binaries.

Put each setting in the right layer

Use the startup command for values that must be present before the process starts, especially the identity, game port, query port, RCON port, and RCON password. Put groups of persistent gameplay and server settings in rust/server/server.identity/cfg/server.cfg. Facepunch states that server.cfg is read at startup and takes priority over lower-priority automatic settings. OxideMod documents the complete precedence order as command-line parameters first, then server.cfg, then ServerAuto.cfg in Server Setup.

#1 Best Overall

Rust Key Cards, Rust Red Key Card, Cobalt Restricted Access Cards, Rust Gift For Gamers, Blue Key Card, Green Key Card (ALL THREE)

• Inspired by the Rust Video Game – These cards replicate the iconic keycards found in Rust (Red, Blue, Green).
• High Quality PVC Plastic – Printed on both sides, durable and water-resistant. Not a sticker.
• Great Rust Gift Idea – Perfect for fans of Rust, whether for cosplay, loot-themed gifts, or collection.
• Wallet-Size Replica – Standard 3.375x2.125 inches, 30 mil thick—fits in any wallet.
• NOT a sticker*

$25.00

Buy on Amazon

After changing a setting, restart the server and inspect the startup log or in-game value to confirm which layer won. Keeping a written inventory of every intentional override prevents an automatic file or an old launch script from silently restoring an unwanted value.

Open only the ports you need and secure RCON

Facepunch’s example uses game port 28015, RCON port 28016, and a separate query port. The game and query ports use UDP, must be reachable from the internet for a public server, and cannot be the same port. RCON requires a password and remote-administration software; use the exact port and protocol settings supplied by your host and firewall rather than assuming that all three ports are interchangeable. See Facepunch’s port and launch examples.

Firewall and credential checklist

1. Allow inbound UDP only for the game and query ports that your instance actually uses.
2. Expose the RCON port only to the administrator addresses or private management network that need it. If your provider supports an allowlist or VPN, use it.
3. Generate a long, unique RCON password; never reuse a player, operating-system, panel, or database credential. Facepunch’s example marks its password as a value you must change.
4. Store the password in a secrets manager or protected environment variable, not in a public repository, screenshot, support ticket, or shared chat.
5. Test RCON from an approved management client, then verify that an unauthorized network cannot connect.

When a server is compromised, rotate the RCON password first, revoke exposed management access, review logs for administrative commands, and only then reopen the game ports.

Operate multiple instances with identities and known data files

A separate server.identity folder lets one installation host multiple isolated servers. The identity contains the files you need to preserve and restore:

• Save and map data: the current world state and generated map.
• Blueprint data: learned crafting progress, which may be wiped independently of the map.
• Player data: inventories, progression, and related records.
• Configuration: the command-line launch definition and files such as cfg/server.cfg.
• Plugin and mod data: configuration and persistent data created by uMod/Oxide plugins.

Facepunch’s Getting started with your Rust server guide notes that the server creates backups whenever it saves. Those save-time copies are useful for quick rollback, but they are not an independent disaster-recovery system: a damaged disk, ransomware event, or mistaken deletion can affect both the live files and local backups.

Rank #2

Rust Video Game Notebook

$15.00

Buy on Amazon

Build backups you can actually restore

Copy the complete identity folder to independent storage, including map, save, blueprint, player, configuration, and plugin data. The official guide does not prescribe an external schedule, so choose one from your wipe cadence and loss tolerance: retain more restore points around scheduled wipes and fewer between low-risk periods. Encrypt backups that contain RCON credentials or player information, restrict who can read them, and periodically verify that the files can be opened.

Document a restore runbook

1. Stop the server process and record the failure time and the last known-good backup.
2. Preserve the damaged identity folder for later analysis; do not overwrite your only evidence.
3. Restore the selected map/save, blueprint, player, cfg, and plugin-data files into the correct identity path.
4. Confirm ownership and permissions, then start with the intended command line and inspect logs for missing or incompatible files.
5. Join as an administrator, check map state, inventories, blueprints, RCON, and plugin functions, and only then allow players back in.

A forced wipe changes protocol and map data. A blueprint wipe is a separate operation, so handle blueprint files deliberately rather than assuming that replacing the map also resets learned recipes.

Update Rust and Oxide without breaking the server

Rust updates can invalidate plugins. Facepunch explicitly says Oxide must be updated after server updates and warns that running SteamCMD in a startup script can overwrite Oxide files and return the installation to vanilla. Automation is useful, but an update-and-restart sequence must account for that ordering.

Safe staged-update procedure

1. Announce maintenance, stop new joins, and make an external backup of the identity folder.
2. Stop the server cleanly so save-time backups complete.
3. Update the Rust server files with SteamCMD or your host’s equivalent, but do not immediately accept players.
4. Install the Oxide/uMod build that matches the updated Rust server.
5. Review every plugin for compatibility, remove or quarantine plugins that have errors, and compare configuration changes rather than blindly replacing files.
6. Start in a staging identity when possible. Read console and plugin logs, test RCON, teleport/admin commands, chat moderation, and any critical gameplay hooks.
7. Open the production ports only after the server reports a healthy plugin state. Keep the pre-update backup until the first stable save and player verification.

If an automated script repeatedly produces a vanilla server, separate the SteamCMD update job from the Oxide installation step and make the script fail visibly when the expected Oxide files are absent.

Know which plugins fit a Community listing

Facepunch’s plugin guidance, updated March 4, 2026, draws a practical line: gameplay-changing and UI-changing plugins belong outside Community rules, while administration and anti-cheat plugins are allowed when they do not alter gameplay for players. Administration examples can include moderation, queue, and chat-management functions when they stay within that limit. Vanilla convars are permitted, but Facepunch warns that most convars are development or debugging settings and that changing defaults can have undesirable performance effects.

Rank #3

Rust Game Props Large Furnace (S)

• Acrylic Painting Pla Plastic

$14.99

Buy on Amazon

Before installing a plugin, record what player behavior it changes, what permissions it grants, what data it writes, and how it will be removed. Test convar changes under realistic load; a setting that appears harmless can raise CPU, memory, or tick-time costs.

Monitor performance and troubleshoot from symptoms

Review server and plugin logs after every restart and update. Track CPU utilization, memory growth, disk space, tick or frame behavior, player reports, connection failures, and repeated plugin exceptions. Correlate a performance change with the last configuration or plugin change instead of changing many variables at once.

Common symptoms and targeted fixes

• Server is invisible: confirm the game and query ports are distinct, reachable UDP ports, and that the advertised identity and region are correct.
• Players cannot connect after a reboot: check firewall rules, provider security groups, the bound ports in the launch command, and whether the process actually completed startup.
• RCON fails: verify the port, password, remote-client settings, and source-IP allowlist; rotate the credential if it may have been exposed.
• Plugins disappeared after an update: inspect whether SteamCMD restored vanilla files, reinstall the matching Oxide build, and then validate each plugin.
• Rising memory or tick delays: review recent plugins and convar changes, reduce world size or player cap if hardware is saturated, and remove development settings that are not required.
• Players lost progress: stop writes, identify the latest intact save-time or external backup, restore to a test identity, and verify before replacing production data.

Choose self-hosting, managed hosting, or a private deployment

Facepunch’s hidden-server guidance notes that Rust does not provide a built-in traditional whitelist. Advanced administrators can combine hidden-server techniques with skip-queue controls and network-level restrictions, but those measures do not replace firewall rules or careful credential handling.

Stay transparent and compliant

Facepunch permits private, unofficial, and community servers, but its Community Server and Hosting Guidelines require clear presentation: do not call a server “official” or imply that it is operated by Facepunch. The same guidelines allow fees, donations, cosmetics or effects, server currency, adverts, sponsorships, and product placements when they are labeled fairly and players retain access to validly purchased Facepunch DLC. Publish your rules, wipe schedule, moderation process, plugin list, and refund or donation terms where players can find them.

A repeatable administrator operating cycle

1. Before launch: confirm identity, seed, level, world size, cap, region, ports, firewall, RCON secret, backup destination, and listing classification.
2. Daily: read logs, check disk space and memory, review plugin errors and player reports, and confirm that saves and backups are being created.
3. Before every update: announce downtime, stop cleanly, copy the identity, update Rust, reinstall matching Oxide, and test in staging.
4. After an update: verify RCON, connections, map state, permissions, moderation tools, and critical plugins before opening the server.
5. Before a wipe: decide separately whether map, save, blueprint, or player data will be reset; archive the prior identity and communicate the exact scope.
6. After an incident: isolate the cause, preserve evidence, restore into a test identity, document the fix, and update the runbook so the next recovery is faster.

This discipline keeps configuration changes intentional, limits the blast radius of compromised credentials or broken plugins, and turns wipes and updates into controlled maintenance rather than emergencies.

Quick Recap

Bestseller No. 1

Rust Key Cards, Rust Red Key Card, Cobalt Restricted Access Cards, Rust Gift For Gamers, Blue Key Card, Green Key Card (ALL THREE)

Wallet-Size Replica – Standard 3.375x2.125 inches, 30 mil thick—fits in any wallet.; NOT a sticker*

$25.00

Bestseller No. 2

Rust Video Game Notebook

$15.00

Bestseller No. 3

Rust Game Props Large Furnace (S)

Acrylic Painting Pla Plastic

$14.99

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.