keepcalculator

06 Numbers and Powers

Rust Server Security: How to Protect Your Server

Card No. 06·73188 · Updated · Standard formula, shown below

Securing a Rust server is essential for keeping gameplay fair, preventing griefing, and protecting player data. This guide walks you through the key steps to lock down your server, from basic configuration to advanced anti-cheat and backup strategies. You’ll need access to your server’s control panel or files, and a basic understanding of server administration.

What You’ll Need

  • Access to your server’s file system (via FTP, SFTP, or a hosting control panel)
  • Ability to edit configuration files (like server.cfg)
  • Admin privileges in-game or via RCON
  • A reliable backup solution (local or cloud storage)

Step-by-Step

  1. Set a strong server password (if private): If your server is meant to be private, set a password in server.cfg using server.password "your_strong_password". Use a mix of uppercase, lowercase, numbers, and symbols. Never use a password you use elsewhere.
  2. Enable and configure EAC (Easy Anti-Cheat): In your server startup parameters, ensure -eac is included. This prevents players with modified game files from joining. For community servers, keep EAC on unless you have a specific reason to disable it.
  3. Install a plugin-based anti-cheat: Use a framework like Oxide (for Rust legacy) or Carbon (for newer versions) and install anti-cheat plugins such as AntiCheat or Vanish. Configure them to detect common cheats (speed hacks, fly hacks, aimbots) and automatically ban offenders.
  4. Set up RCON with a strong password: RCON allows remote administration. In your server config, set rcon.password "a_different_strong_password" and rcon.port 25575 (or a custom port). Never use the same password as the server password. Use a tool like RustAdmin or the built-in RCON console to manage your server securely.
  5. Regularly update the server: Keep your server software and plugins up to date. Rust releases patches that fix exploits and security vulnerabilities. Set up automatic updates if your hosting provider allows it, or check for updates manually at least weekly.
  6. Backup your server files and database: Schedule automatic backups of your world files (server.identity folder) and any databases (like Oxide’s oxide/data). Store backups in a separate location (e.g., cloud storage) to prevent data loss from crashes or attacks.
  7. Monitor server logs: Regularly review your server logs (in Logs folder) for suspicious activity, such as repeated connection attempts, admin command abuse, or plugin errors. Set up alerts if your hosting panel supports them.
  8. Restrict admin commands: Only give admin privileges to trusted individuals. Use the ownerid and moderatorid commands in-game to assign roles. Avoid giving full admin to everyone; use plugins to delegate specific permissions (e.g., kick, ban) without full control.
  9. Secure your server files: Change default FTP and RCON ports to non-standard ones. Use SFTP instead of FTP if possible. Ensure your hosting account password is strong and changed regularly.
  10. Use a firewall (if self-hosted): If you run the server on your own hardware, configure a firewall to only allow necessary ports (e.g., 28015 for game traffic, 25575 for RCON, and your FTP port). Block all others.

Common Mistakes

  • Using weak or reused passwords: This is the most common security flaw. Always use unique, complex passwords for server, RCON, and hosting accounts.
  • Disabling EAC: Some server owners disable EAC to allow modded clients, but this opens the door to cheaters. Keep EAC on unless absolutely necessary.
  • Ignoring plugin updates: Outdated plugins can have security holes. Regularly check for updates and remove unused plugins.
  • Not backing up: A single attack or data corruption can wipe your world. Regular backups are your safety net.
  • Giving too many people admin: More admins means more risk of accidental or malicious damage. Keep the circle small.

Tips

  • Use a dedicated server host: Managed hosts often provide DDoS protection, automatic backups, and security hardening, saving you time and effort.
  • Enable two-factor authentication (2FA) on your hosting account: This adds an extra layer of protection against unauthorized access.
  • Use a separate database for plugins: If you run many plugins, consider using a separate MySQL database instead of the default SQLite to improve performance and security.
  • Regularly audit your admin list: Remove inactive or untrusted admins. Use plugins to log admin actions for accountability.
  • Educate your players: Encourage players to report suspicious behavior. A community that watches out for cheaters helps keep the server clean.

Troubleshooting

Players getting kicked for EAC: If EAC is enabled, players must have a legitimate copy of Rust. If they get kicked, ensure their game files are verified in Steam (right-click Rust > Properties > Local Files > Verify Integrity of Game Files).

RCON not connecting: Check that the RCON port is open in your firewall and that the password in your client matches the server config. Also, ensure rcon.web is set to 1 if you’re using a web-based RCON tool.

Server crashes after adding a plugin: Remove the plugin and check the logs for errors. Often, plugin conflicts or outdated versions cause crashes. Update all plugins to the latest versions compatible with your server’s Rust version.

Backups not restoring: Ensure you’re restoring the correct folder structure. The world files are in server.identity and plugin data in oxide/data. Stop the server before restoring to avoid file locks.

Cheaters still getting through: If anti-cheat plugins aren’t catching everything, consider adding more detection plugins or manually reviewing player reports. Also, keep your anti-cheat plugins updated.

Frequently Asked Questions

Do I need EAC enabled for a modded server?

Yes, EAC can be enabled even on modded servers as long as the mods don’t modify game files. Most popular mods are compatible with EAC. Disabling EAC should be the last resort.

How often should I back up my Rust server?

At least once a day for active servers. If your server has many players, consider backing up every few hours. The more frequent, the less data you lose in a crash.

Can I use the same password for server and RCON?

No. Always use different passwords. If one is compromised, the other remains secure. This limits the damage an attacker can do.

What is the best anti-cheat plugin for Rust?

There’s no single best. Popular options include AntiCheat and Vanish for detection, but you may need a combination. Check community forums for current recommendations.

How do I give admin to a player?

In the game console, type ownerid <SteamID64> "name" for full admin, or moderatorid <SteamID64> "name" for moderator. You can find a player’s SteamID64 via steamid.io or in the server logs.

Is it safe to use default ports?

Default ports are more likely to be scanned by attackers. Changing them to non-standard ports reduces automated attacks, but it’s not a substitute for strong passwords and a firewall.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →