Skip to content

Configure RCON

Without an active RCON connection heliana cannot send commands back to the server, and it cannot tell who the players in the log are: events that name a player are not saved, so only game-level events (broadcast, map, round, capture zone, deployable spawned) are recorded, with no chat. On a server with Config managed by heliana on, the whitelist also can’t be reloaded after a sync.

SquadGame/ServerConfig/Rcon.cfg must contain:

bEnabled=True
Password=<your-rcon-password>
Port=21114
  • bEnabled must be True for RCON to accept connections.
  • Password and Port (21114 by default) are what you enter into heliana.
  • The RCON port must accept inbound TCP.

In the server connection form, fill in the RCON fields:

  • RCON host — the public IP address of your Squad server.
  • RCON port — the port from Rcon.cfg (default 21114).
  • RCON password — the password from Rcon.cfg.

Saving the server only checks that the RCON host address doesn’t point into a private network — it does not test the password or that the port is reachable. Whether the RCON connection is actually working shows up afterwards in the server’s header on the Dashboard: open the summary pill and look at the RCON row — its dot is red when the channel is down, and hovering the row shows the last error.

  • Running RCON commands from automation actions.
  • Reading live server state — who’s online, squad and role, current layer and player count — for the Dashboard.
  • Chat: each message arrives over RCON.
  • The player roster that attributes log lines to players. Without it a line that names a player is dropped after about 15 seconds.
  • Reloading the whitelist on the server after heliana pushes an updated Admins.cfg over SFTP — only on servers with Config managed by heliana turned on.