Common Rust server issues and how to fix them
Most Rust connection failures come from a closed port or a server that hasn't re-registered with Steam, and most crashes come from memory pressure or a conflicting Oxide plugin. Restarting fixes registration; oxide.reload isolates a bad plugin without a full restart.
Rust server problems generally fall into four buckets: connection problems, performance and crashes, admin or Oxide plugin issues, and world or save file issues. Most have a quick fix you can run from the server console, the same place you'd enter any Rust admin or troubleshooting command whether you're self-hosting or on a host. On berrybyte that's the Console tab.
Why won't players connect to my server?
Start with the basics: confirm the server shows as running from Overview, then check status from the Console tab with:
status
If the server is running but players still can't join, it may not have finished registering with Steam. This happens most often right after a restart or a fresh server creation.
Check the server is running
Open Overview and confirm the status shows as running, not stopped or starting.
Confirm the port is reachable
Rust needs its game port (UDP) reachable from the internet. Check your port configuration under Network if players consistently time out rather than getting refused.
Restart to re-register with Steam
A restart forces the server to re-announce itself to Steam, which clears up most stuck connection states.
If only one player can't connect while others join fine, the problem is usually on their end: a firewall, VPN, or a stale Steam server list cached locally.
Why isn't my server showing up in the Rust server browser?
New servers can take 10-15 minutes to appear after their first start. If it's been longer than that:
- Restart the server to force Steam to refresh its listing.
- Check steamstat.us for a wider Steam outage before assuming the problem is on your end.
Why are players lagging or seeing high ping?
Distance to the server is the biggest factor. Beyond that, two convars directly affect how smooth the connection feels:
| Command | What it does |
|---|---|
server.tickrate 30 | Sets how many times per second the server simulates the world. Rust defaults to 30; lowering it reduces server load at the cost of responsiveness. |
fps.limit 60 | Caps the server's internal frame rate, freeing CPU headroom that would otherwise go to uncapped rendering work on the host. |
Both are runtime console commands: type them into the server console on a
running server (on berrybyte, the Console tab) and they apply
immediately, no restart needed. If you self-host, you can also set them as
startup arguments in your launch script with a + prefix, +server.tickrate 30 +fps.limit 60, so they're already in effect the moment the server boots.
Why is my server's FPS low, or why does it crash?
Low server FPS and crashes usually share a root cause: the server is doing more work than its plan's resources comfortably support.
| Command | What it does |
|---|---|
server.worldsize 3000 | Reduces the map size, which lowers the amount of terrain and entities the server tracks. Only takes effect on next world generation. |
gc.collect | Forces an immediate garbage collection pass, freeing memory the server hasn't released yet. |
pool.print_memory | Prints current memory pool usage, useful for confirming whether memory pressure is the problem before you change anything. |
server.worldsize only takes effect the next time the world regenerates, so
setting it in the console on a live server just queues the change. Self-hosters
usually set it as a startup argument instead, +server.worldsize 3000 in the
launch script, so a fresh world generates at that size on the next boot.
gc.collect and pool.print_memory are runtime console commands you can run
anytime the server is up.
If FPS stays low after tuning these:
- Reduce or remove Oxide plugins, especially ones that hook frequently (loot tables, custom events, economy plugins).
- Upgrade to a plan with more RAM if your server regularly runs at 40+ players.
For crashes specifically, check oxide/logs/ in Files for the error
around the crash time, then disable plugins one at a time from Settings →
Game Settings or by removing them from the plugins folder until the crashes
stop. If the world files themselves look corrupted afterward, stop the server
and restore a backup rather than continuing to run
against damaged files.
Why don't my admin commands work?
Confirm your admin status first, then re-add yourself as an owner if needed:
| Command | What it does |
|---|---|
status | Lists connected players along with their Steam IDs, useful for confirming your own ID before granting admin. |
ownerid STEAMID64 "Name" "Admin" | Grants full server owner permissions to the given Steam ID. |
oxide.grant user STEAMID64 admin | Grants Oxide's admin permission group specifically, separate from Rust's native owner system. |
Rust and Oxide track admin permissions separately, so a player can have one
without the other. If native commands work but Oxide-based admin commands
don't, you likely need the oxide.grant step above too.
Why isn't a plugin command responding?
Work through it in order:
Confirm the plugin loaded
Run oxide.plugins in the Console tab and check the plugin appears in the list without
errors next to it.
Reload the plugin
Run oxide.reload PluginName to reload just that plugin without restarting the whole server.
Check the player has permission
Run oxide.grant user STEAMID64 pluginname.use, substituting the plugin's actual permission
name from its documentation.
Disabling a plugin outright can leave behind data or configs that conflict if you reinstall it later. When troubleshooting, reload or unload through Oxide rather than deleting plugin files directly, unless you're intentionally removing it for good.
How do I update my Rust server?
Rust updates through Valve's SteamCMD tool underneath, whether you're self-hosting or running on a host. If you manage your own server, pull the update directly with SteamCMD:
steamcmd +force_install_dir ./rust_server +login anonymous +app_update 258550 +quit
If the update fails, check that SteamCMD has write access to the install directory and that there's enough free disk space; Rust's install is large and a failed update often leaves a partial download behind.
On berrybyte, updates are handled for you: enable Auto Update in Settings → Game Settings to pick up new Rust builds automatically, or trigger one manually by restarting the server from Overview.
Either way, back up configs before a major update and test that any Oxide plugins you rely on still load cleanly afterward, since a Rust update can break plugins that haven't been updated to match.
What do I do about world generation or save problems?
Changing the seed or world size only takes effect the next time the map regenerates, so use these carefully on a server people already play on. As runtime console commands they queue the change for the next regeneration:
server.seed 12345
server.worldsize 4000
If you self-host, you'll more commonly set these as startup arguments in your launch script instead, so the new seed or size is already active the next time the server boots:
+server.seed 12345
+server.worldsize 4000
Changing the seed or world size on an existing server generates a brand new map. Everything built on the old map is lost. Only run these commands when you intend to reset the world, and take a backup first if you're not certain.
If a save looks corrupted rather than intentionally reset:
Stop the server immediately
Continuing to run against a corrupted save risks the corruption spreading to your next automatic save.
Restore your latest backup
Open Backups and restore the most recent backup taken before the corruption appeared.
Test before reopening to players
Start the server and confirm the world loads cleanly before announcing it's back up. See Start, stop & restart for what each power control does.
No usable backup, or the install itself looks damaged rather than just the save? On berrybyte,
stop the server and use Settings → Danger zone → Reinstall Server for a clean slate. Leave
Create a backup first ticked, and tick Erase all files before reinstalling only when you
intend to lose the current world. Self-hosted, the equivalent is reinstalling through SteamCMD
with app_update 258550 validate.
Why is player data corrupted, or why can't players authenticate?
Player data corruption is usually isolated to specific .fwl or .map files
rather than the whole save. Check Backups for a version from before the
corruption and restore individual files through Browse files on that
backup rather than a full restore, if you only need to fix a handful of
players.
For authentication issues, a full restart usually clears stuck Steam
sessions. If VAC-related errors persist, confirm secure mode is enabled by
running server.secure 1 in the console, or, if you self-host, by setting
+server.secure 1 as a startup argument in your launch script so it's
always on from boot.
A specific player keeps getting kicked or can't log in
Ask them to fully restart their Steam client and verify their local game files. Most authentication errors are client-side rather than server-side.
Everyone got logged out at once
This usually follows a crash or an unexpected restart. Once the server is back up and stable, players should be able to reconnect normally.
A player's inventory or blueprints reset
Their player data file may have corrupted independently of the world save. Check whether an older backup has an intact copy of that player's data before assuming it's gone for good.
If you've worked through the relevant section above and the issue continues, open a support ticket with your server linked and a rough timestamp of when the problem started.
Frequently asked questions
Why does my Rust server crash during peak hours?
More players means more entities, scripts, and Oxide hooks running at once, which raises CPU and RAM load. Check usage in the dashboard and consider upgrading RAM or lowering your max player count if crashes cluster around your busiest hours.
How often should I restart my Rust server?
A daily restart during low-population hours clears accumulated memory and applies any pending update if Auto Update is enabled. Busier servers benefit from restarting more often.
What causes "Connection Failed" errors on a Rust server?
Usually the server hasn't finished registering with Steam yet, is temporarily overloaded, or a required port isn't reachable. Restarting the server and checking its status in the dashboard resolves most cases.
How do I recover a corrupted Rust world save?
Stop the server immediately to avoid overwriting anything further, then restore your most recent backup. If no usable backup exists, you'll need to generate a new world with a fresh seed.
How do I update a Rust server manually?
Rust updates through SteamCMD: steamcmd +force_install_dir ./rust_server +login anonymous +app_update 258550 +quit. On berrybyte you don't need SteamCMD directly; enable Auto Update or trigger an update by restarting the server.