THE KEY POINT
Confirm you launched regular Rust, then check the server-browser settings and whether the problem affects one server or the whole list. An empty list does not establish a lost skin or account ban.
01
Identify the scope before changing settings
Write down whether no servers appear, only one known server is missing, or a direct connection fails. Include the Rust version and the time of the observation. This is our diagnostic record; it avoids combining a browsing problem with a particular server’s availability.
Facepunch explains that Rust obtains a list from Steam and queries individual servers. Their responses populate the browser. That explains why seeing a server elsewhere does not establish that your client can reach it.
02
Check the branch and the documented Steam option
- Confirm regular Rust versus Staging Branch in your library; use the intended build.
- Facepunch recommends at least 5000 for Steam Settings → In-Game → Server browser pings / minute, where the option is present.
- Check the selected Rust beta if you did not intend to use a test version; let any resulting update finish.
- Record the result after each change. Do not change several network and client settings at once and then guess which mattered.
These are diagnostic checks, not a guarantee that any server is reachable.
03
If only a known server is missing
For a known server, Facepunch documents F1 from the main menu, then connect followed by its address and port. Obtain that destination from the established operator; this guide does not endorse an unknown server.
Record any VPN context because location may affect the list. Avoid disabling protective software as a generic fix. A network change needs a specific understood reason and the relevant vendor’s guidance.
| Staging opened accidentally | Compare using the intended regular game build. |
|---|---|
| One server missing, others visible | Ask its operator for the current build and address. |
| Whole list empty after checks | Save the branch, observed settings, timestamp and connection results for official support. |
04
Send a record rather than a guessed cause
Provide the last working time and the smallest repeatable sequence that produces the empty list. If the client crashes, use the crash-evidence guide instead of saying only that servers do not work. No single setting here guarantees that a particular server is online or reachable.
BEFORE YOU CONTINUE
Quick checklist
- Identify one missing server versus an entirely empty list.
- Check regular Rust versus Staging and the selected beta.
- Inspect the documented Steam browser option when present.
- Keep one change and one observed result at a time.
Official sources
Facepunch's server-browser instructions were reviewed on 20 October 2026. The guide selects the low-risk checks; it does not promise server availability.
This guide selects low-risk checks from the official article. It does not recommend disabling firewall or anti-cheat protection.