Revision Difference
Creating_a_hidden_whitelisted_server#529066
<cat>Play.Hosting</cat>⤶
<title>Creating a hidden whitelisted server</title>⤶
⤶
This guide will cover basic steps to set up a hidden whitelisted server aimed at advanced users with root access, it will not cover installation.⤶
⤶
The purpose of this guide is to help server owners avoid DOS attacks and the server being discovered publicly. ⤶
⤶
Rust by default doesn't offer a whitelistng system and Umode/Oxide must be used.⤶
⤶
⤶
# Requirements⤶
* Strong knowledge of server hosting⤶
* Knowledge of Rust server installation⤶
* Knowledge of Oxide/Umod installation⤶
* Knowledge of Windows/Linux firewall-config⤶
⤶
# Server Hosting⤶
While this guide will advise on remaining hidden it's strongly recommended you use the best server hosting around with the ability to change IPs quickly, strong DDOS protection and no null routing. ⤶
⤶
Facepunch uses OVH Gaming for years with great success and comes highly recommended. ⤶
⤶
# Ports⤶
Highly advised to use nonstandard ports, this will help minimise attack vectors.⤶
```markdown⤶
server.port⤶
rcon.port⤶
```⤶
⤶
# Steam queryport⤶
The Steam queryport should be blocked at all times otherwise the server can be discovered and seen within the Steam master server list and within Rust server listings. ⤶
```markdown⤶
queryport⤶
```⤶
⤶
# Users Visablity⤶
At all times users should be set to "Invisible" as not to display the Game, IP and port on their Steam profile.⤶
⤶
# Users Connecting⤶
It's common for content creators to accidentally show sensitive on live streams so it's highly reccmended connecting to a server via binds:⤶
⤶
Bind this off stream / out of view of viewers (F1 command)⤶
bind f6 "client.connecthidden IP:PORT;console.clear" ⤶
The streamer will just need to press F6 from the main menu to connect there after and never leak server info.⤶
⤶
# Other helpful Server Commands⤶
```markdown⤶
censorplayerlist true⤶
```⤶