Fix common Rust server errors

Most Rust connection problems come from three things: the server isn’t running yet, the game and server are on different versions after an update, or Steam or Easy Anti-Cheat couldn’t check the player. The fixes are below, most common first. If the server itself crashes, the Console shows a crash helper card with a hint and a fix button when it knows the problem.

Joining problems

Connection attempt failed

The game couldn’t reach the server.

Why it happens: the server isn’t running or hasn’t finished starting, the port is wrong, or the address has a typo.

How to fix it:

1. Check the status on Overview. If it’s stopped, press Start. A stopped server doesn’t wake when someone joins.
2. If it’s starting, wait. Watch the Console for Server startup complete. The first start builds the map and can take up to about 10 minutes on a big map.
3. Copy the address with the copy button on the address card and paste it after client.connect. Include the port after the colon. Rust’s usual 28015 won’t work.
4. If the server was asleep, try once more after a few seconds. The first try wakes it.

Wrong Connection Protocol

The full message ends in Client update required! or Server update required!.

Why it happens: the game and the server are on different Rust versions. It happens most on update day, the first Thursday of each month, while players and servers catch up.

How to fix it:

• Client update required: your game is older than the server. Close Rust, restart Steam, and let Steam finish updating Rust.
• Server update required: the server is older than your game. Restart it from Overview. Servers set to update on their own move to the newest build when they start. If you pinned a version in Settings, switch back to the latest.

On update day, give it a little time. Facepunch’s update arrives at about 19:00 UK time, and Steam can take a few minutes to offer it to everyone.

Steam Auth Failed

The player is kicked while joining. Some players see Steam Auth Timeout instead.

Why it happens: Steam couldn’t confirm the player’s session in time. Usually the player’s Steam client is the problem, and sometimes Steam’s own servers are.

How to fix it:

1. Close Rust and quit Steam fully, then start Steam again.
2. In Steam, make sure Rust isn’t on a beta branch: right-click Rust, open Properties > Betas and pick no beta.
3. Verify the game files: Properties > Installed Files > Verify integrity of game files.
4. If every player gets it at the same moment, Steam is having trouble. Wait a few minutes and try again.

Disconnected: EAC

The message starts with EAC: and a reason, for example Authentication timed out or Client not responding.

Why it happens: Easy Anti-Cheat, the anti-cheat Rust uses, couldn’t check the player’s game. Common causes are a damaged install, a firewall or antivirus blocking it, or a shaky connection.

How to fix it:

1. Always start Rust from Steam, which starts Easy Anti-Cheat with it.
2. Verify the game files in Steam, then restart the PC.
3. Close overlays and tools that hook into games, then try again.
4. Allow Rust and Easy Anti-Cheat through the firewall or antivirus.
5. If it keeps happening, follow Facepunch’s support article on EAC authentication timeouts.

If the message says the player is banned, that ban comes from Facepunch for the whole game. Server owners can’t remove it.

Server is full

Why it happens: the server has reached its max players. Rust may put new players in a queue instead of turning them away.

How to fix it:

• Raise max players in Settings and restart. Keep an eye on RAM if you add many.
• Let friends skip the queue: type global.skipqueueid 76561198000000000 "Name" in the Console.

Server problems

My server isn’t in the server browser

Why it happens: new servers take a few minutes to show up, the server is on another tab, or it’s asleep.

How to fix it:

1. Wait a few minutes after the first start, then refresh the browser.
2. Look on the right tab. Servers with Oxide or Carbon are on Modded, not Community.
3. Clear any filters and search for a word from your server name.
4. If sleep is on, the server drops off the list while it naps. Keep public servers always on in Settings > Sleep.
5. You can always join with client.connect and your address, listed or not.

A server that breaks Facepunch’s server guidelines, like calling itself official, can be removed from the browser.

Plugins stopped working after an update

The Console shows errors that name a plugin, or plugin commands do nothing.

Why it happens: Rust updates change the game’s code. Oxide and Carbon need a matching release, and so do some plugins.

How to fix it:

1. Restart the server once. Our update rollout installs the matching Oxide or Carbon release with each Rust update.
2. Open Mods and update any plugin that has a new version.
3. If one plugin still fails, unload it with oxide.unload PluginName or c.unload PluginName until its author fixes it.

More in Rust plugins with Oxide and Carbon.

My base is gone

Why it happens: almost always a forced wipe. On the first Thursday of each month, Facepunch’s update makes every server start a new map. Blueprints usually stay. A changed map size or seed also builds a new map.

How to fix it: a forced wipe can’t be undone on the new version. Plan for it with Rust wipe day. If you changed the size or seed by mistake, set them back in Settings and restore the backup from before the change in Backups.

Rust+ companion server connectivity test failed

The full log line is Rust+ companion server connectivity test failed! Disabling Rust+ features.

Why it happens: the Rust+ app couldn’t reach your server’s app port, or the server couldn’t reach Facepunch’s Rust+ service.

How to fix it:

1. Remove any app.port or app.publicip lines you added to server.cfg. They can point the app at the wrong place, and we set the app port for you.
2. Restart the server. The test runs at each start.
3. Don’t delete companion.id. It’s your server’s Rust+ identity.
4. If it still fails, contact us at support@wilderack.com.

The server keeps crashing

Why it happens: most often the server ran out of memory, near the end of a wipe or after adding plugins. A broken plugin can also crash it.

How to fix it:

1. Read the crash helper card in the Console. It says when memory was the problem.
2. Check the RAM graph on Overview. If it touches the top of your plan, see the performance guide.
3. Remove the plugin you added last and restart.
4. If you can’t find the cause, send the crash to us from the crash card, or email support@wilderack.com.