This guide will cover the steps for creating a private RUST server. By the end of this guide, the server owner will have installed a uMod plugin that rejects player connections that have not been granted permission to the server and allows those players that have.
![]() Creating a private RUST server
The Rust server can be taxing on your host but maybe not as much as you would think. As a baseline a 3 square km (default gen size) map freshly generated will run at close to 2 gigabytes of ram. After some stress testing and 150k entities later, can use 6+ gigabytes of memory. So I would suggest having at least 7 gigs allocated per server. However, it's not always clear what specs you're getting, and you can run into congestion issues if your server suffers heavy load. If you're looking.
Server owners may wish to create a private RUST server for a variety of reasons, such as:
Whatever the reason, it’s certainly helpful to have a staging ground set up before allowing players to connect to a server that’s currently being configured.
In order to begin, there are two pre-requisites:
Steps for creating a private RUST serverStep 1: Locate and download the whitelist plugin
Navigate to the uMod page for Wulf’s Whitelist plugin, then click on the download button. This will download the latest version of the plugin, automatically saving the file
Whitelist.cs to your computer.
Note that this guide uses a specific plugin, but other whitelist plugins will work as well, as long as they are compatible with RUST.
Step 2: Install the whitelist plugin
Once the whitelist plugin is downloaded, make sure to save the RUST server and stop the server process.
For this step you must have access to one of the following:
Then in the RUST server’s root directory, locate the oxide folder. Inside of the oxide folder look for another folder labeled “plugins”. The folder’s path will look similar to this:
Then copy or upload the
Whitelist.cs file into this folder.
Step 3: Configuring the whitelist plugin
This plugin makes use of the Oxide permissions system, meaning that whitelist permissions are performed through granting or revoking access to permission groups or individuals. This guide does not walk through the uMod (Oxide) permission system, only through what is necessary to get the Whitelist plugin working.
There are two default groups with uMod (Oxide):
The plugin automatically grants access to the admin group and denies access to the default group. These settings can be modified in the plugin’s configuration file located below:
Step 4: Granting whitelist permissions
After the Whitelist plugin is installed, start up the RUST server. Once the server has finished initializing, perform a quick test of the permissions set to the admin group.
Copy the line below into the server console and press enter:
oxide.show group admin
The server console will return the following:
Now grant the admin group the
whitelist.allow permission. Copy the line below into the server console and press enter:
oxide.grant group admin whitelist.allow
The server console will return the following:
Test that the admin group has the newly added
whitelist.allow permission. Copy the line below into your server console and press enter:
oxide.show group admin
![]()
The server console will return the following:
Alternatively, to manually whitelist a player copy the line below into your server console and press enter:
oxide.grant user 64_bit_steam_id whitelist.allow
The server console will return the following:
To revoke the whitelist access, copy the line below into your server console and press enter:
oxide.revoke user 64_bit_steam_id whitelist.allow
The server console will return the following:
Step 5: Verify proper permission functionality
Below is the message that the non-whitelisted player will receive:
This is the default text provided for the rejection message and can be changed in the plugin’s language configuration file, located below:
Below is what the server side sees when a non-whitelisted player attempts to join:
The next step is to verify that whitelisting works by granting whitelist permission to a player. Copy the line below into your server console and press enter:
oxide.grant user 64_bit_steam_id whitelist.allow
The server console will return the following:
Next, have the player attempt to connect now that they are granted the whitelist permission:
Summary![]()
Now that the whitelist plugin has been successfully installed and configured on the RUST server, players and oxide groups can now be whitelisted as desired. This plugin is often used in tandem with 3rd party subscription services that grant and revoke permissions for subscribing players.
Initial Setup
This bit will be the longest part of the guide but will serve you well in terms of the security of your server. This will be mainly focused on people who aren’t familiar in terms of security or Debian in general.
mkdir ~/.ssh
chmod 0700 ~/.ssh
touch ~/.ssh/authorized_keys
chmod 0644 ~/.ssh/authorized_keys
nano ~/.ssh/authorized_keys
Now head back to PuTTYgen then right click inside the box with lots of characters and press select all then copy. Now head back to PuTTY where you left off at the nano editor and right click to paste your public key in then do ctrl+o -> enter -> ctrl+x.
Now type “nano /etc/ssh/sshd_config” then ctrl+w then “PasswordAuth” then enter. Now remove the hash and change the yes at the end to a no. Now page down to the bottom and change UsePAM to no. Now ctrl+w and do type PermitRootLogin and simply change it to “without-password”. Now press ctrl+p (save) and ctrl+x (exit) and then finally type “service ssh reload”
Now you just need to open PuTTYgen back open and save the public and private key in a folder somewhere safe. Now close PuTTY and reopen it then simply on the left side goto Connection -> SSH -> Authentication then browse and select your private key file that you just saved. Once you’ve done that head back to Session then click Default Settings then Save then open for a passwordless login.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |