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

To install Rust:IO Remastered, run a current Rust dedicated server with uMod/Oxide, stop the server, place Oxide.Ext.RustIO.dll in RustDedicated_Data/Managed, and start the server again. The extension loads through uMod/Oxide, creates its configuration files, and serves the map from your external server IP on the game port. The web endpoint needs an inbound TCP rule on that port; RCON must use a different port.

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

Hosted servers can usually install the extension from a Mod Manager or by uploading the same DLL through File Manager/SFTP. This guide covers both routes, configuration, map access, privacy controls, and the fixes for the common server-not-responding and missing-extension errors.

#	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.

What Rust:IO Remastered does

Rust:IO Remastered is a server extension for the uMod (formerly Oxide) Rust modding framework. It adds a browser-based live map and a REST API to a Rust server. It is an extension, not a normal C# plugin: you do not put the DLL in oxide/plugins. The required location is RustDedicated_Data/Managed.

The Remastered project describes itself as an open reimplementation of the Rust:IO server core, revived for current Rust builds after the original playrust.io service went offline. It is not affiliated with Facepunch Studios. Older tutorials that only reference the original service can therefore be misleading; check that the Rust:IO and uMod/Oxide builds you install support your current Rust server.

#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

Once loaded, the map can expose monuments, player and ally locations, events, grid coordinates, and a mortality heat map. Building and loot data are admin-only in the Remastered manual. Steam sign-in is used to locate your own player and allies, so enabling a layer always has a privacy and administration implication.

Prerequisites and network requirements

Run a compatible Rust server and uMod/Oxide

Start with a current Rust dedicated server and a recent uMod/Oxide installation. The uMod Rust guide documents installation with umod install rust -P. Plugin documentation requires Oxide 2.0 or newer for plugins to load. Rust:IO is loaded by that framework, so a server without uMod/Oxide cannot initialize the extension.

Back up the server before replacing managed files. Rust updates monthly, and Facepunch’s server guidance notes that Oxide must be updated after a Rust update. Treat every game update as a compatibility check for both uMod/Oxide and Rust:IO.

Open the correct port

Rust gameplay normally uses UDP, but the livemap web endpoint needs an inbound TCP connection on the game server port. Allow that TCP traffic through the host firewall, cloud security group, and any router or NAT rule in front of the server. If the port is open only for UDP, players may connect to Rust while the browser map remains unreachable.

Keep RCON on another unused port. A typical arrangement is game port 28015 and RCON port 28016. The map URL uses the game port, never the RCON port; the two services cannot share one port.

Choose an installation route

The right route depends on whether you control the Rust installation directory and network firewall. The extension must ultimately reach the Managed directory and the web endpoint must be reachable from outside the machine.

If you cannot access RustDedicated_Data/Managed, cannot open inbound TCP, or cannot restart the server after an upload, a managed Rust host with uMod/Rust:IO support is the practical option. Confirm those capabilities with the provider before ordering or migrating a server.

Install Rust:IO on a self-managed server

1. Stop the server. Do not replace a managed DLL while RustDedicated is running. Use your service manager or console to shut it down cleanly.
2. Download Rust:IO Remastered. Use the project’s current manual and download route, and select a build intended for your Rust version. Keep the downloaded archive until you have verified a successful startup so you can identify exactly what was installed.
3. Copy the extension. Extract and place Oxide.Ext.RustIO.dll directly in RustDedicated_Data/Managed. Do not put it under oxide/plugins, inside an extra nested folder, or in the server root beside the executable.
4. Start Rust. The loader downloads the remaining Rust:IO components automatically. Watch the startup output rather than assuming that a clean process launch means the extension loaded.
5. Verify initialization. The server console should report the Rust:IO extension during startup. If no extension message appears, stop and check the DLL path, uMod/Oxide version, file permissions, and the complete startup log before continuing.
6. Wait for first-run files. A successful first start creates oxide/config/RustIO.json. The web-map data file is oxide/data/rustio/webmap.json; it contains the web endpoint settings and a generated secret.

What a successful install looks like

The decisive checks are visible in the server console and filesystem: an extension-initialization message, a newly created RustIO configuration, and a webmap data file. If those appear, test the browser endpoint before inviting players. If they do not, changing map settings will not fix the underlying load failure.

Install through a hosted control panel

Use the panel’s Mod Manager

Some panels list the package as RUST.io Livemap or Rust:IO Livemap. Stop the server, install that entry, edit the generated configuration, save it, and start the server. One documented workflow is: stop the server, choose RUST.io Livemap in Mod Manager, edit oxideconfigRustIO.json, save, and start.

After startup, inspect the panel console for the extension initialization message and test the map from an external connection. A one-click button is only a shortcut; the same TCP, port, and compatibility requirements still apply.

Rank #2

Rust Video Game Notebook

$15.00

Buy on Amazon

Upload with File Manager or SFTP

If no Mod Manager entry exists, stop the server and upload Oxide.Ext.RustIO.dll to RustDedicated_Data/Managed through the panel’s File Manager or SFTP. Some hosts block that directory. In that case, support staff must install the Managed-directory extension, or you must move to a plan that permits it. Do not upload a plugin copy to oxide/plugins as a substitute.

Restart after the upload and verify the console message. If the host automatically updates Rust but not uMod/Oxide or Rust:IO, ask how compatibility updates are handled before enabling automatic game updates.

Configure Rust:IO

Main settings in RustIO.json

Edit oxide/config/RustIO.json with a JSON-aware editor. Preserve commas, braces, and value types. A malformed file can cause the configuration to be ignored or produce a JSON error in the console.

Web endpoint settings in webmap.json

The first successful launch creates oxide/data/rustio/webmap.json. It contains the web-map-specific values below, including a generated secret.

Change only values you understand, keep valid JSON, and retain a backup of the original file. After editing RustIO.json, run reload RustIO in the server console. Restart instead when your host does not support plugin reloads or when you changed a setting that the panel documents as startup-only.

Open the live map

Direct browser address

Use the server’s external IP and the Rust game port:

http://YOUR-SERVER-IP:YOUR-SERVER-PORT

For a server whose public address is 203.0.113.10 and game port is 28015, the address is http://203.0.113.10:28015. Substitute the real public address; do not use a private LAN address when testing from the internet, and do not substitute the RCON port.

Test from a device outside the server’s network when possible. A local test can succeed through hairpin NAT while remote players remain blocked, or fail locally even though the public endpoint works.

Directory listing and panel buttons

The manual says a server may appear on playrust.me after a short delay. That directory is useful for discoverability, but it is not required for direct access and introduces dependence on an external listing. A hosting panel’s RUST.io Livemap button normally opens the same service in a new window; confirm the displayed address and port if the window reports that the server is not responding.

Understand map layers and player privacy

Players, allies, and Steam sign-in

Players can use the interactive map to view the layers your server exposes. Steam sign-in is used to locate the signed-in player and allies. Explain that behavior in your server rules, especially if the map is public, and avoid enabling identity-related layers without considering whether players expect that information to be visible.

Rank #3

Rust Game Props Large Furnace (S)

• Acrylic Painting Pla Plastic

$14.99

Buy on Amazon

Buildings, loot, sleepers, and mortality

Buildings and Loot are admin-only data in the Remastered manual. Keep those layers restricted to administrators rather than assuming that a browser URL is private. The showSleepers option controls sleeper visibility, while displayMortality adds a mortality heat map that can reveal where combat and deaths concentrate. Review these settings after every configuration change and after installing another map or administration tool.

Chat and event broadcasts

broadcastChat, broadcastSpawns, and broadcastDeaths determine which live events are relayed to the map. Broadcasting can help moderators, but it can also expose player activity. Set each option deliberately instead of leaving all event feeds enabled by default.

Troubleshoot a map that does not respond

1. Check TCP reachability

Confirm an inbound TCP rule exists for the game port on the operating-system firewall, cloud firewall, and router. UDP-only rules allow normal Rust play but do not serve the browser map. Test the public address from outside the server network.

2. Verify the address and port

Use the external IP and game port in the browser. Do not use the RCON port, a private address, or a panel’s internal hostname unless the host specifically documents it as the public endpoint.

3. Bind the server to its public address when needed

If the machine has multiple network interfaces or the service is listening on the wrong interface, start Rust with +server.ip YOUR-SERVER-IP. Use the address assigned to the server and then restart before testing again.

4. Resolve an RCON conflict

Move RCON to game port +1, such as 28016 when the game uses 28015, or choose another unused port. Both services cannot listen on the same port, and a conflict can prevent the web endpoint from accepting connections.

5. Fix a missing extension

Stop the server and confirm that uMod/Oxide is installed, the filename is exactly Oxide.Ext.RustIO.dll, and the file is directly inside RustDedicated_Data/Managed. Start again and inspect the complete console log. A restart is required after an upload.

6. Repair ignored configuration

Open oxide/config/RustIO.json in a JSON-aware editor and correct syntax errors such as a missing comma or quote. Save, run reload RustIO, and read the console for parsing errors. If the host does not support reload, restart the server after saving.

7. Handle a panel that lacks the option

Ask the provider whether it supports Managed-directory extensions and inbound TCP on the game port. If SFTP is permitted, upload the DLL yourself; otherwise request a support installation or use a plan that grants the required access.

8. Recover after a Rust update

When a Rust update breaks the map, update uMod/Oxide and Rust:IO to builds compatible with the new Rust version, restart, and recheck the extension message and web endpoint. Restore your backup if a replacement causes a new failure, then verify compatibility before trying another build.

Post-install operating checklist

• Record the external IP, game port, RCON port, and the map URL in your server administration notes.
• Keep a backup of RustDedicated_Data/Managed, oxide/config/RustIO.json, and oxide/data/rustio/webmap.json before updates.
• After every Rust update, update uMod/Oxide and Rust:IO, restart, and confirm the extension initializes.
• Review TCP firewall rules whenever the host changes networking, migrates machines, or changes the public IP.
• Check that apiKey and the generated web-map secret are not exposed in public repositories, screenshots, logs, or support tickets.
• Re-test the map from an external network and verify that only the intended layers, players, buildings, sleepers, and event broadcasts are visible.
• Tell players how to open the map and how Steam sign-in affects self and ally locations.

Direct answer: the shortest reliable path

For a server you control, stop Rust, install uMod/Oxide, copy Oxide.Ext.RustIO.dll into RustDedicated_Data/Managed, start the server, and confirm the extension in the console. Open inbound TCP on the game port, keep RCON elsewhere, configure oxide/config/RustIO.json, and open http://YOUR-SERVER-IP:YOUR-SERVER-PORT. For a hosted server, use the Mod Manager or ask support to place the DLL in the Managed directory, then apply the same port, configuration, and compatibility checks.

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.