Connect RustAdmin to Rust RCON without exposing credentials

RCON provides remote control of your Rust server. Treat its password like an administrator credential. The game connection port and the remote-console port serve different purposes; entering the game port in RustAdmin will not establish an administrative connection.
Collect the correct endpoint
Check your service's assigned public address and allocated RCON TCP port. Confirm the running startup configuration uses that allocation. In a hosted container, the public endpoint can differ from the address visible inside the container. Do not replace the bind address with your home IP or assume localhost reaches the hosted server.
Record the existing RCON settings privately. Back up the relevant configuration before changing anything. If RCON is already used by monitoring or administration tools, plan the password change with those administrators so their clients can be updated together.
Configure a compatible connection
Check that the Rust server has finished starting successfully.
For a WebRCON-compatible client, confirm 
rcon.web 1 is configured. This selects the protocol; it does not by itself encrypt the connection.
Set a long unique 
rcon.password through the supported startup or configuration method. Avoid passwords reused for billing, Steam or email.
Apply changes through a normal scheduled restart if required. Keep the previous configuration available for rollback.
In your trusted RustAdmin installation, choose the connection mode matching the server, then enter the public address, allocated RCON port and password in the appropriate fields. Client layouts differ, so use the help for your installed edition.
Test with a harmless command
Request a player list or server status first. Confirm the response belongs to your server before issuing any command that changes it. Check that console output remains available from the game panel as a recovery route. Close duplicate client sessions during diagnosis so you can identify the attempt being tested.
Interpret the failure
A timeout suggests the endpoint, allocation, firewall path or listener needs checking. Immediate refusal can mean the process has not opened that port. A successful socket connection followed by authentication failure points towards credentials or protocol. These are clues rather than definitive diagnoses; save the exact error and time for support.
Ask for a narrowly scoped RCON allowlist or a managed private connection where available. Do not open every port or disable the host firewall to test one listener. Some browser-based remote consoles forward secrets through another service; use only a client you trust and avoid putting the password in shared links or screenshots.
Finish safely
Remove stale saved credentials from unused tools and rotate the password if it was exposed. A connection working from one location does not prove access is restricted elsewhere. Tell support which client and protocol worked, with the address and time, while keeping secrets out of the ticket body. Never upload an unredacted configuration file publicly.
Related guides
Diagnose Rust game, query and RCON ports
Assign owner and moderator access
Further reading
Facepunch: creating a Rust server
RustAdmin official client website
Looking for another game? Browse game server setup and troubleshooting guides.