The fastest way to fix Steam Auth Failed on a Rust dedicated server is to identify whether the failure is on the server’s Steam logon, the player’s Steam/Easy Anti-Cheat (EAC) state, or the network path used to find and reach the server. Update and validate the server with SteamCMD first, confirm that it reaches Steam’s connected/logged-on state, then repair the client, EAC, and port or discovery settings indicated by the log.
Playing with friends? Godlike.Host runs hosted Rust servers from 10 data-center locations, with free DDoS protection.
The message Rejecting connection – Steam Auth Error: NetworkIdentityFailure does not, by itself, prove that the server files are broken. Follow the checkpoints below in order so you do not change player permissions or port settings when Steam or EAC is the component that actually failed.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Rust Key Cards, Rust Red Key Card, Cobalt Restricted Access Cards, Rust Gift For Gamers, Blue Key... | $25.00 | Buy on Amazon |
| 2 |
|
Rust Video Game Notebook | $15.00 | Buy on Amazon |
| 3 |
|
Rust Game Props Large Furnace (S) | $14.99 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
First, determine which part of authentication failed
Rust authentication crosses several components. A dedicated server must establish its own Steamworks connection, a player’s Steam client must present a valid identity, EAC may need to authenticate the game process, and the client must reach the correct game and query endpoints. The same broad “Steam Auth Failed” wording can therefore have different remedies.
| What you observe | Most likely area to check first | Useful checkpoint |
|---|---|---|
| The server never appears logged on, or repeatedly reports Steam connection failures during startup. | Server files, SteamCMD update, outbound connectivity, or host firewall. | Steamworks reports the server-connected/logged-on state. |
| The server is online, but one player is rejected while other players can join. | That player’s Steam client, Rust files, EAC, VPN, antivirus, or local network. | Restart and update Steam, verify Rust, then follow the EAC branch if the message names EAC. |
| The server is healthy but cannot be found in the browser. | Discovery settings, branch mismatch, browser-ping limit, or query-port forwarding. | Try a direct F1 connection using the server’s reachable address and game port. |
| A local player can connect but remote players cannot. | Public addressing, router forwarding, host firewall, or a restrictive bind address. | Test locally with localhost, then test remotely with the public address. |
| Everyone is rejected after a server update or script change. | Server build integrity, branch, startup parameters, or Steam logon. | Run SteamCMD validation and inspect the complete startup log. |
Facepunch’s Steamworks documentation describes OnSteamNetAuthenticationStatus as the callback used while authentication is in progress. OnSteamServersConnected indicates that the server has established a working connection to the Steam master server and is logged on. OnValidateAuthTicketResponse reports whether an individual user’s authentication ticket was accepted or rejected. Rust server logs or server-side integrations may expose equivalent states under different wording. Use those states to separate a server-wide problem from a single client’s rejection.
#1 Best Overall
- Inspired by the Rust Video Game – These cards replicate the iconic keycards found in Rust (Red, Blue, Green).
- High Quality PVC Plastic – Printed on both sides, durable and water-resistant. Not a sticker.
- Great Rust Gift Idea – Perfect for fans of Rust, whether for cosplay, loot-themed gifts, or collection.
- Wallet-Size Replica – Standard 3.375x2.125 inches, 30 mil thick—fits in any wallet.
- NOT a sticker*
1. Update and validate the Rust dedicated-server installation
Do this before editing permissions, reinstalling plugins, or forwarding additional ports. A partially updated or corrupted server build can fail its Steam handshake and make every player appear unauthenticated.
Run SteamCMD with the correct app ID and login
Facepunch’s documented Linux-style command is:
./steamcmd.sh +force_install_dir ../rust +login anonymous +app_update 258550 validate +quitRun it from the directory containing steamcmd.sh, or adapt only the paths to match your installation. Rust’s Steam app ID is 258550. The +login anonymous argument is required for this installation method; omitting it can produce ERROR! Failed to install app '258550' (No subscription). Let SteamCMD finish and confirm that it reports a successful update and validation rather than stopping on an error.
Check the branch and startup target
Confirm that SteamCMD and the startup script use the branch you intend to run: the regular public branch for ordinary players or the staging branch for a staging installation. A staging server and a public-branch client are not interchangeable for a normal connection test. Make sure the script launches the actual RustDedicated executable from the directory that SteamCMD updated; validating one directory while launching another leaves the running server unchanged.
Review the launch parameters
Keep the game port, query port, and server identity explicit in the launch script. Facepunch setup examples commonly use ports 28015 and 28016, but the important requirement is consistency: the ports in the command, firewall, router, and connection instructions must refer to the same instance. Give each server a stable identity so it does not unexpectedly start as a different installation after a restart.
- Record the exact
server.portused for player connections. - Record the exact
server.queryportused for server-browser queries. - Confirm the identity and data directory are the ones you intend to maintain.
- Remove accidental duplicate launch scripts that start an old copy on the same machine.
Restart after validation and read the complete startup output. Do not treat a process that remains open as proof of a healthy Steam connection; the server must reach the Steam-connected/logged-on checkpoint described above.
2. Confirm that the server is logged on to Steam
A healthy dedicated server reaches the equivalent of OnSteamServersConnected. Facepunch describes that state as the point at which “the server now is logged on and has a working connection to the Steam master server.” If the log never reaches that state, changing a player’s Steam settings cannot solve the server-wide fault.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
If the connected state never appears
- Re-run SteamCMD validation and make sure the launch script uses the validated directory.
- Check that the host can make outbound connections; a restrictive data-center, Windows, or Linux firewall can allow the process to start while blocking Steam services.
- Look for repeated connection failures, DNS errors, or immediate disconnect/reconnect loops in the server log.
- Confirm that the machine’s clock, operating-system updates, and network interface are functioning normally.
- Stop duplicate RustDedicated processes and start one known-good instance with the intended ports.
Only proceed to player-side troubleshooting once the server consistently reaches the connected/logged-on state. If the state appears briefly and then drops, treat that as a server connectivity or host stability problem rather than a bad individual ticket.
Rank #2
3. Repair the affected player’s Steam and Rust installation
When the server is logged on and other players can join, work through Facepunch’s client sequence on the affected computer. Perform these actions in order so a stale Steam session or damaged local files is not mistaken for an EAC or port problem.
- Restart Steam and Rust. Exit Rust, quit Steam completely rather than merely closing the window, start Steam again, and retry the connection.
- Install Steam client updates. Allow Steam to finish any pending update before launching Rust.
- Opt out of Steam beta participation. A beta client can use a different build or authentication path from the public client. Return to the standard Steam client for the test.
- Verify Rust’s files. Use Rust’s Steam library properties and the installed-files verification command. Wait for Steam to complete and replace or reacquire damaged files.
- Perform a fresh Rust installation if the startup problem persists. This is the final client-side step in Facepunch’s sequence; reserve it for a repeatable failure after restart, update, beta opt-out, and verification.
Retry the same server after each meaningful step. If the server log shows a valid ticket response for other users but rejects only this account, save the exact client message and continue with the EAC and local-network checks below.
4. Repair Easy Anti-Cheat when the error names EAC
Facepunch support defines an EAC authentication error as meaning that EAC was unable to authenticate the connection. Treat that as a separate branch from a server that has not logged on to Steam. Run the following sequence on the affected Windows PC:
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →- Launch Rust from the Steam library. Do not use an old desktop shortcut or an executable copied from another installation for this test.
- Allow the cache time to refresh. Facepunch advises waiting up to 10 minutes before judging the first launch after an EAC-related change.
- Verify Rust’s files in Steam. This can restore missing or modified EAC-related files as well as game files.
- Repair EAC. Open the Rust installation’s
EasyAntiCheatfolder, runEasyAntiCheat_EOS_Setup.exe, and choose the repair action. If using a command-oriented workflow, the repair operation isEasyAntiCheat_EOS_Setup.exe repair. - Restart the PC and router. This clears a stuck service, local network state, or stale connection that survived a game restart.
- Install pending Windows updates. Reboot again if Windows requires it.
- Check antivirus and security software. Temporarily test with the security product’s Rust/EAC exception or protection rule corrected according to its documentation. Do not leave protection disabled as a permanent fix.
- Remove the stale EAC client marker if it exists. Facepunch specifically calls out
RustClient.exe.eac; delete that file only when present, then verify files and launch Rust again. - Inspect
output_log.txt. Look for a forbidden application or overlay named by EAC. Close or uninstall the offending program before retrying.
If EAC now authenticates but the server still rejects the connection, return to the server log and determine whether the remaining failure is the Steam ticket response or network reachability. Do not repeatedly reinstall Rust when the log identifies a blocked application or an unreachable port.
5. Separate server discovery from the actual connection
The in-game server browser and the game connection use related but distinct paths. A server can be healthy yet missing from the browser because its query endpoint is not reachable, while a listed server can still reject a player for Steam or EAC reasons.
Use a direct connection test
In Rust, press F1 to open the console and enter:
connect IP:PortReplace IP with the address reachable from the player’s location and Port with the server’s game port. This bypasses browser search. If direct connection works, focus on discovery, query-port forwarding, and browser settings rather than Steam authentication. If direct connection fails as well, preserve the exact console or server-log error and continue with addressing and firewall checks.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsCorrect the Steam browser-ping setting
Facepunch’s server-list support recommends setting Steam’s Server browser pings / minute to a minimum of 5000. This is a browser query threshold, not a guarantee that a server is online and not a bandwidth measurement for the Rust server. Raise it before concluding that a server is unavailable, then refresh the browser after the server has completed its Steam logon.
Rank #3
- Acrylic Painting Pla Plastic
Eliminate common discovery blockers
- Temporarily disable a VPN and retry. A VPN can change the route or public address used for the query and game connection.
- Check both host and client firewall or antivirus rules. Permit the Rust server and the required UDP/TCP traffic according to the server’s configuration.
- Use the regular Rust branch for a normal public-server test; do not mix a staging client with a public server.
- Verify that the query port is forwarded separately from the game port where the router requires separate rules.
6. Verify the address, bind setting, and port forwarding
Facepunch’s server guide distinguishes local and remote addressing. When the client and server run on the same computer, localhost or 127.0.0.1 is appropriate. Remote players need the server’s reachable LAN or public address, depending on where they connect from.
Local test
Run the server and Rust client on the same machine, then use connect 127.0.0.1:game-port for a controlled test. Replace game-port with the value assigned to server.port. This test avoids router hairpinning and public-address issues. A successful local connection proves that the process is listening, but it does not prove that an internet player can reach it.
Remote test
For a player outside the host’s network, use the host’s reachable public address and forward the configured game port to the machine running RustDedicated. Forward the query port as well if browser listing is required. Confirm that the host firewall permits the same ports and protocol used by the server. A correct router rule pointing to the wrong LAN address is functionally the same as no rule, so reserve a stable local address for the server machine.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Check the bind address
Rust normally binds to 0.0.0.0, allowing the server to listen on available interfaces. The +server.ip option can restrict listening to a specific LAN address. That option is useful when a host has multiple interfaces, but an incorrect value can make the process unreachable from the intended network. Remove an unnecessary restriction for testing or set it to the interface that actually owns the forwarded address.
Do not publish a private address to remote players. Conversely, do not use the public address as proof that a same-machine test is configured correctly; use localhost first, then test from an external network.
7. A decision table for the next action
| Server state | Client or connection result | Next action |
|---|---|---|
| No Steam-connected/logged-on state. | All players fail. | Validate app 258550, check branch and launch directory, then investigate outbound connectivity and host firewall. |
| Steam-connected/logged-on state is stable. | Only one player fails. | Restart/update Steam, opt out of beta, verify Rust, and follow the EAC repair sequence if indicated. |
| Server is healthy. | Browser cannot find it, but direct F1 connection works. | Set browser pings/minute to at least 5000 and check the query port, branch, VPN, and discovery firewall rules. |
| Server is healthy. | Localhost works, remote direct connection fails. | Check public address, router forwarding, host firewall, and any restrictive +server.ip binding. |
| Server is healthy. | EAC explicitly reports authentication failure. | Repair EAC, verify files, allow cache refresh, inspect antivirus and output_log.txt. |
8. When managed hosting is an appropriate fallback
Moving to a managed Rust host is an operational choice, not a Steam-authentication repair. It makes sense when maintaining SteamCMD updates, startup scripts, port forwarding, backups, and uptime is the recurring problem. It cannot fix a player’s damaged Steam client, EAC block, VPN route, or a deliberately mismatched branch.
Before moving an existing server, verify the provider’s current Rust build process, whether RCON is supported, how game and query ports are assigned and forwarded, how updates and restarts are handled, and the published refund and service-level terms. Export the server identity, configuration, world data, and permission records where supported, then test a fresh connection before directing players to the new address.
Recommended Free Tools
Quick Recap
Final troubleshooting checklist
- SteamCMD used anonymous login and app ID 258550.
- The validated directory is the same directory launched by
RustDedicated. - The intended public or staging branch matches the client used for testing.
server.port,server.queryport, identity, and bind settings are deliberate.- The server reaches a stable Steam-connected/logged-on state.
- The affected player restarted Steam and Rust, installed Steam updates, left Steam beta, and verified Rust files.
- EAC repair, cache wait, PC/router restart, Windows updates, security checks, and
output_log.txtreview were completed when EAC was named. - VPN and firewall effects were tested separately.
- Steam’s “Server browser pings / minute” is at least 5000.
- Localhost, direct F1 connection, public addressing, and game/query forwarding were tested in that order.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
