# How to assign ports to a second Rust server on one host

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

Record the first server's active endpoints before adding the second. Then choose available ports for the new world and make them explicit in its launch or hosting settings. Keep the original world's player address handy as the comparison.

## Prepare one row per world

The example assumes the worlds share a host and the listed ports are available. These are explicit assignments. On a rental, use the assignments from the provider. Each world also needs its own save location. Set optional endpoints only for services you use.

| World | Game UDP | Browser query UDP | RCON TCP | Rust+ TCP |
| --- | --- | --- | --- | --- |
| Harbour | 28015 | 28017 | 28016, private | 28082, if used |
| Valley | 28115 | 28117 | 28116, private | 28182, if used |

## Check what each connection is for

Use the game port for direct joins and the query port for discovery. Match only the intended game and query paths through your firewall and router. Keep the administrator console on your existing private management path. If you use Rust+, set app.port in the launch configuration to the chosen Rust+ value. If you leave it unset, Rust+ derives a port from the game's other settings. Check the actual port with app.info on each running server.

For Rust+ on two independent worlds, keep their saved companion identities separate. If Rust+ opens the wrong world or fails after a copy, compare the settings and identities on the two worlds before touching the first world's pairing.

## Prove the rows while both worlds are running

Use a test host first where you can. Start the second world and keep both processes running through each check.

1. Join each game endpoint from the network your players use. Check the matching world name and a familiar landmark.
2. Find each intended public listing and join it from the Rust browser. If direct join works and the listing does not, check the query assignment for that row.
3. Read a harmless status from each remote console endpoint on your private management path. The output should belong to the intended world.
4. If you offer Rust+ on either world, pair with that world and open it from the app. Repeat independently for the other world if you support Rust+ there.
5. If a port is already in use, compare the startup log for the new world with the written rows. Fix the conflicting new assignment before sharing its address.

## Sources

- [Facepunch dedicated-server port settings](https://wiki.facepunch.com/rust/Creating-a-server)
- [Facepunch companion server ports and identity](https://wiki.facepunch.com/rust/rust-companion-server)

## Related resources

- [Change server settings](https://rustsc.com/support/guides/server-settings/index.html.md)
- [How to test your Rust server from another network](https://rustsc.com/learn/setup/test-your-rust-server-from-another-network/index.html.md)
- [How to set up Rust+ on your dedicated server](https://rustsc.com/learn/setup/set-up-rust-plus-on-your-dedicated-server/index.html.md)

---

HTML version: https://rustsc.com/learn/setup/allocate-ports-for-a-second-rust-server/
