How to join a Rust server
Join a Rust server from the F1 console with client.connect IP:gameport, through the in-game browser, or with Steam's +connect launch option. Use the game UDP port from berrybyte Overview, then handle passwords, queues, and common connection errors.
The quickest route into a Rust server is its direct address. Launch Rust, open
the F1 console, and send client.connect to the server's game port:
client.connect 203.0.113.10:28015Replace the example with the full host:port shown by your host. Facepunch's
console command reference
documents direct connections, and its
server setup guide
identifies server.port as the UDP port used by players.
Find the address on berrybyte
Open your Rust server
Sign in to the berrybyte dashboard, then select the Rust server from My Servers.
Check its state on Overview
Wait until Overview shows the process as running. Open Console and find the exact line
Server startup complete. Facepunch uses that message as the point when a dedicated server
is ready for connections.
Copy Server address
Return to Overview and copy Server address. Keep the port attached. An allocated
address might look like chicago.example.berrybyte.net:28142.
rust-overview-server-address.pngberrybyte opens the assigned network allocations. A self-hosted machine needs
matching firewall and router rules. The address on Overview remains the source
of truth for a hosted server, so the default 28015 belongs only in examples.
Join through the F1 console
Start Rust from Steam
Let Steam finish any pending Rust update, then wait for the main menu.
Open the client console
Press F1. Enter client.connect IP:gameport with the address copied from Overview.
Complete the connection
Press Enter and keep the console open while Rust authenticates, downloads the map, and loads the world. Supply the server password if a prompt appears.
For a server running on the same computer as the game client, Facepunch also
documents localhost:
client.connect localhost:28015localhost reaches the current computer. Friends need your public address and
the forwarded game UDP port.
Use client.connecthidden IP:gameport when a stream or recording could expose the address.
Facepunch describes this command in its
hidden server guide.
Use the in-game server browser
Open Play Game, then choose the section that fits the server. Community servers generally appear under Community. A server running Oxide, uMod, Carbon, or gameplay-changing plugins usually belongs under Modded. Search for the exact hostname and clear active filters that exclude its map, region, or tags.
The browser relies on the query port. A fresh listing can arrive after the process becomes playable, which makes F1 direct connect useful during first boot. Favoriting the entry gives players an easier route on later visits. Facepunch explains the available filters in Server Browser Tags.
A hidden server intentionally blocks its query path and will stay out of public listings. Players can still use a direct address when the game port remains reachable.
Connect automatically from Steam
Steam can pass a launch option to Rust when it opens. In the Steam Library, right-click Rust, choose Properties, and enter this in Launch Options:
+connect 203.0.113.10:28015Valve documents where launch options live in Steam Support. Replace the example address with your allocated game address. Remove the option when you want Rust to open at its normal menu.
Choose the correct port
Rust commonly has these allocations on a default self-host:
| Purpose | Common default | Protocol | Used by |
|---|---|---|---|
Game port, server.port | 28015 | UDP | Players joining the world |
RCON port, rcon.port | 28016 | TCP | Remote administration clients |
Query port, server.queryport | 28017 | UDP | Public browser and query services |
The query default follows 1 + max(server.port, rcon.port) when it has no
explicit value. With game 28015 and RCON 28016, that calculation produces
28017. Facepunch requires separate game and query ports, with UDP reachability
for both. RCON uses TCP and carries administrative traffic.
Share the game address with players. Treat the RCON password as a secret and keep the RCON allocation for trusted administration tools.
Handle a password, queue, or full server
A protected server asks for its password during connection. Copy the value exactly, including capital letters and punctuation. On berrybyte, owners can check the configured password under Settings → Game Settings.
When the active player count reaches server.maxplayers, Rust may hold another
player in queue. Leave the client connected so the position can move as slots
open. Server owners can run status in Console to inspect current players
and the configured capacity. Administrators and players with queue privileges
can behave differently according to the server's access setup.
Read immediate connection errors
Connection Failed or connection attempt failed
Confirm the process has printed Server startup complete. Copy the address again, then
verify the client and dedicated server received the same Rust update.
Disconnected: wrong connection protocol
Steam has different builds on the client and server. Update each side to the current public branch, restart the dedicated process, and reconnect.
Server is full or queue does not advance
Check status from the server console. Wait for an open slot or ask the owner to review
server.maxplayers and queue permissions.
Server disappears from search
Direct connect with the current game address. The listing needs its separate UDP query port and may take time to refresh after a restart.
Only one player keeps failing
That player should restart Steam, update Rust, disable a VPN for one test, and retry through F1 with the current address.
The ordered diagnostic continues in Can't connect to a Rust server. For crashes, save damage, and plugin trouble, use Common Rust server issues.
Frequently asked questions
How do I join a Rust server by IP?
Open Rust, press F1 at the main menu, enter client.connect IP:gameport, and press Enter. Copy the complete Server address from berrybyte Overview because hosted servers often use an allocated game port instead of 28015.
Where is my berrybyte Rust server address?
Open the server in the berrybyte dashboard and copy Server address from Overview. The value contains the host and allocated game UDP port in host:port form.
Which Rust port do players connect to?
Players connect to the UDP game port set by server.port. A default self-host commonly uses 28015. RCON commonly uses TCP 28016, while the query port commonly becomes UDP 28017 when the defaults are used.
Why is my Rust server missing from the server browser?
Wait for Server startup complete, then allow time for the listing to refresh. A public self-host also needs a distinct UDP query port open. Direct connect through F1 gives you a useful test while the browser listing catches up.
Can I join a full or password-protected Rust server?
Enter the exact password when Rust asks. A full server may place you in its queue, so leave the connection open and watch your position. Ask an owner to confirm server.maxplayers if the queue never advances.