How to Become Admin on a Rust Server: ownerid and RCON

To become admin on a Rust server, run users in the server console to get your SteamID64, then run ownerid <SteamID64> "<name>". Reconnect to the server and the log shows your new auth level. Use moderatorid the same way for moderators. The change saves on its own.

What you need first

• Access to the server console. On a hosted server, that is the Console page in the panel. On a server you run yourself on Linux, use an RCON client, because the Linux console is not interactive.
• Your SteamID64. It is the long number that identifies your Steam account, such as 76561198123456789.
• To be connected to the server, if you want to get the number with the users command.

If you have no server yet, start with how to make a Rust server.

How to make yourself admin on a Rust server

These steps follow Facepunch's Creating a server guide.

1. Join your server with the Steam account you want to make the owner.
2. Open the server console. In our panel, open Console.
3. Find your SteamID64. Run users. Each connected player is listed with their ID and name.
4. Run the owner command with your own ID and name, as in the example below.
5. Reconnect to the server. Leave and join again.
6. Check the log. Facepunch says you should see has auth level in the log when you join. Admin commands now work in your F1 console.

users

ownerid 76561198123456789 "TomSmith"

The console answers Added owner TomSmith, steamid 76561198123456789. Replace the example ID and name with yours. Facepunch notes the changes are saved automatically.

How to add moderators

Moderators have a lower level than owners. Use the same pattern with moderatorid:

moderatorid 76561198123456789 "PlayerName"

Give owner rights to as few people as possible. The next section explains the difference.

Edit users.cfg by hand

Admins live in a file named users.cfg, in the same cfg folder as your server.cfg. Oxide's docs give its location as /server/my_server_identity/cfg/. Facepunch shows one line per admin:

ownerid 76561198123456789 "TomSmith" ""

You can add, change or remove admins in this file when the server is stopped. To remove someone, delete their line. Open it in the File Manager, save, and start the server again. Rust server.cfg settings explains the rest of the cfg folder.

Use RCON to run commands from outside the game

RCON lets admin tools connect to your server from outside the game. It uses a port and a password, both set in your start options:

• +rcon.port is the RCON port. It uses TCP, and Facepunch's example uses 28016.
• +rcon.password is the password. Facepunch's guide says "Change this value!!!" and it means it.
• +rcon.web 1 is the option Facepunch suggests, because it lets web-based tools connect.

Facepunch hosts a web RCON tool. Its page notes the tool is not HTTPS, so avoid using it on public Wi-Fi. A strong, unique password matters most. Anyone with the RCON password has full control of your server. Never post it in Discord or in a screenshot.

Admin commands worth knowing

Once you are an owner, these commands from Facepunch's useful commands page are the ones you will use most. Run them in the server console, over RCON, or in your F1 console once you are admin.

find is the one to remember. If you do not know a command's exact name, type find and a word, such as find ban, and the console lists the matches. For lag, Rust server lag: how to fix low server FPS uses fps and status to track down the cause.

Running admin commands on a hosted server

On a hosted server you do not need to open an RCON port to get started. The Console page in the panel sends commands straight to your server, so users and ownerid work from there. RCON is for tools that run outside the panel, such as a web console or a Discord bot. If you want one, set the password first and keep it private.

Admins and plugins

If you run Oxide, an owner is added to Oxide's admin group on their own. Oxide's permissions guide says the admin group is assigned to ownerid admins automatically, and default goes to everyone. Plugin permissions are then granted to groups or to single players:

oxide.grant group admin pluginname.use

Carbon uses c.grant. How to install Oxide or Carbon on a Rust server covers permissions in more detail.

Keep your admin list safe

1. Give owner rights to as few people as you can, and use moderators for helpers.
2. Use your own SteamID64. One wrong digit gives admin to a stranger.
3. Back up your cfg folder now and then, so you can restore your admin list and bans.
4. Change the RCON password when a helper leaves.
5. Remove old admins from users.cfg when they stop helping.

If the command does not work

• You did not reconnect. The auth level appears when you join, so leave and join again.
• A wrong ID. Run users again and copy the ID exactly, with no spaces.
• You ran it in the wrong place. Run it in the server console or over RCON, not in a player's F1 console.
• The file was edited while the server ran. Stop the server first when you edit users.cfg.

FAQ

Hosting for this game

• Rust server hostingOxide, Carbon, custom maps and your own wipe schedule