How To Create A Rust Server

Rust is a survival game where servers are the whole experience: the map, the rules, the wipe schedule and the community. Hosting your own server gives you full control, and it is not hard once you know the steps. This guide shows how to run a Rust server on a VPS and what to plan for.

What You Need

• A server. A VPS with a fast CPU, enough RAM and NVMe storage. See Rust Server Requirements for sizing.
• An operating system. The Rust server runs on Windows and Linux. Many owners choose Linux because it is lightweight and good for long-running servers.
• SteamCMD. This is Valve's command line tool that downloads and updates game servers. You install it on your machine.
• Open ports. Players connect over the game port, and you may also use RCON for remote administration.

Step By Step On Linux

1. Prepare the system. Update packages, create a normal user to run the server (not root) and set up a firewall. Our guide How to Secure a Linux VPS covers this.
2. Install SteamCMD using your distribution's package manager or Valve's instructions. You may need to add 32-bit libraries.
3. Download the Rust server. The Rust server's Steam app ID is 258550. A typical command looks like this:

   steamcmd +force_install_dir /home/rust/server +login anonymous +app_update 258550 validate +quit

4. Write a start script. It sets the server name, map size and seed, maximum players, the ports and the identity folder. Check the official Rust server documentation for the current list of options, because they can change between updates.
5. Start the server. The first start generates the map, which can take a while. Run it inside a terminal manager such as screen or tmux, or as a service, so it keeps running after you disconnect.
6. Connect and test. Join through the in-game console with your server address and port.

Ports

The default game port for Rust is 28015 over UDP. RCON commonly uses 28016 over TCP. Only open the ports you actually use, and restrict RCON to your own IP address with a strong password, because RCON gives full control of the server.

Adding Mods And Plugins

Many community servers use a modding framework such as uMod (Oxide) or Carbon to add plugins like kits, teleport, shop systems or anti-cheat helpers. After installing the framework, plugins are small files you place in a plugins folder. Be selective. Each plugin uses some server time, and badly written ones can cause lag. Test new plugins before you put them on your main server.

Wipes

Rust servers reset on a regular schedule. A map wipe creates a fresh map and removes player bases, and a full wipe also resets blueprints. Rust also pushes a forced wipe with its monthly game update, so every server is wiped at least once a month. Plan your schedule around this, tell your players in advance, and back up before each wipe. Wipes also change resource use, which we cover in the requirements guide.

Updates

When Rust updates, servers must update too, otherwise players on the new version cannot connect. Use SteamCMD to update the server, and update your modding framework and plugins as well. Many owners schedule restarts and updates for a quiet time of day.

Protect It From Attacks

Rust servers are often targets of DDoS attacks, especially popular ones. Choose a host that filters traffic on the network, so attacks never reach your machine. Read How DDoS Protection Works for Game Servers to know what to look for. Linceris.com servers run behind DataForest.net DDoS protection.

Choosing A Package

Small and medium servers run well on a strong VPS. Large maps with many players and plugins need a bigger package with more cores and memory. See our VPS packages, hosted in Frankfurt am Main, Germany.

Related Guide

See How To Protect A Rust Server for the matching guide.