How to Install and View the Rust:IO Livemap on Your Rust Server

Rust:IO Remastered is a server extension loaded through uMod/Oxide. Install its Oxide.Ext.RustIO.dll in RustDedicated_Data/Managed, allow incoming TCP traffic on the game port, and open http://YOUR-SERVER-IP:YOUR-SERVER-PORT—not the RCON port—to view the live map. Hosted panels may offer the same installation through a Mod Manager.

Playing with friends? Godlike.Host runs hosted Rust servers from 10 data-center locations, with free DDoS protection.

What Rust:IO Remastered does

Rust:IO Remastered is an open reimplementation of the Rust:IO server core, revived for current Rust builds after the original playrust.io service went offline. Its manual describes it as an extension to the uMod (formerly Oxide) modding framework that adds a live map and a REST API to a Rust server. It is not affiliated with Facepunch Studios, so compatibility must be checked whenever Rust or uMod changes.

#	Preview	Product	Price
1		Rust Key Cards, Rust Red Key Card, Cobalt Restricted Access Cards, Rust Gift For Gamers, Blue Key...	$25.00	Buy on Amazon
2		Rust Video Game Notebook	$15.00	Buy on Amazon
3		Rust Game Props Large Furnace (S)	$14.99	Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

This is a server extension, not a normal C# plugin. Do not place Oxide.Ext.RustIO.dll in oxide/plugins; the loader expects it in the Rust server’s managed assembly directory. Once loaded, Rust:IO can expose map layers such as monuments, player and ally locations, events, grids and mortality. Building and loot information are administrator-only data in the Remastered manual, and sleeper or building visibility has privacy implications.

The extension also provides an API that other tools can use. That makes the installation more than a browser overlay: it is a service attached to the Rust process, with its own web endpoint, generated data file and access controls. Treat it like server infrastructure. A correct file path, compatible build and reachable TCP port are all required; having only one or two of those in place will not produce a working map.

#1 Best Overall

Rust Key Cards, Rust Red Key Card, Cobalt Restricted Access Cards, Rust Gift For Gamers, Blue Key Card, Green Key Card (ALL THREE)

• Inspired by the Rust Video Game – These cards replicate the iconic keycards found in Rust (Red, Blue, Green).
• High Quality PVC Plastic – Printed on both sides, durable and water-resistant. Not a sticker.
• Great Rust Gift Idea – Perfect for fans of Rust, whether for cosplay, loot-themed gifts, or collection.
• Wallet-Size Replica – Standard 3.375x2.125 inches, 30 mil thick—fits in any wallet.
• NOT a sticker*

$25.00

Buy on Amazon

Requirements before you install

• A running Rust dedicated server and a recent uMod/Oxide installation. The uMod Rust guide documents installation with umod install rust -P, and plugin documentation requires Oxide 2.0 or newer for plugins to load.
• Filesystem access to RustDedicated_Data/Managed, either directly on your machine or through a hosting panel’s Mod Manager, File Manager or SFTP.
• An inbound firewall rule for TCP on the game server port. Rust gameplay normally uses UDP, but the livemap web endpoint needs TCP.
• A separate RCON port. For example, with game port 28015, use 28016 for RCON rather than trying to bind both services to one port.
• A current backup. Stop the server before replacing managed files, and plan to update uMod/Oxide and Rust:IO after each Rust monthly update.

Facepunch’s server guidance requires Oxide to be updated after Rust updates. An extension compiled for an older build can stop loading even when its files and configuration have not changed.

Before downloading anything, record the actual game port, RCON port, public IP and provider’s restart method. Do not assume the number shown in a panel is the externally reachable port: NAT and provider forwarding can change what players use. You need the public game endpoint for the browser, while the server process still needs to bind to the address and ports configured by the host.

Choose an installation route

If you cannot reach the managed directory, cannot open TCP on the game port, or do not have restart and console access, a managed Rust host with uMod/Rust:IO support is the practical route. Confirm those capabilities with the provider before migrating.

Ask a prospective host specifically whether its Mod Manager installs the managed-directory extension or only ordinary plugins. Also ask who applies Rust:IO updates after a Rust monthly release, whether you can download backups before an update, and whether support can change firewall rules. A one-click button is useful only if the provider also exposes the required port and keeps the package compatible.

Install Rust:IO on a self-managed server

1. Back up and stop the server. Save the server files and configuration, then shut down the Rust process cleanly. Editing a live managed assembly can leave a partial or locked file.
2. Install or update uMod/Oxide. Use a current Rust-compatible release. If you are installing from the uMod command-line workflow, the documented command is umod install rust -P. Start only after the installation completes.
3. Download Rust:IO Remastered. Use the project’s current manual or download route. Avoid old guides that only reference the retired playrust.io service.
4. Copy the extension to the exact directory. Place Oxide.Ext.RustIO.dll directly in RustDedicated_Data/Managed. Do not rename the file or put it under oxide/plugins.
5. Check ports before starting. Keep the game port and RCON port distinct—for example, game 28015 and RCON 28016—and allow inbound TCP on the game port in addition to the UDP rules used for gameplay.
6. Start the server and watch the console. The loader downloads the remaining Rust:IO components automatically. Startup output should report that the extension initialized.
7. Verify the generated files. After a successful start, Rust:IO creates oxide/config/RustIO.json and its web-map data file at oxide/data/rustio/webmap.json.

If the startup log never mentions Rust:IO, stop the server and recheck the filename, directory, uMod/Oxide version and file permissions. Restarting after the upload is required.

Do not copy several different Rust:IO packages into the server while troubleshooting. Remove the old or duplicate file, restore your backup if needed, and test one compatible release. The loader’s automatic download of remaining components means a successful DLL load may be followed by additional startup messages; wait for the server to finish starting before testing the URL.

Install through a hosted control panel

Using a Mod Manager

1. Stop the server from the panel.
2. Open the panel’s Mod Manager and choose the entry named RUST.io Livemap or an equivalent Rust:IO package.
3. Install it, then open the Rust:IO configuration editor. One documented workflow uses oxideconfigRustIO.json.
4. Save the configuration and start the server. Check the live console for the extension initialization message.

Uploading with File Manager or SFTP

When no Mod Manager entry exists, upload Oxide.Ext.RustIO.dll to RustDedicated_Data/Managed while the server is stopped, then start it again. Some providers restrict the Managed directory; in that case, ask support to install the extension rather than placing it in oxide/plugins. A panel can also require a full restart before the loader sees a newly uploaded assembly.

Panel file managers often display Windows paths with different slash styles, but the destination is still the server’s RustDedicated_Data/Managed directory. Verify the upload completed rather than assuming a progress window means the file is on the live instance. If the panel runs more than one server, confirm you are editing the instance whose public IP and game port you will use.

Configure layers, broadcasts and access

Edit oxide/config/RustIO.json only when the server is stopped or when you can safely reload the extension. Keep the file valid JSON: an extra comma, a missing quote or an invalid value can cause the entire configuration to be ignored. After saving, run reload RustIO in the server console; use a restart if your host does not support extension reloads.

The web-map data file, oxide/data/rustio/webmap.json, contains the web service parameters documented by the project:

• webPort — the web endpoint port used by the map service.
• renderSize — the map rendering size.
• showSleepers — whether sleeping players can be shown.
• updateIntervalMs — the update interval in milliseconds.
• portalUrl — the configured portal address.
• secret — a generated secret used by the web-map setup.

Do not casually expose sleeper, building, loot or API information. Steam sign-in lets users locate themselves and allies, but authorization and the settings above determine what other layers they can see.

Rank #2

Rust Video Game Notebook

$15.00

Buy on Amazon

Make one configuration change at a time and reload before making another. This makes a malformed value easier to identify and lets you compare the console output with the previous working state. Keep a private copy of the API key and generated secret; replacing them unnecessarily can invalidate integrations that depend on the existing values.

Open the Rust:IO live map

1. Find the server’s external, publicly reachable IP address.
2. Use the game server port, not the RCON port, in the browser address: http://YOUR-SERVER-IP:YOUR-SERVER-PORT.
3. For example, a server at 203.0.113.10 using game port 28015 is opened at http://203.0.113.10:28015.
4. If your hosting panel has a RUST.io Livemap button, use it as an alternative; the panel should open the configured endpoint in a new window.
5. Allow a short delay after startup for the server to become discoverable. The manual says it may appear on playrust.me after a short delay, but direct IP access gives you control over the address and does not depend on a directory listing.

The interactive map can provide monument, grid, event, player and ally layers. Steam authentication is used for locating yourself and allies. Building, loot and sleeper visibility depends on server authorization and configuration.

If the browser shows a blank page, loading indicator or connection error, first distinguish a network failure from a map-data problem. A refusal or timeout usually points to the address, firewall, port or binding. A page that loads but lacks layers points instead to RustIO.json permissions or display settings. Test the direct URL from a device outside the server’s local network to avoid false results caused by router loopback behavior.

Fix a map that says the server is not responding

1. Check TCP before changing Rust:IO settings

A browser connection is different from normal Rust gameplay traffic. Confirm that inbound TCP is allowed on the game port in the host firewall, cloud security group and router port-forwarding rule. Keep the UDP rule required for gameplay as well. Test from outside the server’s own network when possible.

2. Confirm the address and port

Use the external IP, not a private LAN address such as 192.168.x.x, and use the game port rather than RCON. If the server has multiple interfaces or a NAT arrangement, start Rust with +server.ip YOUR-SERVER-IP when necessary so the service binds to the intended address.

3. Eliminate an RCON conflict

RCON and the livemap cannot share one port. Move RCON to game port +1 or another unused TCP port, then restart the server and update any RCON client settings.

4. Verify the extension loaded

Look for the Rust:IO initialization message in the startup console. If it is absent, verify that uMod/Oxide is installed, that the DLL is exactly in RustDedicated_Data/Managed, and that the server was restarted after the upload.

5. Validate the JSON configuration

If the extension loads but ignores your changes, inspect oxide/config/RustIO.json for valid JSON syntax and reload with reload RustIO. Console errors usually identify a malformed value or unsupported setting. Restore the last known-good backup if necessary, then change one setting at a time.

6. Ask the provider when the panel blocks the directory

Some hosts do not permit customers to write to RustDedicated_Data/Managed. Request installation of the managed-directory extension, or use SFTP only if the provider explicitly permits it. A missing Mod Manager entry does not mean Rust:IO cannot run; it may mean the provider has not packaged it.

7. Recheck compatibility after a Rust update

When a Rust monthly update breaks the map, update uMod/Oxide first and install a Rust:IO build compatible with the new game build. Then restart and inspect the logs again. Do not assume a previously working DLL remains compatible after the game server changes.

8. Check proxy and binding settings

If you place the map behind a reverse proxy, verify that ipOverride binds Rust:IO to the local address expected by the proxy and that the proxy forwards the configured web port. A proxy URL that points to the wrong internal service can fail even when direct local access works.

Rank #3

Rust Game Props Large Furnace (S)

• Acrylic Painting Pla Plastic

$14.99

Buy on Amazon

Direct access versus the public listing

Use direct access for a private community or a stable link you control. Treat a directory listing as an optional discovery channel, not as a replacement for correct TCP exposure and a working Rust:IO installation.

Operational checklist

• Back up the server before changing managed files.
• Stop the server before copying or replacing Oxide.Ext.RustIO.dll.
• Keep the DLL in RustDedicated_Data/Managed, never oxide/plugins.
• Run a current uMod/Oxide release and keep RCON on a different port.
• Allow inbound TCP on the game port and retain the UDP gameplay rule.
• Confirm the startup console reports the extension.
• Review oxide/config/RustIO.json and oxide/data/rustio/webmap.json after first launch.
• Open the external IP with the game port in a browser.
• Protect API keys and secrets, and decide deliberately whether to expose buildings, loot, sleepers, mortality, chat or event broadcasts.
• After every Rust update, update uMod/Oxide and Rust:IO together and inspect startup logs.

Frequently Asked Questions

Where exactly do I put Oxide.Ext.RustIO.dll?

Copy it directly into the Rust server’s RustDedicated_Data/Managed directory while the server is stopped. It is a managed extension, not a C# plugin, so oxide/plugins is the wrong location.

What URL opens the Rust:IO map?

Use http://YOUR-SERVER-IP:YOUR-SERVER-PORT with the server’s public IP and game port, such as http://203.0.113.10:28015. Do not substitute the RCON port.

Why does the map say the server is not responding?

Check inbound TCP on the game port, the external IP, NAT or port forwarding, and whether RCON is using a separate port. Then confirm the startup console reports Rust:IO initialized and that the DLL is in the Managed directory.

How do I make buildings, loot or sleepers appear?

Review the Rust:IO configuration and web-map settings, including displayBuildings and showSleepers. Buildings and loot are classified as admin-only data, so enable them only for authorized viewers and consider the privacy consequences.

Can I install Rust:IO from a hosting panel?

Yes, if the provider offers a RUST.io Livemap Mod Manager package or permits uploading the DLL through File Manager or SFTP. Some providers restrict RustDedicated_Data/Managed and require support to install it.

What should I do after a Rust monthly update?

Update uMod/Oxide and Rust:IO to versions compatible with the new Rust build, restart the server, and inspect the startup logs. A previously working extension may stop loading after a game update.

Can RCON and the livemap use the same port?

No. Keep RCON on another unused TCP port; game port plus one, such as game 28015 and RCON 28016, is the documented example.

How do I change the map language or disable its welcome message?

Edit defaultLanguage in oxide/config/RustIO.json; the documented choices include English, Czech, German, Russian, French and Spanish. Set welcomeMessage to null to disable it, then reload Rust:IO or restart.

The Bottom Line

Install Rust:IO Remastered as a uMod/Oxide extension in RustDedicated_Data/Managed, not as an oxide/plugins file. Keep RCON on a separate port, allow TCP on the game port, configure oxide/config/RustIO.json, and open the map with the server’s external IP and game port. Protect private layers and recheck compatibility after every Rust update.

Quick Recap

Bestseller No. 1

Rust Key Cards, Rust Red Key Card, Cobalt Restricted Access Cards, Rust Gift For Gamers, Blue Key Card, Green Key Card (ALL THREE)

Wallet-Size Replica – Standard 3.375x2.125 inches, 30 mil thick—fits in any wallet.; NOT a sticker*

$25.00

Bestseller No. 2

Rust Video Game Notebook

$15.00

Bestseller No. 3

Rust Game Props Large Furnace (S)

Acrylic Painting Pla Plastic

$14.99

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.