Vantic for Rust Console Edition
WebRCON Not Connecting: Causes and Fixes
When WebRCON will not connect at all, the cause is almost always one of five setup details rather than the bot. Start with the three values a connection needs, the server IP or host, the RCON port and the RCON password, since a single wrong one fails everything, and watch the two most common traps: using the game port instead of the RCON port, and a password changed in the host panel but never updated. The other causes are a port that is not open or an address that is not a WebRCON endpoint, and the Connect Doctor tests the link and points you at the exact field to fix rather than leaving you guessing.
If WebRCON will not connect at all, the cause is almost always one of five things: a wrong IP or host, the wrong RCON port, the wrong RCON password, a port that is not open, or an address that is not a WebRCON endpoint - and Vantic's Connect Doctor narrows a failure down to the field to fix.
Why WebRCON is not connecting
When WebRCON will not connect for the first time, it is rarely the bot and almost always a setup detail. Vantic reaches your Rust Console server over WebRCON using three values: your server IP or host address, the RCON port, and the RCON password. If any one of those is wrong, or the port is closed, or you have pasted an address that is not a WebRCON endpoint, the handshake fails before a session ever opens. Those five causes account for the overwhelming majority of first-time connection failures on PS4, PS5, and Xbox servers.
This page is about that very first connection never completing. If your server connected fine and then dropped later, that is a different problem with different fixes, covered on the page for when a Rust Console bot keeps disconnecting. Here we walk the five setup causes one at a time and show how Connect Doctor names the exact one instead of leaving you guessing.
Start with the IP, RCON port, and RCON password
The first three fields catch most cases. A wrong IP or host is usually copied from the wrong screen, or the server's public address changed after a restart or a rehost, so the value you saved no longer points anywhere. The wrong RCON port is the classic trap: the RCON port is not the game or query port, and hosts list them separately in the server config, so it is easy to paste the one people see most often. Even one transposed digit means nothing answers.
The RCON password is its own value, separate from your host account login and separate from any in-game admin password. A stray space at the end, a copied line break, or an old password from before a change is the usual culprit. G-Portal (and any host you connect over direct RCON) exposes the IP, RCON port, and RCON password together in the server settings, so read all three straight from there in one pass rather than from memory. Nitrado is different: Vantic links it with a one-click account approval - no IPs, ports, or passwords to copy - so these five WebRCON causes apply to the direct-RCON path, not to a Nitrado link. See our notes on the G-Portal Rust Console bot and the Nitrado Rust Console bot for how each host connects.
Port not opened, or the wrong protocol
On most managed hosts the RCON port is open by default, so this cause is rare there, but it does bite. A custom firewall rule, a network policy, or a self-hosted box can block the port even when your IP, port, and password are all correct: everything looks right, yet nothing responds because the traffic never reaches the server. If the address and credentials check out but the connection still times out, a closed port is the prime suspect.
The last cause is the wrong protocol. WebRCON is a specific connection type, and pasting a plain query-port address, an http or web-panel link, or credentials from a tool that speaks a different RCON flavour will never complete a WebRCON handshake. Vantic connects over WebRCON with your IP, RCON port, and RCON password, and nothing else - so if you are copying values out of a different connection tool, they may simply be for the wrong kind of endpoint.
Connect Doctor tells you exactly what to fix
Rather than a blank "connection failed", Vantic ships Connect Doctor. It tests the connection and reports, in plain language, whether the server rejected your password, could not be reached at that address and port, or did not answer at all, and it points you at the field to fix. That turns a frustrating trial-and-error loop into a single, clear instruction, which is exactly what you want the first time you set a server up.
Every feature is visible on the free plan, so you can run Connect Doctor and get connected before you decide on anything, and Vantic is free to start on every server. Once you are in, the honest live status keeps you informed and never serves stale data as if it were live, and you can watch the whole thing from your Rust Console server dashboard. If you are brand new to this, the guide for Rust Console servers for beginners walks the setup end to end.
What owners say about the support
Owners' own words, used with their permission. Each came through the dashboard or was said in the open in Discord, and is exactly as written.
“It's been great. The owners are extremely fast to fix bugs and glitches, open to opinions and QOL improvements. Highly recommended, and I will continue to use this service for as long as I run a server.”“Your bot is top tier my friend. A+. I am very happy with it.”See it running in minutes
Sign in with Discord, run the Connect Doctor, and watch the Truth Layer go live. Free to start - Premium is A$20 a month per server, cancel anytime.
Frequently asked questions
Why is my WebRCON not connecting?
Because one of five setup details is off: a wrong server IP or host, the wrong RCON port, the wrong RCON password, a port that is not open, or an address that is not actually a WebRCON endpoint. Vantic's Connect Doctor tests the connection and tells you whether the password was rejected, the address could not be reached, or the server never answered, so you fix one thing instead of guessing.
What is the difference between WebRCON not connecting and my bot keeping disconnecting?
WebRCON not connecting means the very first connection never completes, which is nearly always a wrong IP, port, password, closed port, or wrong protocol. A bot that connects and then drops is a running-connection problem with different causes and fixes, covered on the page for when a Rust Console bot keeps disconnecting.
Where do I find my RCON port and RCON password on G-Portal or Nitrado?
On G-Portal (and any direct-RCON host) they sit together in the server settings or config panel - read your IP, RCON port and RCON password straight from there in one pass. The RCON port is not the game or query port, and the RCON password is separate from your host login, so copy each exactly with no stray spaces. Nitrado does not use RCON details at all: you approve Vantic with a one-click account link and pick your server from a list, with no IPs, ports or passwords to copy.
Do I need to open a port for WebRCON on Rust Console?
On most managed hosts the RCON port is already open, so usually no. On a self-hosted box or behind a custom firewall it can be blocked, which looks like correct details that still time out. If the IP, port, and password all check out but nothing responds, a closed port is the likely cause.
I pasted the right IP and password but WebRCON still will not connect - what now?
Two things are worth checking. First, confirm the port is the RCON port, not the game or query port. Second, make sure the address is a WebRCON endpoint and not an http or query-port link from a different tool. Running Connect Doctor is the fastest way to see which of these it is, and it is free to use.
Keep exploring
Rust Console bot keeps disconnecting · G-Portal Rust Console bot · Nitrado Rust Console bot · Rust Console server dashboard · free Rust Console Discord bot · the live network ladder