iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Godlike.Host offers hosted Rust servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
Oxide, now commonly called uMod, is the modding framework that lets a Rust server load server-side plugins. A reliable installation requires a stopped server, the archive matching your operating system, and the extracted files copied into the Rust installation’s RustDedicated_Data directory. You then verify the framework from Rust’s in-game console with oxide.version.
The procedure below covers self-hosted Windows and Linux servers, managed control panels, version updates, and the failure messages most often seen after a Rust update.
Recommended Free Tools
What Oxide (uMod) does on a Rust server
Rust’s dedicated server is vanilla until a modding framework is added. Oxide/uMod provides the hooks and console commands that allow C# plugins to respond to events such as player connections, chat, building, death, raids, and server commands. Plugins are separate files; Oxide is the runtime that loads and manages them.
Installing Oxide does not by itself add kits, teleportation, moderation tools, economy features, or other gameplay changes. Those functions come from individual plugins, which must be compatible with the Rust and Oxide versions running on your server.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application:Upgraded attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Warranty & Support: Our Electric air duster comes with 5 years warranty and 24/7 customer service. During this period, if you have any questions,pls kindly feel free to contact us.
The official installation guidance is maintained by OxideMod documentation. File layouts can change when Rust’s dedicated-server package changes, so use the current guide if the directory described by your server host differs from the one below.
Before you install: requirements and safety checks
- A working Rust dedicated server. Complete the normal server setup first and confirm that it starts without Oxide.
- File access. You need an FTP/SFTP client such as FileZilla or a host control panel with a file manager. On a self-hosted machine, local filesystem access is sufficient.
- A maintenance window. Stop the Rust server before changing its files. Installing while the process is running can leave files locked, partially copied, or loaded inconsistently.
- A backup. Copy your server configuration, identity files, world saves, and any existing
oxidedirectory before replacing files. Oxide normally does not erase those items, but a backup gives you a rollback path. - The correct operating-system package. Windows and Linux use different archives; selecting the wrong one is a common reason for a server that starts without Oxide.
Record your server’s current Rust build or update date before downloading. Oxide releases track Facepunch server changes, so the package must support the Rust build you are actually running.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Find the Rust server directory
The target is the directory that contains the Rust dedicated-server files. On Windows you will normally see RustDedicated.exe; on Linux the executable is commonly named RustDedicated. The official Oxide procedure places the extracted files in the RustDedicated_Data folder inside that server directory.
Do not confuse the server root with a SteamCMD installation folder that contains only the SteamCMD client. If you manage several Rust instances, identify the instance whose start script launches the server you intend to modify. A control panel may hide the absolute path; its file manager’s top-level Rust directory is the equivalent location.
When your host shows a different layout
Some older third-party instructions tell users to extract Oxide directly into the server root. The official installation location is RustDedicated_Data, so follow the current Oxide documentation and your host’s current instructions if the two layouts conflict. Never scatter files across both locations as a trial-and-error fix; that can produce a mixed installation that is harder to remove.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
Download the matching Oxide release
- Open the Oxide GitHub releases page from the official Oxide project.
- Choose the newest release that is not marked “Pre-release.” A pre-release build may target an upcoming Rust update and is not the normal choice for a production server.
- Choose the archive for the server operating system:
Oxide.Rust.zipfor Windows orOxide.Rust-linux.zipfor Linux. - Save the archive locally and check that the download completed before extracting it. A partially downloaded ZIP can produce missing DLLs or shared libraries that look like a version problem.
Do not select an archive solely because its date is newer. The important match is the Rust server build. After a Facepunch update, wait for the corresponding Oxide build if one is not yet available; forcing an older framework onto a newer server is more likely to break plugin loading than to provide a temporary solution.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsInstall Oxide on a self-hosted Windows server
- Stop the server. Close the Rust server console or use your service manager to stop the instance. Wait until the process has exited completely.
- Extract to a temporary folder. Open the downloaded
Oxide.Rust.zipin an archive utility and extract all contents somewhere outside the Rust server directory, such as a folder on your desktop. This makes it clear which files belong to the release and prevents an archive tool from nesting them in the wrong place. - Open the destination. Browse to the Rust server directory and then enter
RustDedicated_Data. - Copy the extracted contents. Copy the files and folders from the temporary extraction into
RustDedicated_Data. Keep the directory structure from the archive; do not copy only a DLL or only the top-level folder. - Allow replacements. If Windows asks whether to overwrite existing files, accept the replacement for the files supplied by the Oxide release. Do not delete world saves, configuration files, or unrelated server data to make room.
- Start normally. Use the same batch file, shortcut, service definition, or panel command that previously started the server. Do not substitute a different executable or add a second server process.
Watch the startup console during the first launch. Oxide should identify itself during initialization. A clean vanilla startup with no Oxide messages usually means the files were copied to the wrong directory, the archive did not match Windows, or an old start procedure is launching a different Rust installation.
Install Oxide on a self-hosted Linux server
- Stop the instance. Use the service manager, terminal session, or hosting panel that controls the Rust process. Confirm that no
RustDedicatedprocess remains before editing files. - Extract outside the server tree. Unpack
Oxide.Rust-linux.zipinto a temporary directory. Avoid extracting over the live server because an archive utility can create an extra nested directory. - Locate the data directory. Enter the Rust server directory and then
RustDedicated_Data. The directory should belong to the same instance referenced by your start script or service unit. - Copy the release files. Copy the complete extracted contents into
RustDedicated_Data, preserving permissions and subdirectories. If your transfer method changes permissions, restore executable permission on files that were executable in the original server installation. - Handle overwrite prompts carefully. Replace files from an older Oxide installation when asked, but leave saves and configuration data intact.
- Start with the existing service or script. Reuse the command that starts this Rust instance, then monitor its terminal output or service log.
Linux hosts often run several instances under separate users. Ensure the account that runs Rust can read the copied files and write to the directories Oxide creates. A permission error can look like a failed Oxide installation even when the archive and path are correct.
Install through a managed Rust hosting panel
Many managed Rust hosts provide a one-click uMod or Oxide installer. The labels vary, but the workflow is usually:
- Stop the server from the control panel.
- Open the panel’s Mod Manager, Mods, or similarly named section.
- Choose uMod or Oxide and click Install.
- Wait for the panel to report completion rather than closing the page during the file operation.
- Start the server again and inspect the live console.
A managed installer reduces file-path and archive-selection mistakes, and some hosts apply framework updates automatically. The trade-off is timing and control: you depend on the host to publish a compatible build, expose the required files, and decide when updates occur. If the panel offers both automatic and manual updates, read its version policy before enabling automation on a server with many plugins.
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
Verify that Oxide loaded
Startup text is useful, but the definitive basic check is an in-game console command:
- Join the server as an administrator.
- Press
F1to open Rust’s in-game console. - Enter
oxide.versionand submit it. - Confirm that the console prints an Oxide version instead of an unknown-command error.
If the command returns a version, the framework is loaded for that server process. Save the displayed version alongside the Rust build number; that pairing is valuable when diagnosing a later update. If oxide.version is not recognized, use the troubleshooting branches below before installing plugins.
Troubleshoot an installation that does not load
There are no Oxide messages at startup
- Confirm that the server was fully stopped while files were copied.
- Check that the files are inside
RustDedicated_Data, not one level above it, in a SteamCMD directory, or in a second Rust instance. - Verify that you used
Oxide.Rust.zipon Windows orOxide.Rust-linux.zipon Linux. - Make sure the start command is launching the instance you modified.
- Remove an accidental extra nesting level, such as
RustDedicated_DataOxide.Rust..., and copy the archive’s contents rather than its containing folder.
oxide.version says the command is unknown
An unknown command means the running process did not load Oxide. Recheck the destination path and startup console first. Then compare the Oxide package with the Rust build. Installing plugins or changing permissions will not fix a framework that never initialized.
The server starts, but every plugin fails
After a Rust update, an older Oxide build can start far enough to expose commands while still being incompatible with plugins or game assemblies. Stop the server, obtain the Oxide release that supports the current Rust build, replace the framework files, and start again. If only one plugin fails after the framework is confirmed current, remove that plugin temporarily and check its own compatibility notes rather than repeatedly reinstalling Oxide.
The server refuses to start after a Rust update
Do not assume the save is lost. First stop attempts to launch the same incompatible combination repeatedly, then check whether a matching Oxide release is available. The framework must be updated for each relevant Facepunch server update. If the host has an automated Rust update, ask whether it also updates uMod and whether it can hold the server on a compatible build.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
SteamCMD keeps reverting the server to vanilla
A frequent mistake is allowing the start script to run SteamCMD every time the server starts. SteamCMD can replace the files you just installed, leaving a vanilla server. Separate update and start operations: update deliberately, then launch the server without an automatic SteamCMD step that overwrites the framework. The Oxide guide recommends the public beta branch for SteamCMD updates and warns against relying on the release branch when it is not synchronized with the public Rust build.
Linux reports permission or shared-library errors
Check ownership and read/execute permissions for the account running Rust, then inspect the service log for the first error rather than the final cascade of plugin failures. Re-copy the Linux archive if files are incomplete. Do not use the Windows archive on Linux or attempt to solve an architecture mismatch by renaming files.
Keep Oxide synchronized with Rust
Version matching is ongoing maintenance, not a one-time installation detail. Facepunch server updates can change the assemblies Oxide hooks, so an Oxide update is expected for each relevant Rust update. Before applying a Rust update on a busy server:
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →- Record the current Rust and Oxide versions.
- Back up configuration, saves, and the existing
oxidedata. - Check the Oxide release notes or official documentation for support for the new Rust build.
- Schedule downtime and stop the server.
- Update Rust using your normal method, then install the matching Oxide archive.
- Start the server without an automatic SteamCMD step that could overwrite Oxide.
- Run
oxide.versionand test critical plugins before announcing the server open.
If no compatible Oxide release exists yet, keeping the server on its previous compatible Rust build is safer than mixing versions, provided your hosting arrangement allows that choice and you understand the security and player-compatibility implications.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Adding plugins after Oxide works
Install and verify the framework before introducing third-party code. Conventional uMod layouts use an oxide/plugins directory, with C# plugin files using the .cs extension. Because plugin folder conventions and loader behavior can change, confirm the current path in the official plugin-installation documentation for your Oxide release before uploading files.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
- Stop the server or use the loader’s documented reload method.
- Upload one plugin at a time so a failure is attributable to a specific file.
- Place the plugin in the documented plugins directory and preserve its filename.
- Start the server and read the Oxide console output for compile errors, missing dependencies, or permission messages.
- Test the plugin in game before adding another.
Keep a record of plugin versions and dependencies. A plugin compiled for an older Rust or Oxide API may fail even when oxide.version reports a healthy framework.
Self-hosted installation versus a managed panel
| Consideration | Self-hosted server | Managed host |
|---|---|---|
| File control | Direct control of archives, paths, permissions, and backups. | Usually limited to the panel and the file access the host exposes. |
| Installation method | Manual extraction and copying into RustDedicated_Data. |
Often a Mod Manager button for uMod/Oxide. |
| Updates | You must coordinate Rust, Oxide, SteamCMD behavior, and plugins. | The host may offer one-click or automatic updates, subject to its schedule. |
| Version control | You choose when to update and can hold a compatible build if supported. | The host controls available versions and update timing. |
| Typical failure source | Wrong path, wrong archive, permissions, or a start script that runs SteamCMD. | Panel installation timing, unavailable compatible build, or host-specific file layout. |
Choose self-hosting when you need complete control over versions and maintenance windows and are comfortable managing files. A managed panel is simpler when you prefer a guided install and can accept host-dependent timing and access.
Free tools Windows power users keep installed
One-click scans. No signup required.
Removal and rollback
If Oxide causes a problem, stop the server before changing files. Keep your backup of the pre-installation data, then restore the files you backed up or remove only the Oxide framework files identified by the current official documentation. Preserve world saves and configuration unless you intentionally want to roll them back. Start the vanilla server and confirm that the issue is isolated before attempting a fresh installation with a release that matches your Rust build.
Quick installation checklist
- Server is fully stopped.
- Backup is complete.
- Rust and Oxide target builds are compatible.
- Windows archive is
Oxide.Rust.zip; Linux archive isOxide.Rust-linux.zip. - Archive was extracted to a temporary location first.
- Contents were copied into
RustDedicated_Data. - Existing files were overwritten only where appropriate.
- Start script does not run SteamCMD in a way that replaces Oxide.
- Startup console shows Oxide initialization.
oxide.versionprints a version in the F1 console.- Plugins are added only after the framework check succeeds.
Frequently Asked Questions
Which Oxide archive should I use for Rust?
Use Oxide.Rust.zip for a Windows server and Oxide.Rust-linux.zip for a Linux server. Choose the latest stable release that supports your Rust build, not merely the newest dated file.
Why does oxide.version not work?
The running server process has not loaded Oxide. Check that the files are in RustDedicated_Data, that the archive matches the operating system, and that your start command launches the instance you modified.
Can I install Oxide while the Rust server is running?
No. Stop the server completely before copying or replacing framework files, then restart it with the normal launch command.
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 →What should I do when Rust updates before Oxide?
Wait for an Oxide release compatible with the new Rust build or keep the server on a compatible build if your setup permits it. Do not rely on an older framework simply because the server starts.
Where do uMod plugins go?
The conventional location is oxide/plugins, with C# files ending in .cs. Verify the current plugin-installation instructions for your Oxide release before uploading files.
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.
