Rust · Troubleshooting · 4 minutes
Rust server browser keeps loading
If your Rust server appears in the in-game browser but the details panel keeps spinning, it does not always mean the server is offline. Rust uses separate game, query, RCON, metadata, and image data, and one part can be slow while the server still accepts players.
What the spinner usually means
The server browser can show ping, map, players, and wipe age from Steam query data. The lower details area may still wait on extra metadata, image loading, or Rust client-side browser behavior.
- If the server does not appear at all, check the address, version, whitelist, password, and whether the server fully started.
- If it appears with ping/player count but details spin, the query port is probably at least partly working.
- Try connecting directly before assuming the panel or ports are broken.
Checks players can do
- Refresh the Rust server browser and wait a few minutes after a restart or wipe.
- Try connecting from Favorites or directly by address if you have it.
- Make sure your Rust client is updated and not filtering the server out with tags or modded/community filters.
- Ask another player to test so you know whether it is one client or everyone.
Settings that can affect the details panel
Server owners should avoid broken metadata values. A website URL is optional and only powers the external website button. A header image should be blank or a real direct image URL.
server.url "https://example.com" server.headerimage "https://example.com/rust-header.jpg"
Do not put random values like 1 in server.headerimage. If the server is live, ask support before changing startup metadata or restarting.
When to contact support
Open a ticket if direct connect fails, the server disappears from the browser, the console shows startup errors, or multiple players cannot connect. Include the server name, the time you tested, whether direct connect worked, and a screenshot of the browser state.
Quick checks
- Visible in browser + ping shown usually means query data is responding.
- Spinning details alone can be Rust browser/client metadata jank.
- Support can verify query, game, and RCON ports from the node side.