Fix Rust "Disconnected: Steam Auth Timeout"

Steam's authentication service did not answer in time, so the server could not confirm who you are. This is almost never the server, and waiting really is sometimes the fix.

6 min read · Updated Oct 21, 2026 · By GuavaHost Team

The message on the player's screen reads:

Disconnected: Steam Auth Timeout

You may also see Disconnected: Steam Auth Failed or Disconnected: Timed out. The first two are about identity, the third is about the connection, so read which one you got.

What is happening behind it

When you connect to a Rust server, your Steam client generates a ticket that proves which Steam account you are. The server sends that ticket to Steam's own servers and asks whether it is valid. Only when Steam says yes does the server let you in.

Three parties have to cooperate: your Steam client, the Rust server, and Steam's authentication service. A timeout means the third one did not answer quickly enough, so the server gave up on the join. Nothing was refused, nothing was wrong with your account, the question simply did not get answered.

That is why there are no server settings to change for this. It is also why it tends to hit several people at once rather than one person for days.

Fixes in order

Start at the top. Most people are back in within a couple of minutes.

1. Try again. Genuinely. These timeouts are frequently transient, and a second attempt thirty seconds later works more often than anything else on this list.
2. Check Steam is online, not in Offline Mode. Offline Mode cannot produce a valid ticket. In Steam, open the Steam menu and make sure it does not offer to go online, which means you are currently offline.
3. Restart Steam completely. Quit it from the tray rather than closing the window, then start it again. This forces a fresh connection to Steam's services and a fresh ticket.
4. Restart Rust. Together with step three, this clears a stale ticket the game is still holding onto.
5. Check for a Steam outage. If your whole group is hitting it at the same moment and nothing changed, this is usually why. Steam's status is public and worth a glance before you change anything else.
6. Restart the computer. Clears a stuck Steam process that is holding an old session.
7. Turn off a VPN. Some VPN exit nodes interfere with Steam's own traffic, which breaks ticket validation even though your game connection looks fine.
8. Verify the game files. Rarely the cause, but cheap, and it rules out a damaged install.

The reconnect loop

There is one thing players do that makes this much worse: hammering the connect button.

Steam rate limits authentication requests per account. If you try to join six times in twenty seconds, the later attempts are more likely to be ignored than the first, so the fix becomes the cause. If you have just failed twice, wait a full minute before the third attempt.

The same applies to a full server you are trying to get into during a wipe rush. Queue, wait, and do not reconnect repeatedly.

Family Sharing and multiple accounts

Rust does not work with Steam Family Sharing, and the symptoms are easy to mistake for this error. A shared copy cannot produce a valid authentication ticket for Rust, so the join fails. The answer is that the player needs their own copy, and there is nothing a server owner can do about it.

Two accounts on one computer causes something similar. If Steam is signed into account A and the game was bought on account B, the ticket does not match. Signing in properly as the owning account clears it.

The server's own Steam connection

There is one case where the server is involved, and it is worth checking if the whole server is affected rather than individual players.

Your Rust server also talks to Steam, both for authentication and to list itself. If that connection is unhealthy, every join fails and the server usually drops off the community browser at the same time. The two symptoms together are the signature.

Open the Console tab on your server page and look at the lines from startup and from a failed join. If the log mentions Steam or authentication failing on the server's side, a restart is the first thing to try: press Restart at the top of the server page and watch it come back up. Start, stop and restart your server safely covers doing that cleanly.

If restarting does not help and your server is also missing from the browser, work through Rust server not showing in the Community or Modded list, because the underlying cause is often the same.

When it is only one player

If everyone else is playing happily, the problem is on that player's machine and the list above is the whole answer. It is worth saying so plainly, because server owners often spend an evening tuning convars for something that was a Steam restart.

Ask them to try joining a different Rust server. If they get the same error there, the server is definitively not the cause and you can stop looking at it.

Things that will not fix it

• Changing convars. No setting in server.cfg affects Steam authentication. Editing server.cfg and Rust convars covers what those settings do control.
• Adding RAM or changing location. This is not a performance problem.
• Reinstalling the server. You will lose time and possibly data for nothing. If you are tempted, read the console first.
• Wiping. Occasionally suggested, never relevant. A wipe clears the map and player progress, which has nothing to do with authentication.
• Plugins. Oxide and Carbon plugins run after authentication, so they cannot cause this. Oxide and Carbon plugins on a Rust server covers what they do affect.

If it is actually a plain timeout

If the message is Disconnected: Timed out with no mention of Steam, that is a connection problem rather than an authentication one, and it needs different checks: confirm the server is Online, confirm the address and port, and look at the player's own network. When a firewall or network blocks your game port covers the network side.

And if players cannot find the server at all rather than failing to join it, that is the community list, not authentication.

Common questions

Is Steam Auth Timeout my server's fault?

Almost never. It means Steam's authentication service did not answer the server's question about a player's identity in time, which is outside both your control and the player's. The exception is when every player is affected and your server has also dropped off the community browser, which points at the server's own Steam connection.

Why does trying again straight away make it worse?

Because Steam rate limits authentication requests per account, so rapid repeated attempts are more likely to be ignored than the first one. After two failures, wait a full minute before trying again rather than clicking connect repeatedly.

Does Rust work with Steam Family Sharing?

No. Rust does not support Family Sharing, and a shared copy cannot produce a valid authentication ticket, which fails in a way that looks exactly like this error. The player needs their own copy of the game.

Everyone on my server got this at once. What should I check?

Look at whether your server has also vanished from the Community browser, because the two together suggest the server's own connection to Steam is the problem and a restart is the first thing to try. If the server is still listed normally, a Steam outage is the likelier explanation and waiting is the answer.

Still stuck? Jump into our Discord at discord.gg/GuavaHost and the team will help you out.

• rust
• steam
• connection
• timeout
• troubleshooting

Host a Rust server From $15.99/mo, with instant setup and DDoS protection.

Still need help? Our team is online 24/7 to answer questions.

Contact support