RCON Remote Administration for Rust
Guide to setting up and using RCON for remote Rust server administration on Witchly.host. Learn about RCON tools, security, and best practices.
Rust (7 articles)
On This Page
RCON Remote Administration for Rust
RCON (Remote Console) allows you to administer your Rust server remotely without needing to be in-game or logged into the dashboard. With RCON, you can run console commands, monitor server activity, manage players, and configure settings from a desktop application or web interface.
What Is RCON?
RCON is a protocol that provides remote access to your server’s console. Any command you can run in the dashboard console can also be run through RCON. This is particularly useful for:
- Quick administration — Run commands without logging into the dashboard
- Multi-server management — Manage multiple servers from a single application
- Real-time monitoring — Watch server output, chat, and events in real time
- Mobile administration — Some RCON tools offer mobile-friendly interfaces
- Team administration — Give moderators RCON access without panel access
Finding Your RCON Details
Your RCON connection information is available in your dashboard:
- Log in to Dashboard and select your Rust server
- Navigate to the Startup tab
- Look for the following values:
- Server IP — Your server’s IP address
- RCON Port — The port used for RCON connections (usually your game port)
- RCON Password — The password required to authenticate (found in startup variables)
Important: Never share your RCON password publicly. Anyone with your RCON credentials has full administrative control over your server.
RCON Tools
Several third-party tools provide RCON connectivity for Rust servers. Here are the most popular options:
RustAdmin
RustAdmin is the most widely used Rust RCON tool, offering a full-featured desktop application for Windows.
Features:
- Real-time console output and chat monitoring
- Player list with Steam profile links
- Quick-action buttons for common commands (kick, ban, mute)
- Chat input for communicating with players
- Server information display (player count, FPS, entities)
- Multiple server support with saved profiles
Setup:
- Download RustAdmin from the official website
- Open the application and click Add Server
- Enter your server details:
- IP: Your server’s IP address
- Port: Your RCON port
- Password: Your RCON password
- Click Connect
- You should see the server console output and player list
WebRCON
WebRCON is a browser-based RCON client that works on any device with a web browser.
Features:
- No software installation required
- Works on Windows, macOS, Linux, and mobile devices
- Real-time console and chat
- Command input and history
Setup:
- Open a WebRCON tool in your browser (several free options are available online)
- Enter your server IP, RCON port, and password
- Click Connect
- Use the console to send commands
Rust Server Manager
A comprehensive Windows application that combines RCON with additional management features.
Features:
- RCON console access
- Scheduled commands and automated tasks
- Player tracking and logging
- Chat monitoring and filtering
Essential RCON Commands
Once connected via RCON, you have access to all Rust server commands. Here are the most commonly used:
Server Management:
| Command | Description |
|---|---|
server.save | Forces an immediate world save |
server.writecfg | Saves configuration changes permanently |
quit | Gracefully shuts down the server |
status | Shows connected players with SteamIDs |
serverinfo | Displays server performance stats |
ent count | Shows total entity count |
fps | Shows server FPS (frames per second) |
Player Management:
| Command | Description |
|---|---|
players | Lists all connected players |
kick <steamid/name> "reason" | Kicks a player from the server |
ban <steamid/name> "reason" | Permanently bans a player |
banid <steamid> "name" "reason" | Bans by SteamID (works for offline players) |
unban <steamid> | Removes a player ban |
banlist | Shows all banned players |
mute <steamid/name> | Mutes a player in chat |
unmute <steamid/name> | Unmutes a player |
Communication:
| Command | Description |
|---|---|
say "message" | Sends a server-wide message |
global.say "message" | Alternative server-wide message |
Oxide Plugin Commands:
| Command | Description |
|---|---|
plugins | Lists all loaded Oxide plugins |
oxide.reload PluginName | Reloads a specific plugin |
oxide.reload * | Reloads all plugins |
oxide.grant group default permission | Grants a permission to a group |
oxide.revoke group default permission | Revokes a permission |
Security Best Practices
RCON provides full administrative access to your server, making security critical:
Use a strong RCON password:
- Minimum 16 characters with a mix of letters, numbers, and symbols
- Never use dictionary words, server names, or common passwords
- Change your RCON password periodically
Limit who has access:
- Only share RCON credentials with trusted administrators
- Consider using different permission levels (owner vs. moderator) through Oxide rather than giving everyone RCON access
- Keep a record of who has RCON access
Secure your connection:
- Avoid using RCON over public Wi-Fi networks without a VPN
- Close RCON client connections when not actively administrating
- Do not leave RCON tools running unattended on shared computers
Monitor RCON usage:
- Review server logs for unexpected RCON connections
- If you suspect unauthorized access, change your RCON password immediately
- Check for commands you did not issue in the console logs
If you suspect a compromise:
- Change your RCON password immediately in the Startup tab of your dashboard
- Restart your server to force-disconnect any active RCON sessions
- Review recent console logs for suspicious activity
- Check for unauthorized admin grants:
banlistandmoderatoridlist - Verify server configuration has not been tampered with
Setting Up Moderator Access
Instead of giving moderators full RCON access, consider using Rust’s built-in moderator system:
- Grant moderator status:
moderatorid <steamid64> "PlayerName" "Moderator" - Save:
server.writecfg - Moderators can use admin commands in-game (F1 console) without needing RCON
This is safer because:
- Moderators cannot shut down or fully reconfigure the server
- Their access is tied to their Steam account, not a shared password
- You can revoke access individually without changing shared credentials
Scheduled Commands
Some RCON tools support scheduled commands, useful for:
- Automatic broadcasts: Remind players about rules, Discord links, or events at regular intervals
- Scheduled saves: Force saves at specific times in addition to auto-save
- Timed announcements: Warn players about upcoming wipes or maintenance
Example schedule in RustAdmin:
Every 30 minutes: say "Join our Discord: discord.witchly.host"
Every 60 minutes: say "Server wipes every Thursday at 6 PM EST"
Every 300 seconds: server.save
Troubleshooting
Cannot connect to RCON:
- Verify the IP address, port, and password are correct
- Ensure your server is running and fully started
- Check that you are using the RCON port, not the game port (they may differ)
- Some RCON tools require WebSocket connections — verify your tool supports Rust’s RCON protocol
RCON connection drops frequently:
- Check your internet connection stability
- Some tools have timeout settings — increase the timeout value
- Reconnect and check the server console for any related error messages
Commands not working:
- Verify the command syntax — Rust commands are case-sensitive
- Some commands require Oxide to be installed
- Check that you are connected with the correct password (read-only vs. full access)
Lag when using RCON:
- RCON itself should not cause server lag
- If running commands that affect game state (teleporting many entities, etc.), lag may occur
- Avoid running heavy commands during peak hours
Need help with RCON setup? Contact our support team on Discord.