Rust server.cfg, Ports and Server Browser Settings
Put Rust settings in the right place, separate game, query and RCON ports, and make the server visible without unnecessary exposure.
A public Rust server relies on three separate services: the game port, the query port used by the browser, and RCON for administration. A common mistake is to open 28015 and reuse it everywhere. Facepunch states that game and query are UDP, must differ and must both be reachable.
Separate startup settings from server.cfg
Keep settings required before configuration loads on the startup line: identity, ports, RCON and world. Put gameplay and presentation variables in:
rust/server/IDENTITY/cfg/server.cfg
IDENTITY is the value of +server.identity. Do not add + or - prefixes inside server.cfg. Rust reads this file on startup and does not rewrite it for you.
server.hostname "My Rust server"
server.description "Vanilla, monthly wipe, active staff"
server.maxplayers 50
server.saveinterval 300
server.pve false
After editing, restart or run server.readcfg for reloadable variables, then inspect their current console values. Ports and identity are best validated after a restart.
Configure ports without collisions
Explicit startup example:
RustDedicated -batchmode \
+server.identity "production" \
+server.port 28015 \
+server.queryport 28017 \
+rcon.port 28016 \
+rcon.password "UNIQUE_PASSWORD" \
+rcon.web 1
| Service | Example | Protocol | Purpose |
|---|---|---|---|
| Game | 28015 | UDP | Player connections |
| Query | 28017 | UDP | Browser information and listing |
| RCON | 28016 | TCP | Remote administration |
| Rust+ | Configured value | TCP | Companion app when enabled |
When server.queryport is omitted, Rust derives it from the highest game or RCON port. Setting it explicitly is easier to document and troubleshoot. Never assign the same value to game and query.
Open and test the network
Give the host a stable LAN address
Create precise rules
Wait for startup to finish
Server startup complete. An initial map generation can otherwise look like a closed port.Test from another network
Check browser visibility
Missing server: quick diagnosis
Read the startup line printed by the panel and the logs, not just the intended configuration. Check in order: live process, Server startup complete, game UDP, direct connection, separate query UDP, browser filters, server version and detected location.
Facepunch uses MaxMind for country detection. If the country is wrong, submit a GeoIP correction and contact the provider instead of changing advertised addresses at random. Multiple instances on one machine need a unique identity and complete non-overlapping port set.
See the RCON administration guide for roles and commands, and the backup and update guide before larger maintenance.
Avoid Rust port-forwarding problems
Compare Rust plans with preconfigured networking, a console and a stable public address.
Frequently asked questions
Which Rust ports must be opened?
Why does direct connection work but not the browser?
Can every setting go in server.cfg?
Primary source: Facepunch — Creating a server.
Ready to launch your Rust server?
Here are the best Rust hosting deals right now, promo codes included. Still unsure? Our quiz finds the ideal host for you in under 2 minutes.
My box 12
Minestrator
Specifications
Compatible games
Features
- ✓DDoS Protection
- ✓Backups
Wood
Shockbyte
Specifications
Compatible games
Features
- ✓DDoS Protection
- ✓Oxide mod support
- ✓Instant Setup
- ✓24/7 Support
Rust
OptiNAS
Specifications
Compatible games
Features
- ✓Environ 30 joueurs
- ✓Minimum : 6 vCPU et 16 Go de RAM
- ✓Conseillé : 6 vCPU et 16 Go de RAM
- ✓Plugins et mods possibles selon le jeu
- +2 more features