[{"data":1,"prerenderedAt":31},["ShallowReactive",2],{"doc-en-become-admin-rust-server":3},{"path":4,"slug":5,"title":6,"description":7,"category":8,"subcategory":9,"icon":10,"date":11,"author":12,"order":13,"image":14,"tags":15,"keywords":20,"docGroup":28,"docGroupIcon":28,"link_fr":29,"bodyHtml":30},"\u002Fdocs\u002Fen\u002Fgaming\u002Frust\u002Fbecome-admin-rust-server","become-admin-rust-server","How to Become an Admin on a Rust Server","Become owner or moderator of your Winheberg Rust server with ownerid and the SteamID64, remove rights with removeowner and secure the RCON password.","jeux","rust","tabler:file-text","2026-11-01","Winheberg",115,"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fgaming\u002Frust\u002Fbecome-admin-rust-server.webp",[16,17,18,19],"Rust","Administration","RCON","Game panel",[21,22,23,24,25,26,27],"rust server admin","rust ownerid","rust moderatorid","rust rcon","rust steamid64","rust hosting","rust admin commands","","\u002Fdocs\u002Frust\u002Fdevenir-admin-serveur-rust","\u003Ch2>Context\u003C\u002Fh2>\n\u003Cp>To ban a cheater, teleport or spawn items on your Rust server, you need to be an \u003Cstrong>administrator\u003C\u002Fstrong>. Rust has two levels, \u003Cstrong>owner\u003C\u002Fstrong> and \u003Cstrong>moderator\u003C\u002Fstrong>, granted with a simple console command using the player's \u003Cstrong>SteamID64\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>This guide shows you how to give yourself rights on your Winheberg Rust server, how to remove them, and how to secure \u003Cstrong>RCON\u003C\u002Fstrong> access, which lets you manage the server remotely with a dedicated tool.\u003C\u002Fp>\n\u003Ch2>Prerequisites\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>An active \u003Cstrong>Rust server\u003C\u002Fstrong> on your \u003Ca href=\"https:\u002F\u002Fpanel.winheberg.com\">Winheberg gaming panel\u003C\u002Fa>, with the \u003Cstrong>Online\u003C\u002Fstrong> status\u003C\u002Fli>\n\u003Cli>The \u003Cstrong>SteamID64\u003C\u002Fstrong> of the player to promote, a 17-digit ID starting with \u003Ccode>7656119\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>A custom \u003Cstrong>RCON PASSWORD\u003C\u002Fstrong> in the \u003Cstrong>Startup\u003C\u002Fstrong> tab, as explained in step 5. With the default \u003Ccode>CHANGEME\u003C\u002Fcode> value, the panel console cannot send any command to the server\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>1. Find the player's SteamID64\u003C\u002Fh2>\n\u003Cp>Unlike the player name, the SteamID64 never changes. Here are two easy ways to find it.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>In Steam, open the player's profile, right-click on the page and choose \u003Cstrong>Copy Page URL\u003C\u002Fstrong>. If the URL ends with a string of 17 digits, that is the SteamID64\u003C\u002Fli>\n\u003Cli>If the profile uses a custom URL, paste it into a converter such as \u003Ca href=\"https:\u002F\u002Fsteamid.io\u002F\">steamid.io\u003C\u002Fa>, which shows the \u003Cstrong>steamID64\u003C\u002Fstrong> line\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>2. Grant rights from the console\u003C\u002Fh2>\n\u003Cp>Open your server \u003Cstrong>Console\u003C\u002Fstrong> in the panel. Type the command in the \u003Cstrong>Type a command...\u003C\u002Fstrong> field, \u003Cstrong>without a \u003Ccode>\u002F\u003C\u002Fcode> in front\u003C\u002Fstrong>, replacing the SteamID64 and the name.\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">ownerid 76561198000000000 "MyName"\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The name in quotes is only a label in the administrator list. Rust has two levels of rights.\u003C\u002Fp>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Command\u003C\u002Fth>\n\u003Cth>Level\u003C\u002Fth>\n\u003Cth>Use\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>\u003Ccode>ownerid <SteamID64> "name"\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Owner, level 2\u003C\u002Ftd>\n\u003Ctd>Full access to administration commands\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>moderatorid <SteamID64> "name"\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Moderator, level 1\u003C\u002Ftd>\n\u003Ctd>Moderation commands, for your trusted team\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003Cp>The change is \u003Cstrong>saved automatically\u003C\u002Fstrong> in the \u003Ccode>server\u002Frust\u002Fcfg\u002Fusers.cfg\u003C\u002Fcode> file. It survives restarts, there is nothing else to do.\u003C\u002Fp>\n\u003Cdiv class=\"markdown-alert markdown-alert-important\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Cpath d=\"M12 22c5.523 0 10-4.477 10-10S17.523 2 12 2 2 6.477 2 12s4.477 10 10 10z\"\u002F>\u003Cpath d=\"M12 8v4\"\u002F>\u003Cpath d=\"M12 16h.01\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>The player must \u003Cstrong>disconnect and reconnect\u003C\u002Fstrong> to the server for their new rights to apply.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Cdiv class=\"markdown-alert markdown-alert-note\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cline x1=\"12\" y1=\"16\" x2=\"12\" y2=\"12\"\u002F>\u003Cline x1=\"12\" y1=\"8\" x2=\"12.01\" y2=\"8\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>If the console replies \u003Ccode>Unable to run "ownerid" due to RCON not being connected yet.\u003C\u002Fcode>, the server has not finished starting. Wait for the \u003Cstrong>Online\u003C\u002Fstrong> status and type the command again.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>3. Use the commands in game\u003C\u002Fh2>\n\u003Cp>Once reconnected, the player opens the Rust console with the \u003Cstrong>F1\u003C\u002Fstrong> key. They can type administration commands there, still without \u003Ccode>\u002F\u003C\u002Fcode>. For example, \u003Ccode>kick\u003C\u002Fcode> and \u003Ccode>ban\u003C\u002Fcode> followed by the player name, or \u003Ccode>banid\u003C\u002Fcode> followed by the SteamID64 to ban a player who is offline.\u003C\u002Fp>\n\u003Cp>If you use Oxide, owners are also automatically added to the Oxide \u003Ccode>admin\u003C\u002Fcode> group, which gives them the permissions your plugins set aside for administrators. Moderators are not, so grant them the permissions you want with \u003Ccode>o.grant\u003C\u002Fcode>. It is all explained in our guide \u003Cstrong>"How to Install Oxide or Carbon and Plugins on a Rust Server"\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Ch2>4. Remove a player's rights\u003C\u002Fh2>\n\u003Cp>Type the command matching their level in the panel console.\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">removeowner 76561198000000000\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cpre>\u003Ccode class=\"language-bash\">removemoderator 76561198000000000\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The removal is also saved automatically in \u003Ccode>users.cfg\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Ch2>5. Secure and use RCON\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>RCON\u003C\u002Fstrong> lets you send commands to the server from an external tool, without opening the panel. It is protected by a password, set in the \u003Cstrong>Startup\u003C\u002Fstrong> tab.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fgaming\u002Frust\u002Fbecome-admin-rust-server-1793567288479-a97c57bbbba43cb20165e90a.webp\" alt=\"RCON PORT and RCON PASSWORD variables in the panel Startup tab\" width=\"600\" \u002F>\n\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Variable\u003C\u002Fth>\n\u003Cth>Purpose\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>\u003Cstrong>RCON PORT\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>RCON port assigned to your server, read-only\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>RCON PASSWORD\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>Password required for every RCON connection\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003Cdiv class=\"markdown-alert markdown-alert-caution\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cline x1=\"12\" y1=\"8\" x2=\"12\" y2=\"12\"\u002F>\u003Cline x1=\"12\" y1=\"16\" x2=\"12.01\" y2=\"16\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>The default password is \u003Ccode>CHANGEME\u003C\u002Fcode>. As long as it is not replaced, RCON does not start and the panel console cannot run any command. \u003Cstrong>Replace it\u003C\u002Fstrong> with a long, unique password made of letters and digits, click outside the field to save it, then click \u003Cstrong>Restart\u003C\u002Fstrong>. Anyone who knows this password can take full control of the server.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Cp>To connect with a WebRCON-compatible RCON tool, enter your server address shown at the top of the panel (for example \u003Ccode>gm1-whXX.wh-game.fr\u003C\u002Fcode>), the \u003Cstrong>RCON PORT\u003C\u002Fstrong> instead of the game port, and your \u003Cstrong>RCON PASSWORD\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cdiv class=\"markdown-alert markdown-alert-note\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cline x1=\"12\" y1=\"16\" x2=\"12\" y2=\"12\"\u002F>\u003Cline x1=\"12\" y1=\"8\" x2=\"12.01\" y2=\"8\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>The panel console also uses RCON to send your commands. After changing the password, restart the server so that the console and the game both use the same one.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>If you run into trouble\u003C\u002Fh2>\n\u003Ch3>❌ The player does not have their rights in game\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Check that they disconnected and reconnected after the command\u003C\u002Fli>\n\u003Cli>Check the SteamID64, 17 digits, no spaces, and not the short ID in the \u003Ccode>STEAM_0:...\u003C\u002Fcode> format\u003C\u002Fli>\n\u003Cli>Open \u003Ccode>server\u002Frust\u002Fcfg\u002Fusers.cfg\u003C\u002Fcode> and check that their line is there\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>❌ The panel console does not run any command\u003C\u002Fh3>\n\u003Cp>If \u003Ccode>Waiting for RCON to come up...\u003C\u002Fcode> keeps looping long after \u003Ccode>Server startup complete\u003C\u002Fcode>, the console cannot connect to the server's RCON. The most common cause is the default password. Replace \u003Ccode>CHANGEME\u003C\u002Fcode> in \u003Cstrong>RCON PASSWORD\u003C\u002Fstrong> with a password made of letters and digits, then restart. When everything works, the console shows this line.\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">Connected to RCON. Generating the map now. Please wait until the server status switches to "Running".\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch2>Best practices\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Hand out the owner level sparingly\u003C\u002Fstrong>, the moderator level is enough for most members of your team\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Never share the RCON password\u003C\u002Fstrong>, it gives more power than any owner account\u003C\u002Fli>\n\u003Cli>\u003Cstrong>To delegate server management\u003C\u002Fstrong>, use a sub-user with limited permissions instead, as explained in our guide \u003Ca href=\"https:\u002F\u002Fwinheberg.com\u002Fen\u002Fdocs\u002Fpanel-gaming\u002Fadd-sub-user-gaming-panel\">How to Add a Sub-User to Your Gaming Panel\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Remove the rights\u003C\u002Fstrong> of a member who leaves your team, with \u003Ccode>removeowner\u003C\u002Fcode> or \u003Ccode>removemoderator\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Need help?\u003C\u002Fh2>\n\u003Cp>If the rights still do not apply after these checks, our team is here to help. Open a ticket in the \u003Cstrong>Technical\u003C\u002Fstrong> department from your \u003Ca href=\"https:\u002F\u002Fbilling.winheberg.com\">client area\u003C\u002Fa>, fill in the \u003Cstrong>Related Product\u003C\u002Fstrong> field with your Rust server and attach a screenshot of the console.\u003C\u002Fp>\n\u003Cp>Check out our plans on the \u003Ca href=\"https:\u002F\u002Fwinheberg.com\u002Fen\u002Fgaming\u002Frust\">Rust Hosting\u003C\u002Fa> page. Your Rust server is now in good hands 🔒\u003C\u002Fp>\n",1794353875306]