The reliable way to whitelist a Rust server is to run Oxide/uMod and install the community Whitelist plugin. Rust’s dedicated-server software does not provide a native, permission-based whitelist. Once the plugin is loaded, give each approved player the whitelist.allow permission by Steam64 ID, then test both an approved and an unapproved account.
Playing with friends? Godlike.Host runs hosted Rust servers from 10 data-center locations, with free DDoS protection.
That controls admission, but it does not automatically hide the server from the server browser or query tools. If the server must be private for a small group, combine the permission setup with firewall and discovery controls described below.
As an Amazon Associate I earn from qualifying purchases.
What you need before you start
Prepare these items before changing the server. Missing any one of them usually leads to a server that appears configured but either lets nobody in or is difficult to maintain.
- A running Rust dedicated server with administrator or root/RCON access. You need a console from which Oxide commands can be executed.
- Oxide/uMod installed for the exact Rust server build. The framework must match the game-server update. A Rust update can require reinstalling or updating Oxide/uMod before plugins will load.
- The Whitelist plugin file. Keep the plugin’s
.csfile in the server’soxide/plugins/directory. - Every player’s Steam64 ID. The permission is attached to this numeric account identifier, not to a display name. Record the ID for each person you intend to admit.
- A backup plan. Before updates, copy the identity-specific
cfgdirectory and the plugin configuration directory so you can restore settings if a framework or wipe changes files.
Facepunch’s server documentation identifies the identity-specific configuration location as rust/server/server.identity/cfg/. Replace server.identity with the actual identity used by your installation. The administrative users.cfg file is kept beside server.cfg in that directory; plugin settings are stored in the plugin configuration directory.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
How the permission whitelist works
The framework loads the Whitelist plugin, and the plugin checks whether a connecting Steam64 ID has whitelist.allow. A player with that permission is admitted; a player without it receives the plugin’s not-whitelisted response. Permission changes are made with Oxide’s user-permission commands and can be reversed without editing the plugin source.
This is separate from administrator status. An owner or moderator entry in users.cfg gives administrative capabilities, while whitelist.allow controls admission. A person can therefore be allowed to play without being given server-admin powers.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Set up the whitelist step by step
1. Install or update Oxide/uMod
- Download the Rust-compatible Oxide/uMod build for your server version.
- Extract it into the Rust server installation as directed by the framework’s installation instructions. Do not place the files in a client-side Rust folder.
- Start or restart the dedicated server.
- Watch the server console for framework load messages and resolve any version or file errors before installing the plugin.
If the server has just received a Rust update, perform this compatibility check even if Oxide/uMod was working previously. A plugin that worked before the update may remain in the directory but fail to load under an incompatible framework.
2. Install the Whitelist plugin
- Download the current Whitelist plugin file.
- Copy its
.csfile intooxide/plugins/under the active Rust server installation. - Restart the server, or load the plugin through the Oxide command system if you are already operating the console.
- Confirm in the console that the plugin loaded without an exception. If it did not, fix the reported dependency, path, or framework problem before granting permissions.
The plugin’s configuration file is created in the framework’s plugin configuration directory after its first successful load. Do not edit a configuration file that was never generated; that generally indicates the plugin did not load.
3. Collect and verify Steam64 IDs
Use each player’s Steam64 ID exactly as supplied, including all digits. Names can change and may contain spaces or punctuation, so they are unsuitable as the permission key. Keep a private roster that maps a person to the numeric ID you granted.
Administrative entries use the same identity-specific cfg directory. If you need to make yourself an owner or moderator for console access, use the documented ownerid or moderatorid format in users.cfg. That step is not a substitute for granting whitelist.allow.
Recommended Free Tools
4. Grant each player access
From the server console, RCON, or an authorized in-game F1 console, run:
oxide.grant user <Steam64ID> whitelist.allowFor example, replace the token with the player’s real Steam64 ID:
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
oxide.grant user 7656119XXXXXXXXXX whitelist.allowRepeat the command once for every approved account. Facepunch’s hidden-server instructions also show the shorter alias:
o.grant user <Steam64ID> whitelist.allowUse one command form consistently when documenting your server procedures. After each grant, check the console response for a successful permission assignment rather than assuming a mistyped ID was accepted.
Free tools Windows power users keep installed
One-click scans. No signup required.
5. Test both sides of the rule
- Have an approved account connect while the server is running. This verifies that the plugin is loaded and the ID was entered correctly.
- Temporarily remove that account’s permission:
oxide.revoke user <Steam64ID> whitelist.allow- Attempt a connection from that account and from another account that has never been granted access. Both should be treated as not whitelisted by the plugin.
- Restore the approved player:
oxide.grant user <Steam64ID> whitelist.allowThis check is an operational procedure, not a claim that every server configuration behaves identically. Confirm the actual console messages and player-facing response on your own deployment, especially after a Rust or framework update.
6. Reload after configuration changes
If you change the plugin’s settings file while the server is running, reload it with:
oxide.reload WhitelistReload only after saving a backup of the configuration. A reload can briefly reinitialize the admission check; perform it during a quiet period and then reconnect with a permitted account.
Where the files and permissions persist
Keep the server identity organized so updates do not silently target a different instance:
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchrust/server/server.identity/cfg/server.cfgcontains server settings for that identity.rust/server/server.identity/cfg/users.cfgcontains documented owner and moderator entries.- The framework’s plugin directory contains the Whitelist
.csfile, normally underoxide/plugins/. - The framework’s configuration directory contains the plugin’s generated settings file.
Back up these locations before a wipe, framework replacement, or Rust update. After restarting, verify that the plugin appears in the console and that a known approved ID still has access. If you restore a server to a different identity, make sure you copied the corresponding cfg directory rather than an unrelated instance’s files.
Managing the approved-player roster
A whitelist is easiest to operate when the roster is treated as an access list rather than an informal chat message. Keep the player’s name, Steam64 ID, date added, and who approved the request in a private administrator record. The name helps humans identify the account, but only the numeric ID belongs in the permission command. Remove access promptly when someone leaves the group by running the revoke command, and record the change so another administrator can understand why a connection was denied.
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
Do not grant the permission to a shared Steam account or to an ID copied from an unverified profile. Ask the player to provide the ID through a private channel, compare it with the account that actually connects, and avoid posting the roster in public Discord channels, screenshots, or stream overlays. A whitelist limits entry; it does not protect the IDs or server endpoint that administrators disclose.
For a larger community, designate at least two trusted administrators who can use RCON or the server console. Document the exact grant and revoke syntax, the active server identity, and the backup location. This prevents a single unavailable operator from becoming the only person able to admit a new player or repair an accidental removal.
A simpler option for a tiny trusted group: skip-queue
Facepunch documents a built-in approach that can be useful when only a few trusted people need a shortcut into a private server. It is not the same permission-based admission workflow: it changes queue behavior rather than using the Whitelist plugin’s per-player permission check.
- Set the maximum player value to zero:
server.maxplayers 0- Add each approved Steam ID in
users.cfgwith:
global.skipqueueid <id> [name] [note]The bracketed name and note are optional annotations. The account ID is the important part. Because this method has different semantics, do not describe it to players as interchangeable with a whitelist. It is best suited to a very small group that you trust and can manage directly; larger communities generally need explicit permission grants and revokes.
Make the server private and harder to discover
Admission control and discoverability are two separate problems. A player can be denied by the plugin while the server still exposes its address, player names, or metadata to public listings and query tools. For a genuinely private deployment, apply the following controls in addition to whitelist.allow.
Block the Steam query port
Use firewall rules to block the Steam query endpoint from the public internet. The relevant setting is server.queryport. Blocking that port reduces the information available to server-list scrapers and query clients, but it does not grant anyone access; the permission plugin remains necessary.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsChoose ports deliberately
Use nonstandard game and RCON ports where appropriate, and restrict RCON to trusted network addresses with firewall rules. A nonstandard port is not authentication, but it reduces casual scanning and makes an accidentally published default endpoint less useful.
Protect the connection endpoint
Players who already know the endpoint can connect directly, so do not paste it into public chat, screenshots, stream overlays, or logs that viewers can read. A streamer can bind a private client key to connect without displaying the endpoint in visible console history:
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
bind f6 "client.connecthidden IP:PORT;console.clear"Replace IP:PORT with the actual endpoint. Treat the keybind as an exposure-reduction measure, not as a replacement for firewalling or permission checks.
Reduce player-name exposure
Set:
censorplayerlist trueThis masks player names from third-party list scrapers. It does not make the server invisible and does not affect whether the Whitelist plugin accepts a connection.
Keep account visibility private
Ask members not to publish their Steam game visibility or the private server endpoint. These personal-account and operational controls complement the server-side firewall; neither one changes the plugin’s allow list.
Update and recovery checklist
Use the same short routine after every Rust update, Oxide/uMod replacement, wipe, or move to a new host:
- Stop the server cleanly and copy the identity’s
cfgdirectory, plugin file, and plugin configuration. - Install the Rust-compatible framework build before troubleshooting individual permissions.
- Start the server and confirm framework and Whitelist load messages in the console.
- Check that
server.cfg,users.cfg, and the plugin configuration belong to the intended server identity. - Test one known approved ID and one unapproved account.
- Only then announce the server endpoint or reopen access.
This sequence catches the common mistake of restoring files to one identity while players connect to another. It also distinguishes a framework failure from a bad Steam64 ID, saving time when a previously approved player is rejected.
Whitelist commands at a glance
| Purpose | Command | Where to run it |
|---|---|---|
| Grant admission | oxide.grant user <Steam64ID> whitelist.allow |
Server console, RCON, or authorized F1 console |
| Grant admission using the short alias | o.grant user <Steam64ID> whitelist.allow |
Same administrative consoles |
| Remove admission | oxide.revoke user <Steam64ID> whitelist.allow |
Server console, RCON, or authorized F1 console |
| Reload plugin settings | oxide.reload Whitelist |
Server console or authorized Oxide console |
| Enable skip-queue alternative | server.maxplayers 0 |
Server console or configuration workflow |
| Add a skip-queue account | global.skipqueueid <id> [name] [note] |
users.cfg / server administration |
| Query endpoint to protect | server.queryport |
Firewall and server configuration planning |
| Mask player names | censorplayerlist true |
Server console or configuration |
Troubleshooting common failures
The plugin never appears to load
- Confirm the file is in the active server’s
oxide/plugins/directory, not another Rust installation. - Check that Oxide/uMod is installed for the current Rust build.
- Read the console for compile errors, missing dependencies, or permission failures.
- Restart after correcting the problem, then verify that the plugin configuration file was generated.
An approved player is rejected
- Compare the granted value with the player’s complete Steam64 ID; a display name or truncated number will not work.
- Run the grant command again from an administrator-authorized console.
- Make sure you granted
whitelist.allowto the same server identity the player is joining. - Check that a recent plugin reload or framework update did not remove the loaded permission state.
A rejected player can still see the server
That is expected when only admission is configured. Add query-port firewalling, endpoint handling, and player-list censoring if the goal is to reduce discovery. Those measures limit information exposure; they do not alter the allow list.
Permissions disappear after an update
Stop treating updates as a file-copy operation. Back up server.cfg, users.cfg, the plugin file, and plugin configuration first; confirm the server identity after the update; then verify framework and plugin load messages and test one approved account. If the framework was replaced, reinstall the Rust-compatible build before diagnosing individual permissions.
RCON commands are ignored
Check that RCON is enabled, that you are connected to the correct port, and that the account has administrative authorization. If the command works in the local server console but not through RCON, the problem is the RCON connection or privilege path rather than the whitelist syntax.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
Listing and policy implications
Facepunch’s current plugin guidance places gameplay-changing or user-interface plugins under the Modded section. Before advertising a server as Community, check the current policy and consider what the Whitelist plugin changes. Classification rules can change, so do not assume that an earlier listing decision remains valid after a plugin or game update.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Which approach should you choose?
| Requirement | Oxide/uMod plus Whitelist | Skip-queue method |
|---|---|---|
| Native game feature | Uses a framework and community plugin | Uses documented server commands and users.cfg |
| Per-player permission management | Explicit grant and revoke with whitelist.allow |
Maintains skip-queue IDs instead |
| Best fit | Groups that need clear, reversible admission control | A very small, trusted group needing queue bypass |
| Discovery control | Must be added separately with firewall and privacy measures | Must be added separately with firewall and privacy measures |
| Update work | Keep framework and plugin aligned with Rust updates | Maintain identity files and verify server settings after updates |
| Policy consideration | Plugin effects may require Modded classification | Check current listing rules for the resulting server setup |
For most friend groups, communities, and event servers that need an auditable list, use the plugin workflow: install the matching framework, grant whitelist.allow by Steam64 ID, test a rejection, and back up the identity files. Use skip-queue only when its queue-oriented behavior is exactly what the group wants. Add network controls whenever “private” also means difficult to find.
Frequently Asked Questions
Does Rust have a built-in whitelist?
No. Rust’s dedicated server has no native permission-based whitelist. Facepunch’s documented approach is Oxide/uMod plus the community Whitelist plugin. The built-in skip-queue commands are a different access method.
What command adds a player to a Rust whitelist?
Run oxide.grant user <Steam64ID> whitelist.allow from the server console, RCON, or an authorized F1 console. The shorter o.grant user <Steam64ID> whitelist.allow alias is also documented.
How do I remove someone?
Run oxide.revoke user <Steam64ID> whitelist.allow. The permission is tied to the Steam64 ID, so revoking it does not depend on the player’s current display name.
Can I hide a whitelisted server from the server list?
A whitelist controls admission, not discovery. Block the Steam query port with firewall rules, consider nonstandard game and RCON ports, keep the endpoint out of public posts, use censorplayerlist true, and protect streamer connection commands. These steps reduce exposure but do not replace the plugin.
Why is an approved player still denied?
Verify the complete Steam64 ID, confirm the grant was run on the identity the player is joining, check that Oxide/uMod and Whitelist loaded without errors, and repeat the grant from an authorized console. Test again after any framework update or plugin reload.
What should I back up?
Back up the active identity’s server.cfg, users.cfg, the Whitelist plugin file, and its generated configuration directory before a Rust update, framework replacement, wipe, or host move.
Should I use skip-queue instead of the plugin?
Use skip-queue only for a very small, trusted group that wants queue bypass. Set server.maxplayers 0 and add IDs with global.skipqueueid <id> [name] [note]. It does not provide the same explicit grant-and-revoke permission workflow.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Will the plugin affect server listing classification?
Facepunch’s current guidance places gameplay-changing or user-interface plugins under Modded. Check the current listing policy before advertising a plugin-enabled server as Community, because classification rules can change.
The Bottom Line
Rust has no native permission whitelist. Install a Rust-matched Oxide/uMod build and the Whitelist plugin, grant whitelist.allow to each verified Steam64 ID, test both admission and rejection, and back up the active identity files. If privacy also means low discoverability, add query-port firewalling, endpoint protection, and player-list censoring. Use skip-queue only when its queue-bypass behavior fits your small trusted group.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
