Where to Find Your WebRCON IP, Port and Password (G-Portal and Nitrado)

The three fields a bot needs (and the one that trips everyone up)

Every Rust Console bot connects the same way. It needs your server's IP address, your RCON port, and your RCON password. That is the whole handshake. There are no plugins, no developer console, and no F1 menu to worry about, because none of that exists on console. Get those three values right and the bot talks to your server. Get one wrong and you stare at a connection that never completes.

The field that causes the most grief is the port, because your server actually runs on two of them. Players join through the game port, which is UDP and usually 28015. Your bot connects through the RCON port, which is a separate TCP/WebSocket port and is usually 28016. They sit one number apart, they are easy to swap, and the panels do not always spell out which is which. If you want the full picture, the difference between the RCON port and the game port is worth two minutes before you start.

G-Portal: where the IP, RCON port and password live

On G-Portal the connection is direct, so you copy all three values by hand. Log in, open your Rust Console server, and look at the server details or status area. The IP address is shown right at the top next to your server name. That is the same address players use, and it is the one the bot needs too.

The RCON port and password sit in the settings or configuration section, usually near the fields labeled RCON. The RCON port is commonly 28016, not the game port you see listed for players. The password is either displayed there or set by you in that same panel. If there is a switch or config line for rcon.web, make sure it is enabled, which usually means setting it to 1. Some G-Portal setups need WebRCON turned on before the port will accept a bot at all.

Copy the IP, the RCON port, and the password exactly as shown, with no extra spaces. That is everything you need to connect a bot to your G-Portal server. One thing worth knowing up front: G-Portal auto-updates and reboots your server whenever Facepunch ships a patch, which briefly knocks any bot offline until it reconnects. That is normal, not a setup mistake.

Nitrado: the one-click link that skips the copying

Nitrado exposes the same RCON details if you want them. The RCON port and password live in your server's settings under the RCON or general configuration area, and the IP is on the server's main page. Any bot that asks for three fields can use those.

But on Nitrado you usually do not have to touch any of that. Because Nitrado supports an account link, you authorize your Nitrado account once and let the bot pull the server in for you, with no IP, port, or password to copy or mistype. That is how you link a Nitrado server to Vantic: sign in, approve the link, pick your server, and you are connected. If copying long strings into a phone is where these setups usually fall apart, this removes that step entirely.

Players can join but the bot cannot connect

This is the single most common console setup error, and it almost always means the same thing: you put the game port where the RCON port belongs. If people are happily joining your server but the bot times out, your server is clearly online, so the address is fine. The bot is knocking on 28015, the game port, when it should be knocking on 28016, the RCON port.

Swap the port to the RCON value, confirm rcon.web is enabled on hosts that require it, and try again. Both ports have to be reachable for their own jobs: the game port for players, the RCON port for your bot. When only the players get through, the RCON port is the first thing to check.

When the password is the real problem

If the port is right and it still fails on the password, look at the password itself. A host-generated password full of special characters, or one with a stray space at the start or end, can break authentication even when every character looks correct. Copy it cleanly, or regenerate a simpler one in the panel and reconnect.

One warning saves a lot of frustration. Rust rate-limits and briefly locks RCON after repeated failed attempts, so hammering the connect button after a bad password makes the lockout worse, not better. Fix the value, wait a moment, then try once. If you keep seeing an authentication failed error, the answer is almost always a clean password plus a short pause, not more retries.

Paste it in, connect, and confirm

With the three values in hand, or the account linked, enter them in the bot's connection setup: IP, RCON port, password. Save and let it connect. A healthy connection usually shows a status like connected or online within a few seconds, and a good bot will start reporting server activity right away so you know the link is live.

If it still will not connect after you have checked the port and the password, work through the rest in order instead of guessing. The full first-connection checklist for when the bot still will not connect covers every remaining cause, from firewalls to rcon.web to a server that has not finished booting. Nine times out of ten on console, though, it comes back to the same two things: the RCON port instead of the game port, and a clean password entered once.

Frequently asked questions

Keep reading

the first-connection troubleshooter for when WebRCON will not connect · connect a bot to your G-Portal server · link a Nitrado server with one click · RCON port vs game port explained · fix an RCON authentication failed error