Rust server not showing up: connection, query and browser checks

By Niko Catarino

Updated 15 September 2026

Start with a direct join if your Rust server is not showing up in the browser. Use its game address and record the result before editing settings. If the join works, focus on queries and the browser. If it fails, begin with the server’s startup and connection path.

The Rust browser gets a list of candidates from Steam, then sends A2S queries to those servers for details. Each player’s client assembles its list from the replies, so another player may see an entry that is missing for you. Facepunch: No servers showing

These instructions apply to Rust PC dedicated servers. Console Edition has its own hosting and browser setup.

Test result	Follow this path
Direct connection fails	Keep the error, read the startup log and check the game endpoint, protocol and rules.
Direct connection works, but your testers cannot find the listing	Query the public endpoint, review Steam-related startup errors and inspect browser filters.
Another player sees the server	Compare that player’s branch, filters and connection with the affected client’s setup.

Scroll to see all columns →

1. Confirm players can connect to the running server

Find the public game address and game port in your hosting panel. Use that endpoint for the join; query, RCON and Rust+ ports have other jobs. At Rust’s main menu, open F1 and enter:

connect IP:PORT

Substitute your assigned game endpoint for IP:PORT. Have a tester outside the server’s local network try it as well so you check the public route. Facepunch describes this test in its player troubleshooting guide.

On a failed join, save the timestamp and exact message. A whitelist refusal, a version mismatch and a timeout each point to different checks. Read the console to see whether the world has finished loading, the process has crashed or startup keeps repeating. The panel can show a running process while the world is still loading.

Match the tester’s client build and branch to the server. Regular Rust and Rust Staging Branch use different lists. Confirm the intended release before changing network rules. If you need to update, back up the world, config and plugin data, use the host’s update procedure and verify framework support before reopening.

If the join succeeds but play stalls, record that result and continue with the Rust lag diagnosis.

2. Check the query endpoint and Steam connection

Rust uses different UDP port numbers for its game and query services. The query endpoint returns the information shown in the browser. An unset server.queryport can be derived from other configured ports, so read the running value or ask your host instead of adding one to the game port. Facepunch query-port documentation

Keep the four services separate

Service	Setting to verify	Protocol and purpose
Game	server.port	Players connect and play over UDP.
Steam query	server.queryport	UDP replies supply the browser listing.
RCON	rcon.port	Remote administrators connect over TCP.
Rust+	app.port	The enabled companion app service uses TCP.

Scroll to see all columns →

Set rules against your assigned or configured values. Example ports in a guide may differ from your allocation. The VYKIX Rust port reference lists the corresponding VxShield filters and dashboard steps.

A working RCON connection checks the admin service; send a UDP query to check the browser endpoint. To investigate Rust+ itself, run app.info in the server console. Facepunch Rust+ documentation

Test the public query path

Ask the host to send a normal A2S query to your public query endpoint from outside its network, or use an A2S-capable monitoring tool. Save the target address, timestamp and reply or timeout.

Use a tool that supports UDP. A TCP port check will not test this service, and a UDP timeout still needs investigation to locate the failure.

If you manage the machine, trace the process’s listening endpoint through the OS firewall, NAT mapping and upstream protection. Check both public and internal ports where translation is used. Save the existing rule, correct one mismatch and query the same endpoint again.

For managed Rust hosting, send VYKIX staff your game/query addresses and failed test; we maintain the protection rules. On Game VPS or bare metal, you manage them. VxShield starts with ports closed, so you must align upstream permissions with the OS firewall. Follow Rust protection in the VxShield firewall guide to match the preset to your ports.

Leave protection enabled while correcting the query rule. Opening RCON, exposing an origin address or permitting a broad port range will not isolate this fault. Put back the saved rule if your change does not help.

Check Steam registration after a successful query

If an external query gets a reply but your testers still cannot find the server, look for Steam connection, registration or authentication errors in startup. Save the exact message and ask the host to compare the advertised public endpoint and Steam connection with your running configuration.

A green monitoring status records a successful probe. Continue with another player’s browser check and the advertised fields before closing the issue. Keep your last successful test for support. Repeated restarts or a wipe can interrupt a working world while leaving a registration problem untouched.

Check with the owner before opening query access on a server that may have been hidden on purpose. Facepunch’s hidden setup restricts queries; admission controls decide who can join. Facepunch hidden-server guide

3. Check the client’s browser and server tags

Clear optional filters and search for a distinctive part of the name. Look in the applicable Community or Modded category. Compare region, player-count and tag settings with those of a player who can see the entry.

For a failing tag search, read server.tags. Facepunch groups some tags as exclusive: using both weekly and monthly can interfere with matching. Use the tags that describe your wipe policy. Facepunch server browser tags

The May 2026 browser update introduced location sorting using the estimated country and coordinates of a server IP. If the entry appears in the wrong region, investigate that mapping before changing a game port. Facepunch browser update

If most servers are missing for one player, use Facepunch’s client-side server-list checks. Confirm regular Rust versus staging, active betas and connection conditions. Note any VPN, which can change the apparent location. Correct specific permitted rules or get provider help while keeping security controls in place.

Refresh after the correction and note the result. If the entry remains absent, pair a new external query with another player’s search and send both results to the provider.

Keep one record for the host or support team

Collect your running values and test results in one place:

Time / time zone / last known working time:
Rust server build and branch / client build and branch:
Public game endpoint / assigned query endpoint:
Direct-connect result / exact error:
External query test / source / reply or timeout:
Browser category / region / filters / search text:
Second tester's result / connection conditions:
Startup or Steam-related error and timestamp:
Recent IP, port, firewall, framework or version change:
One correction tested / result / rollback:

Share the service addresses through the provider’s support channel. Remove passwords, tokens, device codes and player identifiers from public logs. Retain the private originals so support can match your timestamps to its records.

Choosing hosting after the fault is understood

On VYKIX managed Rust hosting, we maintain the host OS and protection rules while you administer Rust’s files and configuration. Bring the failed query or join result when discussing a move so we can address the problem you found.

After you can join the new server, use the Rust server requirements guide to test the map, plugins and player activity you want to host.