Rust Server Not Showing Up? A Discovery Troubleshooting Checklist

A Rust server can be running and still fail to appear in the browser. Discovery depends on successful startup, public network reachability, Steam query responses and browser filters. Work through the chain in order instead of repeatedly restarting or changing unrelated settings.

Confirm the server completed startup

Review the console for a completed world load and listening ports. A process can exist while still downloading, generating the map, loading plugins or failing on configuration. Check for bind errors, update mismatches and plugin crashes before investigating discovery.

Verify public ports and addressing

The game port, query port and RCON port are distinct. Ensure the configured game and query ports are permitted through the operating-system firewall, provider firewall and router/NAT layer. UDP is essential for game and query traffic. Test from outside the host network; a local connection does not prove public reachability.

If the machine has multiple interfaces or sits behind NAT, confirm the server advertises and binds the intended address. Avoid publishing a private RFC1918 address as the public endpoint.

Check Steam query visibility

External directories generally discover Rust servers through Steam’s server-query ecosystem. If the query endpoint does not answer, the server may be playable by direct connect yet absent from lists. Confirm that the query port is not accidentally mapped as TCP-only and that another service is not using it.

Remove browser-side filters

In the Rust client, clear search text and filters, check the appropriate official, community or modded category, and allow the browser time to refresh. A server with plugins may be categorized differently than expected. Version differences after an update can also hide incompatible servers until both client and server are current.

Check identity and metadata

Use a clear hostname and truthful description. Duplicate names do not normally prevent listing, but make verification difficult. Ensure the server identity directory is stable and that startup arguments are actually applied by the host panel. After changes, allow discovery systems to poll again instead of expecting every directory to update instantly.

• Direct-connect test succeeds from an external network.
• Game and query UDP ports answer publicly.
• Server and client versions match.
• Browser category and filters are correct.
• No startup or port-binding errors remain.