Rust Steam Auth Timeout? How to Fix It (Players and Servers)

The Rust "Steam Auth Timeout" error means the server could not confirm your Steam ticket with Valve in time, so it dropped you. It is usually caused by Steam itself being slow or down, launching Rust outside Steam, a VPN, or a server that is mid update or overloaded. Restarting Steam fully and rejoining with client.connect fixes most cases.

What does "Disconnected: Steam Auth Timeout" mean in Rust?

When you join, the Rust server asks Steam to verify that your account owns the game and is allowed to play. If Steam does not answer before the server gives up, you see:

Disconnected: Steam Auth Timeout

It is a handshake problem between three parties: your client, the server and Steam's authentication servers. That is why it often hits many players at once on force wipe day, when millions of people connect within the same hour.

Quick fix checklist

Fully close Steam (right click the tray icon, Exit), start it again and launch Rust from your Steam library.
Wait a few minutes if it is force wipe day or Steam is having issues, then try again.
Turn off any VPN or proxy.
Join with the console: press F1 and type client.connect address:port instead of using the browser.
Verify game files: in Steam, right click Rust, Properties, Installed Files, Verify integrity of game files.
If you own the server, restart it and check that it is on the latest Rust version.

Rust connection errors compared

Rust has several look alike disconnect messages. Each one points at a different cause.

Error message	What it means	First thing to try
`Steam Auth Timeout`	Steam did not confirm your ticket in time	Restart Steam, wait, rejoin
`Steam Auth Failed`	Steam answered and rejected the ticket	Restart Steam, make sure you are online and not in offline mode
`EAC: Authentication timed out`	Easy Anti Cheat did not finish its check in time	Repair EAC, restart PC, disable VPN
`EAC: Client Integrity Violation`	EAC found modified or corrupted files	Verify game files, remove overlays or tools that inject into the game
`Wrong Connection Protocol`	Your game and the server are on different versions	Update the game or wait for the server to update

If you are seeing the protocol error, read our force wipe schedule: it nearly always happens in the hours after a monthly update while servers catch up.

How do players fix Steam Auth Timeout?

Start with the cheapest fixes and work down.

Check Steam's status. If Steam's connection or authentication services are degraded, nothing you do locally helps. Wait it out. This is the single most common cause on wipe day.

Restart Steam and launch Rust from Steam. Launching through a shortcut that bypasses Steam, or having Steam stuck in offline mode, means there is no valid ticket to send. A full exit and relaunch issues a fresh one.

Remove VPNs and network filters. VPNs, some antivirus web shields and gaming network optimisers can delay or reroute the auth traffic enough to time out. Disable them and try again.

Restart your router. A long running router with a full NAT table can drop the UDP traffic Rust uses. A power cycle clears it.

Verify files and repair EAC. Corrupt files can cause the client to stall during connection. Verify integrity in Steam. If EAC errors appear too, run the EAC setup tool from the EasyAntiCheat folder in the Rust install directory and choose Repair.

Try another server. If you can join other servers fine, the problem is that server, not you. Tell the owner.

How do server owners fix Steam Auth Timeout?

If many players get the error on your server while they can join others, look at the server.

Restart the server and update it. A server that has been up for days, or that missed an update, is the most common server side cause. On a self hosted box, run SteamCMD with +app_update 258550 validate and restart. On a hosted server, a restart normally pulls the update.

Check the server is not overloaded. When server FPS drops very low, the join queue processes slowly and auth can time out before the server handles it. Run fps and serverinfo in the console. If FPS is in single digits, read our Rust lag fix.

Check plugins on join. Oxide or Carbon plugins that run heavy work when a player connects, such as large database lookups or anti VPN checks against a slow API, can delay the connection. Unload recently added plugins one at a time to test.

Raise the connection timeout. Several hosts recommend raising server.connectiontimeout (in seconds) on servers with slow joins, for example:

server.connectiontimeout 300

Add it to server.cfg so it survives restarts. Treat it as a mitigation: if the real cause is Steam being down or the server lagging, a longer wait only delays the same failure. Our server.cfg guide shows where that file lives.

Make sure the ports are right. Rust uses the game port over UDP (28015 by default) and a Steam query port. If the query port is blocked, the server can drop out of the browser and players connecting through favourites can see odd timeouts. Our server not showing guide covers the ports in detail.

Why does Steam Auth Timeout happen on wipe day?

Force wipe is the busiest hour of the month in Rust. Facepunch releases the update, every client downloads it, thousands of servers restart and huge numbers of players try to connect at once. Steam's authentication services get hammered, and servers are busy generating maps at the same time. If you see the error in the first hour after a wipe, the honest fix is to wait 10 to 20 minutes and try again.

Avoiding it on your own server

Most server side causes come down to an out of date or overloaded server. A few habits help:

Restart daily, which clears memory and pulls updates.
Keep plugin count sensible, and remove plugins you no longer use. The best Rust plugins list points at lightweight choices.
Size RAM for your map and population so FPS stays healthy late in the wipe.

On a GamezServers Rust server, Rust and Oxide or Carbon update on every restart, the ports are open from the start, and the dashboard console lets you check fps and run convars without logging in to a box. If your server runs out of memory late in a wipe, you can move to a bigger plan from the panel.

FAQ

Is Steam Auth Timeout a ban?

No. A ban shows its own kick message. Steam Auth Timeout is a connection handshake failure and usually clears on its own or after restarting Steam.

Why do I get Steam Auth Timeout on only one server?

That server is likely out of date, overloaded or running a slow plugin on join. Other servers working fine means your Steam account and game are OK.

Does verifying game files fix Steam Auth Timeout?

Sometimes. It fixes corrupted files that stall the connection, but it will not help if Steam's auth service is down or the server is the cause.

How long should I wait during a Steam outage?

Usually 10 to 30 minutes. Steam incidents on update days tend to clear quickly once the first rush of downloads and logins passes.

Can a VPN cause Steam Auth Timeout in Rust?

Yes. A VPN can delay or reroute the authentication traffic enough for it to time out. Disable it and connect directly.