TG TOP OF GAMES
RustGuide

Rust Server Not Showing? Check the Query Port and Browser Tags

Rust uses server.port for player connections and server.queryport for services that retrieve server information. Facepunch states that the query port is required for a server to appear in Rust's server browser.

By TOP OF GAMES Editorial2 min read2 sources

THE SHORT ANSWER

Rust uses server.port for player connections and server.queryport for services that retrieve server information. Facepunch states that the query port is required for a server to appear in Rust's server browser.

  • Rust uses server.port as the UDP game port for player connections, and its default value is 28015.
  • Rust uses server.queryport for services that retrieve server information, and the query port is required for the server to appear in the server browser.
  • When the client and server run on the same computer, a player can press F1 at Rust's main menu and use connect localhost:28015, substituting the configured server.port when necessary.
  • The server.port and server.queryport values must both be open and accessible over UDP and cannot use the same port number.
  • If server.queryport is not explicitly set, it defaults to one greater than the higher of server.port and rcon.port.
  • A Rust server behind a router will most likely require port forwarding for connections from outside its local network.
  • Facepunch recommends assigning the server a static LAN address so router forwarding continues to target the correct machine.
  • A Rust server can take several minutes to start, and Server startup complete indicates that it should be ready for connections.

Rust uses server.port for player connections and server.queryport for services that retrieve server information. Facepunch states that the query port is required for a server to appear in Rust's server browser.

1. Wait for startup to finish

A Rust server can take several minutes to start. Check the console or log for:

Server startup complete

Facepunch identifies this message as the point when the server should be ready for connections.

2. Test the game port locally

Facepunch documents server.port as the UDP port players use to connect and lists 28015 as its default value.

If Rust and the server are running on the same computer, open Rust's main menu, press F1, and enter:

connect localhost:28015

Use the configured server.port instead of 28015 if the server uses a different game port.

3. Verify the query port

Facepunch specifies that:

  • server.port and server.queryport must both be open and accessible over UDP.
  • The game and query ports cannot use the same number.
  • If server.queryport is not explicitly set, it defaults to one greater than whichever is higher: server.port or rcon.port.

Use the server's actual port values when configuring its network access.

If the server is behind a router and must accept connections from outside the local network, Facepunch says port forwarding will most likely be required. The forwarding rule must direct traffic to the correct LAN address. Facepunch also recommends assigning the server a static LAN address rather than using DHCP.

4. Audit browser tags

Browser tags are assigned as comma-separated values through the server.tags convar. For example:

server.tags weekly,vanilla,roleplay

Documented tags include monthly, biweekly, weekly, vanilla, hardcore, softcore, pve, roleplay, creative, minigame, and training. Some tags can also be applied by other convars; enabling server.pve, for example, automatically applies the PvE tag.

Do not assign multiple tags from the same group. Wipe-schedule tags such as weekly and monthly are mutually exclusive, as are difficulty tags such as hardcore and softcore. Facepunch warns that the browser will display only one tag from such a group and that the server may not appear in searches for specific tags.

Troubleshooting order

  1. Wait for Server startup complete.
  2. Test the configured game port locally with connect localhost:PORT.
  3. Confirm that server.port and server.queryport are different, accessible UDP ports.
  4. Configure router forwarding to the server's static LAN address when outside connections are required.
  5. Remove mutually exclusive values from server.tags.

References