# Which Rust ports should you forward at home?

[Rust server guides](https://rustsc.com/learn/index.html.md) / [Server setup](https://rustsc.com/learn/setup/index.html.md)

Start with the game port, which players enter when they join by address. Add the query port if you want the server to appear in the public browser. Both use UDP and need different port numbers.

## Read the ports from your own server

Find server.port and server.queryport in your startup settings. Facepunch documents that when you leave the query port unset, Rust takes the higher of the game and RCON ports and adds one. Read the values on your host before copying any example from a guide.

Here is an example for a server using game port 28015 and query port 28017. Both rules point to the game's host. Allow both ports in its firewall and reserve its local address in the router if possible.

| Purpose | Router rule | What proves it works |
| --- | --- | --- |
| Play | UDP 28015 to 28015 | A friend joins by address from outside the home. |
| List the server | UDP 28017 to 28017 | The friend finds the correct entry in the browser. |

## Check each rule from outside your home

Ask a friend on another network to join by your public address and game port. Once that works, ask them to find the server in the browser if you enabled public listing. A successful direct join is your check for the game rule. Finding the server in the browser checks the listing path.

Remote console access and Rust+ have their own ports. Leave those out of this setup when the goal is to let friends play and find the server.

## Sources

- [Facepunch server ports and router setup](https://wiki.facepunch.com/rust/Creating-a-server)

## Related resources

- [What a message means and what to do](https://rustsc.com/support/guides/fix-common-problems/index.html.md)

---

HTML version: https://rustsc.com/learn/setup/game-port-and-query-port-at-home/
