How to Host a Dedicated Rust Server for Free (2025 Edition)

Looking to set up your own Rust server without spending a fortune, right?

I’ve been down that road, and let me tell you, it’s not as straightforward as it sounds. You’re probably worried about the costs climbing up or getting messed up in all the technical stuff needed to get your server off the ground.

But what if I told you there’s a way out?

Imagine setting up your server so smoothly, it feels like everything just clicks into place.

You could create a unique spot in the Rust world that players are drawn to, not just for the gameplay but for the community you’ve built.

I know what you’re thinking – it sounds great, but there’s always that nagging fear in the back of your mind.

What if your server becomes infamous for being down more than it’s up, or worse, it becomes a target for security threats?

Let’s tackle this head-on. I’m here to help you navigate through these challenges. We’re not just aiming to avoid the pitfalls; we’re looking to create a Rust server that’s perfect for gamers looking for an epic experience, all without breaking the bank.

Method 1: Cloud Service (The Easy Way)

In case you want to set up a more reliable, scalable, and accessible Rust server, the cloud service method can be a better bet as compared to the DIY method.

Gamers with limited technical expertise can opt for this easy yet step-pronged solution.

rust banner

If you don’t want to know about the easy way to host a Rust server, skip this section and continue with the tutorial.

But if you’re interested, here’s the deal:

Hosting your own Rust server is a great way to learn the game, create base designs, practice, and have fun with a few friends.

It’s also a pain in the ass to manage, and takes a while to setup.

But there’s another problem:

When you host the server on your own PC, it’s going to consume your resources. Your computer not only has to run the game, it also has to run the server and manage everyone connected to the server.

Dedicated Rust server hosting is taxing on your system’s performance, not to mention your internet bandwidth. There are ways to improve your internet speed, but nothing you do will be enough to host more than 5-10 people on the server.

Furthermore, your friends can only connect to the server when it’s running on your PC, meaning you’d have to leave your computer on 24/7 to have a real Rust server that actually attracts a player base.

Quick Tip

If you want to have a real Rust server that can accommodate dozens of people and run 24/7 without compromising performance, paying for Rust server hosting is the way to go.

It’s cheap, fast, and easy. Plus, it’s the only way you’ll be able to host a real Rust server. If you want to host a Rust server the easy way, check out our guide on the best Rust server hosting companies.

If you want to host a Rust dedicated server the easy way, you’re better off investing a small amount to pay for a dedicated server.

Step 1: Choose the right cloud provider.

There are tons of cloud-based service providers that you can use to run a Rust server. In most cases, the obvious picks include the following:

  • Amazon web services for its extensive range of compute instances and an extensive network of data centers.
  • Microsoft Azure for its widest possible range of tailored services and low latency connections.
  • Google Cloud Platform for its extensive infrastructure
  • DigitalOcean for its developer-friendly options supporting customization

You should pick one depending on the player count and server complexity. As for pricing, there are several elements to consider.

For instance, AWS offers a 12-month free program and free trails, S3 storage support, and other perks. Other service providers that offer similar credits and trial packs make better bets.

If you are in the market for cost-effective solutions, it is better to opt for burstable CPU options, including the AWS T-series or the Azure B-series.

Finally, you can pick depending on what kind of pricing you are comfortable with. From long-term commitments to Pay-as-you-Go services, there are several options to choose from. Do note that the best Rust server hosting provider depends on your requirements.

Step 2: Setting up the server

Even though this isn’t DIY, you would still need to set up a server. Here are the associated steps:

Step 2.1: Create a VM instance (as the process involves creating a virtual machine)

  • Log into the cloud service provider’s console, navigate to the compute service section, and choose the right VM.
  • Create a new instance by filling in details regarding the machine type, image, and other elements.

You can choose the VM instance based on the OS you prefer.

Step 2.2: Configure

Even though the cloud service takes care of most elements, you still need to configure it for optimal performance. For Windows, it is about choosing VMs with at least four vCPUs and 8GB RAM in case you wish to create a small-to-medium Rust server. You can scale the hardware accordingly.

For Linux, you can scale similarly, but as the overheads are lower, you might be able to set up larger Rust servers with a bit less power. The SSD component in both cases should be around 100GB as the starting point.

Pro Tip: Rely on tools like Chef, Puppet, and Ansible to streamline the server setup process. These tools allow you to define the server configuration in the form of code, ensuring that you can apply updates and replicate setups with ease.

Another aspect of configuration is network configuration, which involves the following steps:

  • Assigning a static IP to the VM (you can even choose Elastic IP)
  • Setting up firewall rules as was in the DIY method

Step 3: Install and Configure

It is now time to install the server and make it usable to the gamer community. Here are the sub-steps involved:

  • For Linux: Use the right SSH client via the command ssh username@your_vm_ip. Here, the username and your_vm_ip are the ones you would set in the first place while interacting with the VM.
  • For Windows, using tools like PuTTY and entering the static IP address takes care of the SSH connection.

Connecting VM to SSH allows you to access the cloud-based VM from any local PC.

I would be using Xshell as the SSH tool.

Xshell as SSH tool

Updating lists and installing SteamCMD:

As you would be running the VMs remotely, updating package lists will refresh the same and ensure that you have the latest tools to play with. The features steps include:

  • Open the VM-specific SSH terminal or the Xshell.
  • Update the package lists by using the following command — sudo apt update for the Linux distro.
  • Install SteamCMD using sudo apt install steamcmd

You can get all the details as part of Linux’s Game Server interface.

Once installed, you will still need to download the Rust server files, customize the server settings, and even create a startup script to run the VM seamlessly on the local PC. Here are the associated steps:

  • Run the SteamCMD application by typing steamcmd in the command line interface.
  • Log in anonymously using “login anonymous.” (you wouldn’t need a key in this case)
  • Set an installation directory as you did for the DIY method using force_install_dir/path/to/rust_server/, replacing the last bit with the actual path name.
  • Download and install the server files using app_update 258550 validate command
  • Exit the interface with quit

To edit the server files, follow along:

  • Navigate to the Rust directory that you created
  • Create a server.cfg file inside the directory
  • Open the file in Notepad and fill in the specific gameplay details like Your Rust server name, server.worldsize, and other components.

Then, you need to create a startup script to ensure seamless functioning. The steps include:

  • Create a text file termed start.sh
  • Inside the file, type in the following command: (change the password and other details, accordingly)

#!/bin/bash
./RustDedicated -batchmode +server.port 28015 +server.level "Procedural Map" +server.worldsize 3000 +server.maxplayers 100 +server.hostname "Your Server Name" +server.identity "my_rust_server" +rcon.port 28016 +rcon.web 1 +rcon.password "yourpassword"

  • Ensure that you make the script executable using chmod +x start.sh
  • You can then run the ./start.sh script from the server directory.

Step 4: Security and networking

How to make your own Rust server for free isn’t only about connecting with a service provider and connecting the VM to the local PC. You also need to account for the security aspect. Here are the associated steps to configure the security groups and elements:

  • Head over to the console of the cloud service provider and locate the security groups, mostly accessible under the networking or security section.
  • Create a new group and assign a name to it
  • Configure the inbound rules for this group by assigning ports
  • Also, set outbound rules

networking and security options

Do note that online gameplay can make the system or even server vulnerable to Distributed Denial of Service attacks. However, these risks can be handled by:

  • Enabling the DDoS protection as part of the cloud service’s security configuration tasks
  • Configuring protection settings by tweeting traffic thresholds, response strategies, and other metrics.

Note: To protect the SSH or the local PC, you can use tools like fail2ban. Also, while configuring the Rust server settings, doing the same inside a Virtual Private Cloud or VPC makes sense as it isolates and allows you to launch resources without security concerns.

VPC for added security

Here are all the additional command line options and prompts, in case you are unsure as to how the same works:

command line prompts list

Step 5. Launch and Maintain

Once you have set up the Rust server, along with the security considerations, it is time to launch the same. Here are the associated steps:

  • You can start the launch process using the startup script you created earlier — start.sh for Linux and StartServer.bat for Windows.
  • You can simply type in the relevant script name in the command line interface, and the same starts using your predefined configurations.
  • You can use the dashboard of the cloud service provider to monitor the metrics associated with the server usage.

To maintain the server, you should initiate routine checks and set automated backups by tweaking a few settings at the cloud service provider’s end. However, to initiate regular updates, you need to log into the server using SSH, run SteamCMD using the command line, and type in app_update 258550.

And that should take care of free Rust server hosting (provided you sign up using a trial plan).

Method 2: DIY (The Hard Way)

If you prefer hands-on experience with the server while being able to control and customize even the smallest of server requirements, the DIY method can be useful.

This method makes sense if you are a true gaming enthusiast and interested in hosting games for a group of friends, all while focusing on unique environments.

Required tools

Hardware requirements:

  • A mid-range to high-end processor featuring at least four cores. The focus here should be on getting a processor with a high single-threaded clock speed. Intel Core 11th gen and higher models or AMD Ryzen 7 and higher can be considered.
  • When it comes to memory management, you should at least get a 16GB RAM module for making and running your own Rust server. This applies to every small to medium-sized server. For larger consortiums, even 32GB might be needed.
  • Rust servers are better off with fast storage solutions. In most cases, traditional SSDs are more than enough, but if you are serious about gaming and quality, NVMe SSDs with excellent read/write capabilities should be preferred.
  • You would also need an ultra-fast internet setup, with the connection speed going as high as 20 Mbps, for the smoothest possible gaming experience. It is advisable to connect with the ISP to get hold of a dedicated IP address for your Rust server for additional stability.

Software prerequisites:

  • Firstly, you need the latest version of Windows installed, Windows 10 or 11. Plus, every latest update should be installed.
  • The command prompt access should be active, or you can even ensure PowerShell access precisely to be able to execute scripts, commands, and system-level tasks.
  • Ensure that your system is running at least .NET v4.5, as several elements of the Rust setup, plugins, third-party tools, and more might rely on the same to work seamlessly.

Do note that having a Windows OS isn’t compulsory. If you are more familiar with the Linux ecosystem, the following software prerequisites might make sense:

  • You might want to have a modern distro like Ubuntu 20.04 LTS or higher installed. It is better to have a Long Term Support or LTS version installed to focus on stability, compatibility, and security.

Ubuntu 22043 LTS version

(I tested using the Ubuntu 22.04.3 LTS version)

  • If you are unfamiliar with Linux but willing to give it a try for seamlessly managing Rust, command-line proficiency might be needed.

Following these hardware and software prerequisites can help you with Rust customization and control needed for adjusting elements like day/night cycles during gaming, player-vs-player settings, and even moderating the player base by enforcing specific rules.

Step 1: Setting up the Server

To set up the Rust server via the DIY method, you first need to zero in on the OS.

If on Windows, the steps involve:

downloading SteamCMD

  • Then extract the contents to a dedicated steam folder — C:\SteamCMD

folder for SteamCMD

  • Launch the command prompt and navigate to the SteamCMD folder
  • The command to run here would be steamcmd.exe which would then complete the installation

For Linux, follow the mentioned steps:

  • Install SteamCMD via the package manager. Everything happens via the command line, so the command to type here would be: sudo apt install steamcmd
  • Once done, run SteamCMD and install updates if needed.

SteamCMD in Linux

Step 1.1: Creating update scripts

While setting up the server is crucial, creating an update script is as important. This way, you can keep your server updated with new patches and game updates, without having to manually do the same. The update process is automated and differs based on the OS in play:

For Windows, you need to open the notepad and type in the following commands:
@echo off
start /wait C:\SteamCMD\steamcmd.exe +login anonymous +force_install_dir C:\RustServer\ +app_update 258550 validate +quit
echo Rust server has been updated.

Note: You can update the paths (C:\SteamCMD or the C:\RustServer, depending on the names you have selected)

Once you have typed in the code, save the Notepad file using the .bat extension. After that, whenever you want to update the server, simply right-click on the .bat file and select “Run as administrator” to get the process underway.

For Linux, the first step would be to open the terminal and then use Vim, nano, or any other text editor. Or, you can simply type in “nano update_rust_server.sh” to create a script file.

Once done, type in the following code into the editor: (Linux only)
#!/bin/bash
/path/to/steamcmd/steamcmd.sh +login anonymous +force_install_dir /path/to/rust_server/ +app_update 258550 validate +quit
echo "Rust server has been updated."

Do note that the path names can vary depending on where you wish to have the same on your computer. Once you type in the editor, make the same executable by running the following command:
chmod +x update_rust_server.sh

Once done, you can simply type in the following command to execute the update script whenever you feel like it!:
./update_rust_server.sh

Notably, having an update script handy is convenient and efficient.

Post the update-script discussion, it is necessary to download the server files. This process initiates immediately after you have installed SteamCMD. Post-installation, you can launch the SteamCMD, use “login anonymous as the command, type in app_update 258550 validate and download the server files. This process remains the same for Windows and Linux.
Note: You can download the pre-defined Rust server setup, open the same to access the batch file, and then move it into the directory folder of the SteamCMD.

Step 2: Configuration and Customization

Once you have set up the server, using the steps mentioned above, you would want to customize the same better. This way, you can get the most out of the gameplay. And the process isn’t as complicated. The idea is to create standard startup scripts, enabling remote server management and utilizing tools for continuous server operation.

Phase 1: Creating the startup script

The process varies for Windows and Linux. Let us address both scenarios:

For Windows:

  • Head over to the Rust directory — the C-drive path that you created in the first place.
  • Within the directory, right-click and create a .bat document (using Notepad)
  • Name it StartServer.bat
  • Once done, right-click on the same, open to edit, and insert the following document:

RustDedicated.exe -batchmode +server.ip 0.0.0.0 +server.port 28015 +server.tickrate 30 +server.hostname "Your Server Name" +server.maxplayers 50 +server.worldsize 3000 +server.saveinterval 300 +server.identity "my_server"
You can customize the parameters like .hostname, .maxplayers, and .worldsize components depending on your preferences.

For Linux:

  • Open the terminal and then head over to the Rust directory
  • Open the editor and name it nano StartServer.sh (provided you are using nano as the editor)
  • Once the editor is open, like Windows, type in the following command (adjusted for Linux):

#!/bin/bash
./RustDedicated -batchmode +server.ip 0.0.0.0 +server.port 28015 +server.tickrate 30 +server.hostname "Your Linux Server Name" +server.maxplayers 50 +server.worldsize 3000 +server.saveinterval 300 +server.identity "linux_server"

Phase 2: Enabling Web RCON

If you wish to install Rust on Windows, you are better off installing the Web-based RCON or the Remote Console. As the name suggests, this helps administer and manage the Rust server remotely via the web interface.

To include the same, head over to the .bat file that you created in the first place and add the following parameters:

+rcon.web 1 +rcon.ip 0.0.0.0 +rcon.port 28016 +rcon.password "your_rcon_password"

You can even use third-party shared server tools like GameServers to activate web RCON.

GameServers Rust RCON

Phase 3: Making the Script Executable

Just like how you would prepare an executable update script, the config script also needs to be made executable in case you want it to run in the background. To do the same in Linux, use the command line to run the following:

chmod +x StartServer.sh

Another aspect while trying to work with Linux is to use the tmux or screen tools to ensure that the processes related to configuration can seamlessly run in the background. To use tmux, which is a more convenient option, install tmux using the package manager. Do note that tmux can also be used with Windows.

Once tmux is installed, start a session using the following command: Tmux new -s rust_server

Post that, run /StartServer.sh.

You can detach yourself from the process once it’s done by typing ctrl and b and then d. To configure the background settings, you can always reattach using the following command:

tmux attach-session -t rust_server

Step 3: Going Live

One of the many Rust server requirements would be to ensure that it goes live. Here is how to take care of the same:

Step 3.1: Port forwarding (this method allows others to join in)

This step allows you to connect or redirect game traffic from the internet to the Rust server. Here is how you can go about the same:

  • Access the admin page of the router by using the web browser, feeding the IP address, and typing something like this URL: 192.168.1.1 or something relevant.
  • Login using credentials, and head over to the port forwarding system.
  • You can change the port forwarding rules depending on the scenarios in play. For forwarding game traffic, change the UDP port or port ID 28015 rule, and for RCON, focus on the TCP or the 28016 port. Plus, for the Rust+ app itself, focus on the TCP port 28082.

set port fowarding for rust

Once the rule changes are made, apply and save the changes.

You can use the command line prompt to find the router details and other insights:

router details

Step 3.2: Configuring the firewall

This step is necessary to allow traffic movement to the specific ports. Here are the associated steps:

  • Access the settings by heading over to the Windows Defender Firewall. For Linux, you can access UFW or the iptables to manage the firewall.
  • For Windows, the next step would be to select Inbound rules and select new rules while playing around with the Firewall. The idea is to choose the port, assign forwarding rules to them, and apply the firewall settings to the entire consortium.
  • In the case of Linux, you can use commands like the sudo ufw allow 28015/udp
    and other port settings following each command to set firewall rules for specific ports.

port for rust

To live, open the Rust app, type F1 to get access to Rust’s command line interface and type in the following command connect localhost: 28015

Feeding the command > status gives you the status of the server, like the number of active players and more.

check active players

Step 4. Maintenance and Updates

If you wish to opt for the DIY way of free Rust server hosting, you also need to take care of server maintenance and updates. These include the following steps:

4.1 Focus on regular updates.

Focusing on regular updates is necessary if you wish to maintain and run servers. Here is the command to process the same:

steamcmd +login anonymous +force_install_dir /path/to/rust_server/ +app_update 258550 validate +quit

This command lets you log in anonymously, checks for updates and installs the same.

4.2 Automating updates

On Windows, you can train the task scheduler to take care of automatic updates. And on Linux, you can automate the same using the “cron” job.

4.3 scheduling backups

To schedule backups, it is necessary to locate the data directories and use tools like “rsync” to sync the server data with the existing backups.

5. Troubleshooting

By now, most of the DIY concerns related to Rust’s private server setup should be taken care of. However, you should take care of the possible issues and the strategies to handle them. Some of the more obvious issues include configuration errors, server crashes, and connectivity concerns. In some cases, the server might not even be visible in the game list. To combat the same, the possible troubleshooting ideas include:

  • Port forwarding rechecks
  • Rechecking firewall configuration
  • Checking the server performance
  • Checking the internet connection
  • Rechecking game updates, mods, and configuration

It is advisable to consult the server logs while troubleshooting, as you can get detailed insights related to server operations and errors.

Batch File Commands for Rust Servers

Here’s a list of batch file commands for Rust servers and what they do:

  • echo off Tells the server not to display all executed batch commands.
  • :start Start point of the server.
  • goto start Tells the server to restart upon shut down.
  • -batchmode Opens Unity in non-GUI mode.
  • +server.port 28015 Runs Rust’s default port for client connection.
  • +server.seed X The seed determines the shape of a procedurally generated world (kinda like Minecraft), and the value ranges are 0-2147483647.
  • +server.level “Procedural Map” Picks the server map. You can replace “Procedural Map” for other maps like “SavasIsland,” “SavasIsland_koth,” “Barren,” and “HapisIsland”.
  • +server.worldsize X Select a world size between 1000 and 6000.
  • +server.maxplayers X Choose the number of player slots the server has.
  • +server.hostname “Server Name” Choose the name your server will display on the server list.
  • +server.description “Server Description” Choose the description your server will display on the server list.
  • +server.url “https://yourwebsite.com” If a website is placed here, a “View Webpage” button will appear when connecting to the server.
  • +server.headerimage “Image link” Paste an image link that will be used as the background image when connecting to the server.
  • +server.identity “server0” The parent name for all server files.
  • +rcon.port 28016 Rcon port for client connection.
  • +rcon.password “password” Rcon access password. It does not allow spaces or special characters.
  • +rcon.web 1 Rcon WebSocket connection mode.

Promoting Your Server

If you plan on trying to turn your dedicated server into a public masterpiece there are a couple of routes you can take to promote your server.

First of all, before you put it out for the world to see, come up with a catchy server name and description for players to see on the server list. You can even change the loading picture to make your server stand out from the rest.

Second, take advantage of all the online resources at your disposal. Forums like the official PlayRust and Rust Server Directory subreddits are great places to start.

You can also post on Rust’s official discord server and try to garner a following there. If officiality isn’t your thing, there are hundreds of player-ran servers out there to advertise on.

Dedicated Rust Server vs Rust Server Hosting

Each type of hosting has its own tradeoffs. Use these pros and cons to choose whichever fits your Rust server needs best.

Dedicated Rust Server

Dedicated hosting, for the most part, is best for when you want to host a small server with a couple of friends.

Trying to grow past that small player count is difficult with the limited resources that your PC and internet can provide.

Pros:

  • Free
  • Full customization freedom
  • User serviceable

Cons:

  • Little to no protection
  • Uses personal resources like processing power and internet bandwidth
  • Requires a little know-how to set up and manage
  • Only fit for a small player count

Rust Server Hosting

While you have to pay a monthly fee to use the service, purchasing a host allows you to run much bigger and faster servers than you ever can on a dedicated connection.

Pros:

  • No strain on your internet or computer
  • Much faster
  • Included support team
  • Ease of use and quick setup

Cons:

  • Paid service
  • May limit control
  • May not allow direct access to server files

FAQs

What is the cheapest way to host a Rust server?

The cheapest way to host a Rust server is by using an old PC. Once there, you can rely on shared game server hosting plans or even subscribe to the free tiers offered by the cloud providers. Another approach would be to get community funding — from individuals who would be using the server to play.

How do I host a solo Rust server?

To host a solo Rust server, you would need your own hardware. Or, you can even rely on the paid plans offered by cloud service providers like Azure and AWS. In the DIY method, you need to install the Rust server files using SteamCMD.

How much RAM does a Rust server need?

For setting up a small server, 8GB RAM is sufficient. In case you wish to set up a medium-sized unit with standard maps and a decent player count, 16GB is recommended. For large servers, 32GB ensures optimal performance.

How much does a Rust server cost?

For the standard do-it-yourself approach, there aren’t any overheads except the internet costs. However, if you wish to install a server using dedicated server providers, which would also take care of DDoS threats, you need to spend anywhere between $10 to $100. For standard cloud hosting, $20 to $200 can be the associated cost, while for shared hosting, you can start as low as $10.