Helios Rust Console Bot Documentation

Untitled

Last updated
Maintained by
Helios RCE

title: G-Portal vs Nitrado: Setting Up a Rust Console Bot on Each description: What actually differs when connecting a Discord bot to a Rust Console server on G-Portal versus Nitrado, where to find your RCON values on each host, and why the setup process itself is the same. relatedCommand: /server add

Short Answer

The bot setup process is the same on both hosts. Helios connects over WebRCON, and WebRCON works the same way regardless of who runs the machine. Anyone telling you a bot works on one and not the other is describing a credentials problem, not a compatibility problem.

What actually differs is where you find the three values you need, and how each host behaves around wipes and restarts. Those three values are identical in kind on both:

  • Server IP
  • RCON port (not the game port)
  • RCON password

The Setup Is Host-Agnostic

On either host, the sequence is:

  1. Finish Discord Roles & Channels before connecting anything.
  2. Add the server with /server add using the host's current values.
  3. Validate command execution with /cmd send command:"fps".
  4. Validate player polling with /whoson.
  5. Enable modules in /settings server — but only after both checks pass.
  6. Turn on killfeed and admin alerts first, so staff have visibility during rollout.
/server add
/server list
/server edit
/cmd send command:"fps"
/whoson
/settings server

TIPValidate before enabling modules

Enabling modules before the connection is proven is the most common way to turn one problem into five. If /cmd send and /whoson both work, every later failure is a module or permission issue, which is a much smaller search space.

Where the Values Come From

G-PortalNitrado
Where to lookActive server settings in the G-Portal panelServer settings in the Nitrado panel
What to copyHost, RCON port, RCON passwordHost, RCON port, RCON password
Common trapCopying the game port instead of the RCON portSame
After a reinstallRe-read all three; they may have changedRe-read all three; they may have changed

The authoritative source is always your host's control panel. Do not reuse values from an old message, a note, or memory — that is the cause of most "it stopped working" reports.

Host-Specific Behaviour Worth Knowing

Both hosts

  • Credentials can change on wipe or reinstall. Verify the connection after every wipe as a matter of routine, not only when something looks broken.
  • The server must be fully started. WebRCON does not answer during boot, which can take several minutes after a wipe. A failed check during boot is not a configuration error.

G-Portal

G-Portal also runs its own first-party bot, Mr. Bandit, which some owners run alongside or instead of a third-party bot. If you are weighing that choice, see Helios vs Mr. Bandit, which is sourced from G-Portal's own documentation.

Nitrado

If /whoson returns nothing on a server that otherwise responds, confirm the server status in the Nitrado panel before changing any stored values — a restarting server produces exactly this symptom, and editing credentials during a restart adds a second problem.

If It Will Not Connect

The diagnosis is the same on both hosts, and it is worth doing in order rather than by guesswork. See Why WebRCON Is Not Connecting.

The short version:

  1. /server list — is the entry enabled?
  2. /cmd send command:"fps" — do commands arrive?
  3. Re-read IP, RCON port, and password from the host panel and compare.
  4. /server edit to correct anything stale, then retest.

Choosing Between the Hosts

This guide deliberately does not rank the two hosts. Pricing, hardware, regional availability, and support quality change often enough that any comparison published here would go stale, and we cannot verify either host's current offering continuously. Judge them on your own requirements — but the bot setup should not be part of that decision, because it is the same either way.

Related Pages