Getting kicked with “Disconnected: EAC,” stuck on “Connecting,” or bounced by “Connection attempt failed” is one of the most common Rust frustrations — and almost all of it traces back to Easy Anti-Cheat, your network, or wipe-day version mismatches. This guide covers every common Rust connection and EAC error and exactly how to fix it. It’s for the PC (Steam) version; Rust Console Edition is separate and these steps don’t apply.
The fastest workaround: direct connect with F1
When the server browser fails or a server won’t appear, skip it entirely. Press F1 to open the console and type:
client.connect 123.45.67.89:28015Use the server’s real IP and port (Rust’s default game port is 28015). You must include client.connect, not just the IP. This bypasses the server-browser layer that causes a lot of “can’t connect” problems.
“Disconnected: Connection attempt failed”
A catch-all for server-browser settings, corrupted files, VPN/proxy, DNS, firewall, or EAC comms. Work through:
- Raise your server-browser ping rate. Steam → Settings → In Game → set Server browser pings/minute much higher than default, then wait ~15 minutes.
- Direct-connect via F1 (above).
- Verify integrity of game files and clear the Steam download cache (Steam → Settings → Downloads).
- Disable any auto-VPN and proxy (Windows → Network & Internet → Proxy).
- Change your DNS to Google (8.8.8.8 / 8.8.4.4) or Cloudflare (1.1.1.1 / 1.0.0.1).
- Allow Rust through Windows Firewall (private and public).
- Repair EAC from the
EasyAntiCheatfolder in your Rust directory.
“EAC: Disconnected” / EAC connection errors
Facepunch’s explanation: your connection to the Easy Anti-Cheat back-end servers isn’t working, so the game server can’t verify EAC is running and drops you. Fixes:
- Launch from Steam, not the .exe — EAC won’t load otherwise.
- Make sure your firewall/antivirus isn’t blocking
client.easyanticheat.netover HTTP/HTTPS (ports 80 and 443). - If Rust crashes right after “EasyAntiCheat Loaded,” your local EAC files failed to update — delete the
EasyAntiCheatfolder and verify files. - Update your GPU, chipset, and network drivers.
“Disconnected: Timed Out” / EAC Authentication Timeout
Caused by a stale EAC auth cache, corrupted EAC files, conflicting background software, or packet loss. The fix sequence:
- Fully exit the game and wait about 10 minutes to let EAC refresh its auth cache.
- Verify files and repair EAC.
- Restart your PC and router; use wired Ethernet; test another network (mobile hotspot) to rule out your ISP.
- If present, delete
RustClient.exe.eacin the Rust folder, then relaunch via Steam. - Check the bottom of
output_log.txtfor apps EAC flagged as “forbidden” and close them.
“Client Integrity Violation”
This means a corrupted EAC folder — often from a banned tool like ReShade injected into the client. Delete the entire EasyAntiCheat folder, verify integrity, and restart Steam as administrator. Remove ReShade and any other injectors first.
Steam auth ticket errors
“Auth ticket canceled” / “Steam auth timeout” usually means a Steam authentication hiccup or a slow connection preventing the handshake. Restart your PC and modem, fully exit and wait ~10 minutes for the EAC cache to refresh, use a wired connection, and repair EAC. If Steam itself is having an outage, you just have to wait it out.
“You are still connected to this server”
When you disconnect, your player slot isn’t released instantly — it stays reserved until a server-side timer expires, and rejoining too fast hits that still-reserved slot. The fix is simply to wait a minute or two before reconnecting so the disconnect timer can finish.
Stuck on “Connecting” / “Receiving data” / “Spawning World”
- Disable all overlays (Steam, GeForce Experience, Game Bar).
- Run
ipconfig /flushdns, verify files, and restart your router or switch to Ethernet. - For “Spawning World (X/Y)” specifically: disable DLSS, join the server, then re-enable DLSS once you’ve spawned — DLSS can interfere with world initialization.
Version mismatch on wipe day
Rust ships its forced monthly update and map wipe on the first Thursday of each month. The server update lands first and the client update follows shortly after, so for a window your client is on an older protocol than updated servers (“client update required”). Open Steam → Downloads and let Rust update; if it doesn’t show, restart Steam or verify files to force it, and opt out of any beta/Staging branch if you’re not testing.
Other EAC error strings
- “Network DNS Error” (download.eac-cdn.com): run
ipconfig /flushdnsand restart the game. - “Error validating EasyAntiCheat code signing certificate”: install Windows updates and update your antivirus.
- “Untrusted System File”: run
sfc /scannowas admin, install Windows updates, run a full AV scan. - “Start Service Failed”: close all EAC and Rust processes in Task Manager, reboot, update Windows.
- “Blacklisted device — Bloody Mouse”: Bloody/A4Tech macro hardware is blocked — switch to a different mouse.
When it’s the server, not you
If you can join other servers fine but one keeps failing, that server is behind on the wipe-day update, misconfigured, or overloaded. If it’s your own, our connect-to-your-Rust-server docs and troubleshooting docs cover the server side. A weak host that chokes on a full wipe-day pop causes timeouts and failed joins for everyone — running on managed Rust server hosting with guaranteed resources and DDoS protection keeps connections clean when it matters most. If Rust is crashing rather than disconnecting, see our Rust crashing & won’t launch guide.
Frequently asked questions
How do I fix “Disconnected: EAC” in Rust?
It means your connection to Easy Anti-Cheat’s back-end failed. Launch Rust from Steam (not the .exe), make sure your firewall isn’t blocking client.easyanticheat.net on ports 80/443, delete the EasyAntiCheat folder and verify files to force a clean update, and update your network and GPU drivers.
How do I direct-connect to a Rust server?
Press F1 to open the console and type client.connect IP:PORT (for example client.connect 123.45.67.89:28015 — 28015 is the default port). This bypasses the server browser and fixes most “connection attempt failed” and server-not-appearing issues.
Why can’t I connect to Rust servers on wipe day?
Rust force-updates on the first Thursday of each month, and the server update arrives before the client one, so your client can briefly be on an older protocol (“client update required”). Let Rust update in Steam → Downloads, restart Steam or verify files to force it, and opt out of any beta branch.
Why does Rust say “you are still connected to this server”?
Your player slot stays reserved for a short time after you disconnect, and rejoining too quickly hits that reserved slot. Wait a minute or two before reconnecting and it’ll let you back in.
Ready to play?
Run your own Rust server with XGamingServer
Spin up an always-on Rust server your friends can join in minutes — no port-forwarding, no tech headaches.
