Rust Dedicated Server FAQ and Fixes
Rust separates identity data, generated maps, player-facing traffic, Steam query traffic, and WebRCON administration. Confusing any two can make a healthy server look missing or can turn a planned map change into an accidental wipe. These checks preserve the active identity directory before testing launch arguments or plugins. Record the complete startup command, identity name, seed, world size, and current build so the next launch can be compared with the last known-good run.
Read this before changing anything
Run server.save and native quit, then copy the entire active server/<identity> directory—including database sidecars and companion.id—before an update, wipe, plugin change, import, or restore.
6 common problems
Match the symptom. Make it right.
Open the answer that sounds like your server. Start at the top of its checklist and stop as soon as the server is healthy.
01NetworkingIs UDP 28016 always Rust's query port?
What players see
Different setup guides assign 28016 to different services.
What happened
Rust ports are configurable and derived defaults can vary with the other selected ports.
Why it happened
Gone Wrong Servers explicitly uses UDP 28016 for query and TCP 28017 for RCON.
What to do next
- 1Read the live server.port, server.queryport, and rcon.port values.
- 2Match every firewall/router/client rule to the protocol and configured value.
References[facepunch-create]
02WorldWhy did changing the launch script look like a server wipe?
What players see
A new procedural world opens after maintenance.
What happened
The startup definition selected a different identity, seed, size, map type, or save protocol.
Why it happened
Rust derives the durable world from those connected identity values.
What to do next
- 1Stop before saving more state.
- 2Restore the original launch values and complete identity from a known-good snapshot.
References[facepunch-create]
03UpdatesDoes every monthly Rust update require a blueprint wipe?
What players see
A server owner plans to reset all progression for every update.
What happened
A map/protocol wipe and a blueprint-progression wipe are separate events.
Why it happened
The current Facepunch update announcement, not a generic monthly rule, determines forced compatibility changes.
What to do next
- 1Read the current official update notice before maintenance.
- 2Tell players explicitly whether map, blueprints, or neither will reset.
References[rust-news]
04AccessCan I set a vanilla Rust join password?
What players see
A private group expects a password field.
What happened
Vanilla Rust does not provide a normal join password.
Why it happened
Private access needs a network boundary, an understood allowlist, or a separately evaluated plugin approach.
What to do next
- 1Choose the access design before publishing the server address.
- 2Back up and test any third-party allowlist plugin rather than advertising a nonexistent native feature.
References[facepunch-create]
05ModsWhy did plugins disappear after SteamCMD validation?
What players see
Rust starts without the expected plugin framework.
What happened
Validation can replace files patched by a third-party framework.
Why it happened
Oxide/uMod and Carbon are separate from official Rust binaries and must match the updated build.
What to do next
- 1Preserve plugin config/data and confirm vanilla startup.
- 2Install a compatible framework build, then reintroduce plugins in controlled groups.
References[facepunch-create]
06Rust+Why did Rust+ stop working after migration?
What players see
The game server works but the companion app is offline or unpaired.
What happened
The companion port or companion.id did not move with the server identity, or pairing was regenerated.
Why it happened
Rust+ has its own TCP service and sensitive persistent pairing identity.
What to do next
- 1Restore companion.id privately from the same stopped identity snapshot.
- 2Verify the actual app.port and its firewall/NAT path separately from game/query ports.
References[rust-companion]
Step-by-step troubleshooting
Complete Rust server fixes
Use these focused guides when the short answer matches your symptom and you need the full diagnostic path.
The server process starts and one service works, but direct joining, the server browser, or RCON fails—often after copying a guide that assumes port 28016 always means RCON.
Rust Game, Query, and RCON Ports Explained
Fix Rust joins, server-browser discovery, or RCON by mapping each configured port to the correct UDP or TCP service.
Read the complete fix →
After migration or maintenance, Rust starts normally but shows a new map and no expected bases, while old .map, .sav, or database files may still exist under another identity.
Rust World Appears Wiped After Identity Change
Recover a Rust server that starts a fresh procedural map after its launch script, identity, seed or world size changes.
Read the complete fix →
The vanilla Rust server reaches startup complete after an update, but plugins disappear, produce API errors, or crash the process before players can join.
Rust Plugins Fail After a Server Update
Recover Oxide/uMod or Carbon plugins after SteamCMD updates Rust and replaces or invalidates framework files.
Read the complete fix →
Official references
Built from current game guidance
Last reviewed 2026-08-30. Game behavior changes, so official sources win when a new patch changes an option.
Rust and its artwork are the property of their respective owners. Gone Wrong Servers is independent third-party software.
Can your friends play tonight?
Free gives you the complete server: guided install, settings, connection help, manual operation, mods, backups, and recovery. Pro adds Guardian, scheduling, safe automatic updates, advanced recovery, and concurrent servers.