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

If your Rust server is not showing up, try joining its game address before changing the configuration. A successful join lets you narrow the search to the query service and browser. A failed join gives you a different fault to investigate.

Facepunch describes the browser getting candidates from Steam, then asking those servers for information through A2S queries. Each client builds its results from the replies it receives. Your missing listing may still appear for another player. Facepunch: No servers showing

These checks cover Rust PC dedicated servers. Rust Console Edition uses a different hosting and browser path.

1. Confirm players can connect to the running server

Copy the public game address and game port from your hosting panel. Query, RCON and Rust+ ports serve other purposes. From the Rust main menu, press F1 and enter:

connect IP:PORT

Replace IP:PORT with your assigned game endpoint. Ask someone outside the server’s local network to try it too; a local join does not test the public route. Facepunch includes this direct-connect check in its player troubleshooting guide.

Keep the time and exact message if the join fails. A timeout, version mismatch and whitelist rejection call for different checks. In the console, look for completed world loading, a crash or a restart loop. The panel’s running status can appear before the world is ready.

Compare the server build and branch with the tester’s client. Regular Rust and Rust Staging Branch have different lists. Match the intended release before editing firewall rules. If an update is needed, back up the world, configuration and plugin data, follow the host’s update workflow and confirm framework compatibility before reopening.

If players join but gameplay stalls, keep that result and move to the Rust lag diagnosis.

2. Check the query endpoint and Steam connection

Rust’s game and query services use UDP on different port numbers. The query service supplies browser information. If server.queryport is unset, Rust can derive it from other configured ports. Read the effective value or ask the host; do not assume game port plus one. Facepunch query-port documentation

Keep the four services separate

Use your assigned or configured values, not example ports copied from a guide. Our VYKIX Rust port reference maps these services to their VxShield filters and the current dashboard procedure.

RCON answering tells you the admin endpoint works. It leaves the UDP query untested. For a Rust+ error, inspect its own service information with the server-console command app.info. Facepunch Rust+ documentation

Test the public query path

Ask the host to send a normal A2S query to the assigned public query address from outside its network. An A2S-capable monitoring tool can do the same check. Record the target, time and reply or timeout.

A TCP port checker cannot validate UDP. A UDP timeout cannot identify the failing network layer on its own.

On a self-managed machine, compare the process’s listening endpoint with the OS firewall, NAT mapping and upstream protection. A public port can be translated before reaching the process, so check both sides. Save the current rule, make one targeted correction and retest the same endpoint.

Our support split is explicit: VYKIX staff manage protection rules on managed Rust hosting. Send us the game/query endpoints and failed test. On Game VPS or bare metal, you manage the rules. VxShield starts with ports closed, and opening the OS firewall alone is insufficient. Match the preset to your configured ports using Rust protection in the VxShield firewall guide.

Keep protection enabled. Opening RCON, exposing an origin address or allowing a broad port range adds risk without isolating the query fault. Restore the saved rule if your correction fails.

Query replies and registration are different evidence

If queries answer but the listing remains absent for your testers, inspect startup for Steam connection, registration or authentication failures. Keep the exact message. Ask the host to compare the advertised public endpoint and Steam connection with the active configuration.

A monitoring service’s green status means its probe received a reply. It cannot confirm every client’s listing or all advertised fields. Preserve the last successful test and escalate the unresolved result. Repeated restarts, or a wipe, can disrupt a healthy world without fixing registration.

Check whether the owner intended the server to stay hidden before opening query access. Facepunch documents a setup that restricts query visibility. That is separate from deciding who may join. Facepunch hidden-server guide

3. Check the client’s browser and server tags

Search a distinctive part of the server name with optional filters cleared. Check the relevant Community or Modded category. Compare region, player-count and tag selections with a tester who can see the server.

If a tag search fails, inspect server.tags. Facepunch warns about tags from the same exclusive group: advertising both weekly and monthly wipe schedules can interfere with matching. Describe the server’s actual policy instead of adding unrelated tags for exposure. Facepunch server browser tags

Facepunch’s May 2026 browser update added location sorting based on the server IP’s estimated country and coordinates. An unexpected region calls for a mapping check, not a new game port. Facepunch browser update

If the player sees few servers in total, use Facepunch’s client-side server-list checks. Check regular Rust versus staging, active betas and connection conditions. A VPN can alter the apparent location. Use specific allowed rules or provider help without disabling security controls.

Refresh after a correction and record the result. If the listing is still absent, repeat the query test and the second player’s search. Those paired results give the provider something to investigate; an assumed listing delay does not.

Keep one record for the host or support team

Fill this in with active values and observed results:

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:

Send service addresses through your provider’s support channel. Redact passwords, tokens, device codes and player identifiers before posting logs in public. Keep the original private so support can correlate your timestamps with its logs.

Choosing hosting after the fault is understood

VYKIX managed Rust hosting leaves host-OS maintenance and protection rules with our staff while you control Rust files and configuration. Bring the failed connection or query test when discussing a move, so the replacement addresses the need you identified.

For a new server, use the Rust server requirements guide to plan the map, plugins and workload test once joins work.