Connect to a Rust Server by IP: Console Command, Ports and Browser Fixes
You can join a Rust server without the server browser by opening the console at the main menu and typing the connect command with the server's address and port. The game port is 28015 by default, and it uses UDP. Separately, the query port is what lets the server appear in the in-game list.
This guide covers both ways of connecting, what each port is for, and the usual reasons a server is unreachable or missing from the list. It was checked on 2026-11-17 against Facepunch's server documentation. The documentation shows the connect command for localhost and not for a remote address, so the remote form below follows the same pattern and is marked as such. On ChicagoServers the ports are assigned by the panel, so you do not forward anything.
- At the main menu press F1, then type
connect ADDRESS:PORT. Facepunch's example isconnect localhost:28015. - server.port (default 28015) is UDP and is needed to play. The query port is UDP and is needed for the server list. RCON and Rust+ use TCP and are optional.
- Addresses starting with
192.,172.or10.are private. They do not work from the internet. - On ChicagoServers, copy the address and port from the top of your server page, or from Network on the Startup tab.
- If a server joins by address but is not in the list, check the query port first.
On this page
Connect with the console
- Get the address and port
On ChicagoServers, open your server in the panel. The address and port are at the top of the page, and under Network on the Startup tab each has an address to copy.
- Start Rust
Launch the game and wait at the main menu.
- Open the console
Press F1 to open the console.
- Type the command
Use your server's address and port. Replace the example with your own values.
connect 203.0.113.10:28015 - Press Enter
The game connects and loads the map.
What each port is for
| Port | Protocol | Used for |
|---|---|---|
server.port, default 28015 | UDP | Playing. Required. |
| Query port | UDP | The in-game server list. It must not be the same as the game port, and if not set it defaults to one more than the game port or RCON port, whichever is greater. |
rcon.port | TCP | Remote admin tools. Optional. |
| Rust+ port | TCP | The companion app. Optional. See the Rust+ guide. |
Facepunch's documentation suggests getting the game port working first, and then adding the others. On ChicagoServers the panel assigns each port and shows it under Network, so you do not change them. If a plugin needs another port, the Extra ports area on the same tab can reserve one. More on settings is in the Rust server settings guide.
Public and private addresses
An address that starts with 192., 172. or 10. is a private address on a local network. Facepunch notes that these are not reachable from the internet. Players outside your network need a public IP, and if you host at home, port forwarding on your router. For hosted servers, use the address the panel shows. For the general idea, see what is a game server IP and port.
- By default a Rust server listens on all addresses of its machine (
0.0.0.0). A+server.ipoption can restrict it, for example to a LAN address. On ChicagoServers the launch line is managed for you. - Dynamic home IPs change, so a hosted server avoids the problem entirely.
The server is not in the list
| Check | Why it matters |
|---|---|
| Can you join by address? | If yes, the game port works, and the problem is the listing. |
| The query port | The list needs the query UDP port. Facepunch says it is required for the server browser listing. |
| The server has fully started | A server that is still loading or restarting may not appear yet. |
| Your search and filters | Filters in the in-game browser can hide a server. Try its exact name. |
| The server's country | Facepunch works out a server's location from a third-party IP location database. If it shows the wrong country, a correction can be requested from that database's provider, and hosts can ask for their geofeed data to be used. If this affects your server, contact support. |
The documentation does not say where in the game the country is displayed, so check the server's entry in the browser.
Common errors
| Problem | Likely cause and fix |
|---|---|
| The connect command does nothing | Check you opened the console with F1 at the menu, and typed the address and port with a colon between them. |
| Connection times out | Wrong address or port, the server is offline, or you used a private IP. Copy the details from the panel. |
| Cannot find the server by name | Query port or listing problem. Join by address, then investigate the listing. |
| Works for you but not friends (home server) | Port forwarding is missing or points at a different computer. This does not apply to a hosted server. |
| Fails right after a game update | Check that your game and the server are on the same version. |
Need admin rights once you are in? See Rust admin setup. For a map that has just wiped, see the wipe schedule guide. Looking for a host? See Rust server hosting.
Frequently asked questions
How do I connect to a Rust server by IP?
At the main menu press F1 to open the console, then type connect followed by the server address and port, such as connect localhost:28015 for your own machine.
What port does Rust use?
The game port server.port is 28015 by default and uses UDP. The query port is UDP too, and RCON and Rust+ use TCP.
Why is my Rust server not showing in the server list?
Usually the query port. It must be reachable over UDP and different from the game port. Also check the server has fully started and your filters.
Why can't friends join my Rust server by IP?
A private address starting with 192., 172. or 10. is not reachable from the internet. Use the public address, and on a home server forward the ports.
How do I open the Rust console?
Press F1. At the main menu you can use it to run the connect command.