Rust: Can't connect to server — every fix
Fix a Rust connection in the right order. Wait for Steam registration, match the client and server protocol, paste client.connect with the allocated game port, share the password, then clear a stale server-list cache.
If Rust says Connection Failed, work through these checks in
order. Do not wipe the map or delete server.cfg first. The usual
post-restart failure is a server that has not finished
registering with Steam.
Stop as soon as one fix works. If you are helping somebody else, test with one player before asking the whole group to retry.
1. Wait for Steam registration
A Rust dedicated server can show as running while Steam still has no listing. Joins during that window fail even when the address is correct.
Confirm Overview shows running
On berrybyte the process must be running, not stopped or still updating.
Ask Console for status
Run status in Console. Wait until the hostname, map, and
player count print without a registration error.
Restart once to re-announce
If the server has been up for several minutes and still refuses everyone, restart it so Steam gets a fresh announce.
New public listings can take 10 to 15 minutes to appear in the browser. Direct connect does not need the browser, but it still needs Steam's session. If you do not want to watch that handshake, rent a Rust server with the live address on Overview.
2. Match the client and server protocol
Facepunch ships protocol changes with forced wipes. The Steam client often updates before a dedicated server that is still on last month's build.
Update the player's game
Close Rust completely and let Steam finish the update. Opting into a beta branch that the server is not on will also fail.
Update the dedicated server
Stop the server. On berrybyte, Auto Update pulls the
current dedicated build (258550) on the next start.
Restart once after the wipe patch is live. If you self-host:
steamcmd +force_install_dir /path/to/rust +login anonymous +app_update 258550 validate +quitStay off the wrong staging branch
A server pinned to a staging or relic branch will refuse the public client. Both sides must be on the same branch.
3. Join with client.connect and the allocated port
The in-game browser is optional. The reliable test is the F1 console.
Copy the current address
On berrybyte, copy Server address from Overview. Do not
assume port 28015.
Run client.connect
Launch Rust, press F1, paste client.connect host:port,
and press Enter. On berrybyte the How to join dialog already
builds that command.
Do not test with 127.0.0.1 from another PC
Use the public address. Loopback only works on the machine that is running the process.
See Common Rust server issues for crashes and plugins after you can join.
4. Check the UDP game port
Rust needs its UDP game port reachable from the internet. The Steam browser also needs the query port. TCP on the same numbers does not create a working game path.
Use the port the server bound
On berrybyte, Overview is the source of truth. On a
self-hosted box, read +server.port from the launch
command.
Forward that UDP port (self-host)
Every firewall and router between the machine and the internet must allow UDP on the game port and the query port.
berrybyte opens the allocated ports, including RCON and Rust+. Self-hosters who are fighting NAT can rent a Rust server that already has them reachable.
5. Share the password and confirm the queue
A passworded Rust server rejects a blank or mistyped password at the prompt. A full server looks similar if the player is not waiting in queue.
Send the exact password
Copy it from Settings → Game Settings. Check capitalisation and characters that chat apps rewrite.
Check player cap
If status shows the server is full, the next join waits
in queue or fails. Raise the billed slot cap or wait.
6. Clear a one-player failure
If everyone else is in and one client is not, the server is reachable.
Skip the browser
Have that player run client.connect with the current
address instead of searching a cached list.
Disable a local VPN or firewall briefly
A client-side block is the usual one-player failure.
Verify Steam is up
Check steamstat.us before assuming the dedicated server died.
If none of the six fixes worked
Confirm status prints a hostname. Then check the leftover
causes:
- An Oxide or Carbon plugin that kicks on connect. Disable the framework for one test join.
- A banned SteamID in
bans.cfg. - EAC failures on a modified client.
- Check berrybytestatus.com.
Frequently asked questions
Why can't I connect to a Rust server?
Wait until the dedicated server has registered with Steam, then match the protocol version. After a forced wipe update the client often updates first. If those match, join with client.connect and the allocated UDP game port, share the password, and clear a stale browser cache.
Why does Rust say Connection Failed right after a restart?
The process is up but Steam has not finished listing it. This is the usual post-restart gap. Wait for the console to finish, or restart once more to force a re-announce. Direct connect with client.connect still needs that registration to complete.
How do I join a Rust server by IP?
Launch Rust, press F1, and run client.connect host:port using the address from Overview. On berrybyte that value already includes the allocated game port. Do not assume 28015.
What port does a Rust dedicated server use?
One UDP game port, commonly 28015 on a default self-host, plus a query port for the Steam browser. berrybyte allocates those ports and opens them. Forward the ports the process actually bound.
Why can my friends join a Rust server when I cannot?
The server is reachable. The failing client usually has a stale Steam server-list cache, a local firewall, or a VPN. Have that player run client.connect with the current address instead of searching the browser.