Rust server problems

Common Rust server problems and how to fix them. Settings named here are on your Startup page, see Rust settings.

My server is not in the server list

Why it happens: New Rust servers can take several minutes to appear in the in-game list, and the list only shows servers that are Online with a name and description set. Filters in the game can also hide it.

How to fix it:

1. Check the status says Online and wait about 10 minutes after starting.
2. In the game server browser, search for the exact Server Name (HOSTNAME on Startup).
3. Clear all filters, and check the “Modded” and “Community” tabs, since a modded server is not listed under Official.
4. You can always connect directly: press F1 in game to open the console and type client.connect address:port, using the address and port from your Network page.
5. If direct connect works but the list never shows the server, open a ticket and we will check the ports.

Cannot connect to the server (Connection refused, timed out, or stuck on “Connecting”)

Why it happens: The server is still starting, the wrong address or port is used, or the game client and server are on different versions.

How to fix it:

1. Wait until the panel status says Online. Rust can take a few minutes to load a large map.
2. Use the address and port shown on the Network page, and make sure you use the Primary port and not another one.
3. Restart Rust on your side, and update it in Steam.
4. If it only fails for some players, see Can’t connect to any game.

Version mismatch, or “Disconnected: Wrong Connection Protocol”

Why it happens: Rust updates often. If the server files are older or newer than the players’ game, they cannot join.

How to fix it:

1. Restart the server from the power bar. Rust servers usually check for a new version when they start.
2. Ask the players to restart Steam so Rust updates.
3. If the server is still on an older version after a restart, open a ticket.

Server crashes or fails to load after the monthly Rust update

Why it happens: Facepunch normally ships a big Rust update on the first Thursday of each month, and that update forces a map wipe on every server. After an update, Oxide or Carbon can also be out of date and fail to load until their developers publish a matching version.

How to fix it:

1. Restart the server so it downloads the newest Rust files.
2. If the console shows plugin or framework errors right after the update, the framework is probably behind. Wait for the Oxide (uMod) or Carbon update, then restart.
3. To get the server running immediately, set Modding Framework (FRAMEWORK) to vanilla on Startup, save, and start. Switch back once the framework has updated.
4. Read the last lines of the Console and see Server keeps restarting.

When does my server wipe, and how do I wipe it?

Why it happens: Rust has two kinds of wipe. A map wipe resets the world and buildings. A blueprint wipe also resets what players have learned. Facepunch’s monthly update forces a map wipe on force-wipe day, but a blueprint wipe is a choice, not forced (most servers do it by habit). Many servers also wipe on their own schedule.

How to fix it:

1. Back up first: see Backups.
2. Stop the server.
3. Open Files and find your server’s save folder (often under server, in a subfolder named after the server identity). Map wipe: delete the .map and .sav files (the map and the world save).
4. Blueprint wipe: also delete the files matching player.blueprints.*.db in the same folder. File names include a number that changes between Rust versions, so match the pattern.
5. To get a new map, change World Seed (WORLD_SEED) or World Size (WORLD_SIZE) on Startup, then start the server.
6. If you cannot find the files, open a ticket.

How do I change the world size or seed?

Why it happens: The map is generated from size and seed the first time, then saved. Changing the settings does nothing to an already saved map.

How to fix it:

1. Stop the server.
2. On Startup, set World Size (WORLD_SIZE) and World Seed (WORLD_SEED).
3. In Files, delete the saved map (.map and .sav files) so a new one is generated. This is a wipe, so back up first.
4. Start the server. Large sizes use more memory and take longer to generate.

Custom map does not load, or the server crashes on start with a map URL

Why it happens: Custom Map URL (MAP_URL) must be a direct download link to the map file. The Startup page notes that invalid URLs will cause the server to crash. A page that shows a download button, or a link that needs a login, does not work.

How to fix it:

1. Stop the server.
2. On Startup, clear Custom Map URL, or replace it with a direct link that downloads the file when opened.
3. Check Level (LEVEL) matches what you want: Procedural Map for a generated world.
4. Start the server and watch the Console.

The map keeps regenerating or my Custom Map URL was ignored

Why it happens: When a custom map URL is set, the server downloads it at start and it replaces the map. Leaving a URL in place means the map is reset from that link every start.

How to fix it:

1. Clear Custom Map URL after the first successful start if you want normal saves to carry over.
2. Make sure you did not delete the save files by accident: look in Files.

Kicked: “Steam authentication failed” or “Steam Auth Failed”

Why it happens: Steam did not confirm the player’s account. This is usually a short Steam outage, a player who is logged out of Steam, or a shared or family-shared copy.

How to fix it:

1. Ask the player to fully close Rust and Steam, sign in to Steam again, and reconnect.
2. Check the Steam status if many players see it at once.
3. Restart your server if it happens to everyone and Steam is fine.
4. If it keeps happening, open a ticket with the exact message.

Kicked by Easy Anti-Cheat (EAC)

Why it happens: Messages like “Kicked: EAC: Authentication Failed” or “EAC: Untrusted Client” come from the player’s side: Easy Anti-Cheat did not start, is out of date, or found a file it does not trust.

How to fix it:

1. In Steam, right-click Rust, choose Properties, then Installed Files, then verify integrity.
2. Restart the PC so EAC can reinstall its service.
3. Close overlay and modding tools, then start Rust again.
4. Only if EAC failed for every player, restart the server and open a ticket.

How do I use RCON?

Why it happens: Rust uses WebRCON. You need the password and the correct address and port.

How to fix it:

1. Set RCON Password (RCON_PASS) on Startup to a strong password. Do not leave it blank.
2. Restart the server.
3. In your RCON tool, use the address and the RCON port. Check the Network page for your allocations. If the RCON port is not shown or the tool cannot connect, open a ticket.

RCON says “wrong password” or cannot connect

Why it happens: The password does not match what the server started with, or the tool is using the wrong port, or the change was saved but not restarted.

How to fix it:

1. Check RCON Password on Startup for spaces at the ends.
2. Restart the server after changing it.
3. Avoid special characters if your tool has trouble with them.

Oxide or Carbon is not loading, or I want to change framework

Why it happens: The Modding Framework (FRAMEWORK) variable decides what gets installed: vanilla, oxide or carbon. It changes on the next start.

How to fix it:

1. Stop the server.
2. On Startup, set Modding Framework to oxide or carbon, save, and start.
3. Wait for the Console to finish. Look for the Oxide or Carbon loading lines.
4. If it fails, try again after a restart, then open a ticket with the Console text.

Where do I put plugins? (Oxide vs Carbon)

Why it happens: Each framework has its own folder, so a plugin in the wrong one is silently ignored.

How to fix it:

1. Oxide plugins go in the oxide/plugins folder. Data and config are in oxide/data and oxide/config.
2. Carbon plugins go in the carbon/plugins folder, with carbon/configs and carbon/data beside it.
3. Upload the .cs file with Files, and the framework loads it automatically. See Files.
4. Use the plugin’s own reload command in the Console or RCON if it does not load.

Plugin errors in the Console (compile error, missing dependency)

Why it happens: Plugins are written for a specific framework and Rust version. After a Rust update, many break until updated. Some need another plugin as a dependency.

How to fix it:

1. Read the Console line, which names the plugin and the line that failed.
2. Download the latest version from the plugin author.
3. Install any dependency the plugin page lists.
4. Remove the plugin file to isolate it if the server will not start.
5. We cannot fix third party plugin code. Ask the plugin author for support.

Server lags or uses too much memory

Why it happens: Rust uses more memory the larger the map and the more players and entities there are. Large maps and many plugins raise it further. It grows the longer the server runs.

How to fix it:

1. Lower World Size (WORLD_SIZE) for a new map, and lower Max Players (MAX_PLAYERS).
2. Remove heavy plugins.
3. Restart the server on a schedule: see Schedules.
4. If the Console shows “Out of memory: true”, see Out of memory and consider upgrading.

My progress rolled back or saves are lost

Why it happens: Rust saves on an interval. If the server stops uncleanly, anything since the last save is lost.

How to fix it:

1. Check Save Interval (SAVEINTERVAL) on Startup. The default is 60 seconds.
2. Always use Stop, not Kill, so the server can save first.
3. Take regular backups: see Backups.

Still stuck?

Open a ticket or ask on Discord. See Contact support.