A Rust server can be fully running and still fail to appear in the browser if its query port is unavailable. Facepunch documents that server.port and server.queryport are separate UDP ports, cannot be the same, and both must be reachable for normal browser discovery. Start by proving the server works locally, then test external connectivity, then focus on discovery.

Fix it step by step

1Confirm the server completed startup

Read the console for binding errors, Steam/query errors, repeated crashes, or an unfinished update. Do not troubleshoot browser visibility while the server itself is still failing to start cleanly.

2Verify server.port and server.queryport

Facepunch documents server.queryport as the port used for server-browser information. If it is not explicitly set it can default based on other ports, but server.port and server.queryport cannot be the same. Both are UDP and both need to be accessible.

3Test locally with client.connect

If the game client is on the same machine, use the Rust console to connect to localhost and your server port. A successful local connection proves the game process is listening even if internet routing is still wrong.

4Test direct connection from outside the LAN

Use the public IP and game port from a separate internet connection when possible. A successful direct connection but missing browser entry strongly points toward query-port/firewall/discovery configuration.

5Check router and provider firewall rules

Forward the required UDP ports to the server's stable LAN IP and allow the server application/ports through the host firewall. Hosted servers may also have a provider-level firewall that must be configured separately.

6Rule out CGNAT or non-public addressing

Compare the router's WAN address with the public address seen from the internet. If the ISP uses CGNAT, normal home-router forwarding may not make the server reachable from outside.

7Confirm hostname and visibility configuration

After networking works, review server.hostname, identity/config files, query port, and any intentional hidden-server settings. Browser discovery can take time after a fresh start, so avoid changing multiple networking variables at once.

Frequently asked questions

Can players connect even if the Rust server is not listed?

Yes. If direct connection succeeds, the core game port works and the remaining problem may be query/discovery related.

Can server.port and server.queryport be identical?

No. Facepunch explicitly states they cannot be the same port.

Why does it work on localhost but not from the internet?

That points toward router forwarding, host/provider firewall rules, public-IP availability, or CGNAT rather than the Rust server process itself.

Official sources

These references were used to build and verify the troubleshooting order in this guide.

Related troubleshooting guides

Continue with closely related guides from the same topic hub.