How To Protect A Rust Server

Rust servers are among the most attacked game servers. Competition between clans is fierce, wipe days bring lots of attention, and a server that lags or goes offline during raids can lose its players for good. This guide explains how to protect a Rust server in layers.

Why Rust Servers Are Targeted

• Competition. Rival servers and angry players sometimes try to disrupt popular servers, especially at wipe time.
• Raid Disputes. A clan that loses a base can try to punish the server.
• Visible Addresses. Servers are listed publicly with their IP and port.
• UDP Traffic. Rust uses UDP for the game connection, which is easy to flood with fake packets.

Learn the basics in What Is A DDoS Attack?

Layer 1: Network Protection

The largest attacks fill the network connection, and only filtering in front of your server can stop them. For Rust, look for a host that:

• Includes always-on DDoS protection.
• Filters UDP game traffic and not only web traffic.
• Filters in its own network before traffic reaches your machine.
• Lets you manage ports and country blocking if your players come from known regions.

Linceris.com servers run behind DataForest.net DDoS protection. See How DDoS Protection Works.

Layer 2: Close Ports And Protect RCON

Rust uses UDP port 28015 for the game by default. RCON, the remote administration interface, commonly uses port 28016 over TCP, and gives full control of your server.

• Open the game port to everyone, and nothing more than you need.
• Restrict RCON to your own IP address with the firewall.
• Use a long, random RCON password and never reuse it.
• Do not share RCON details with plugin tools or panels you do not trust.

sudo ufw allow OpenSSH
sudo ufw allow 28015/udp
sudo ufw allow from YOUR_HOME_IP to any port 28016 proto tcp
sudo ufw enable

Layer 3: Be Careful With Plugins

Plugins from Oxide (uMod) or Carbon add features, and they run inside your server with full access. A bad one can leak data, crash the server or give someone control.

• Download plugins only from trusted sources and read their reviews.
• Avoid cracked or modified copies of paid plugins.
• Add plugins one at a time and test before wipe day.
• Keep the modding framework and plugins updated after each Rust update.
• Remove plugins you no longer use.

Layer 4: Secure The Machine

1. Run the server under its own non-root user.
2. Use SSH keys and disable password login.
3. Install fail2ban and automatic security updates.
4. Keep the operating system and SteamCMD updated.

See How To Secure A Linux VPS For Your Game Server for the commands.

Layer 5: Prepare For Wipe Day

Wipe day brings the most players and the most attention. Plan for it:

• Update the server, framework and plugins a day early and test them.
• Make sure your hardware has headroom for the player peak. See Rust Server Requirements: RAM, CPU And Wipe Planning.
• Back up before the wipe.
• Check with your host that protection is active, and know how to contact support quickly.
• Keep an eye on traffic graphs during the first hours.

Signs You Are Being Attacked

• Many players get disconnected at once.
• The server disappears from the list, or ping is high for everyone.
• The server's frame rate looks fine, but players cannot connect.
• Your provider's graph shows a spike in incoming traffic.

Make sure it is not just load. A heavy plugin or a full world can cause lag without any attack.

After An Attack

1. Note the time and length of the attack and report it to your host.
2. Tell your players on Discord what happened.
3. Review logs, including RCON and plugin logs, for anything unusual.
4. Change passwords if you think any were exposed.

New To Rust Hosting?

Start with How To Create A Rust Server, then use this guide to protect it. Our VPS packages in Frankfurt am Main, Germany come with DDoS protection included.