Rust server RCON setup is one of the highest leverage tasks for operators. If your command path is unstable, every moderation action slows down and every wipe day gets harder. This guide covers a repeatable setup flow for secure WebSocket RCON and fast verification.
Start by enabling RCON in your server config with a strong password and explicit port. Keep credentials out of shared chat, rotate periodically, and store encrypted values in your control plane.
rcon.web 1 rcon.ip 0.0.0.0 rcon.port 28016 rcon.password "CHANGE_ME_STRONG_PASSWORD"
After config reload, test with safe read commands first. Avoid destructive commands until you have verified output formatting, latency, and permission boundaries for each staff role.
> serverinfo [OK] Framerate: 101, Players: 143, EntityCount: 280123 > playerlist [OK] Returned 143 players
Teams running more than one server should centralise command execution and history. With a shared control plane, moderators can use approved commands while admins retain access to advanced operations and audit exports.
Next steps: follow the getting started docs, then set up Discord webhook alerts so every critical event is visible in real time.
Start RustGuard free and run your first command in minutes.