RCON Authentication Failed on Rust Console: Fix Password Symbols and the Login Lockout

First, read the exact error: auth failed is not connection refused

Before you change anything, read the exact words your bot gave you. If the message says authentication failed, auth failed, login failed, or something with a 401 in it, that is actually half good news. Your bot reached the server. The IP and the RCON port were correct, the server answered, and only the password was rejected. That narrows the whole problem down to one field.

If instead you see connection refused, connection timed out, or the wheel just spins forever, that is a different problem. The bot never reached the server at all, which usually points at the wrong port or a blocked connection, not the password. If you are not certain which of the two you are looking at, the first-connection troubleshooter for WebRCON separates them cleanly before you touch a single setting.

Cause 1: a special character in your host-generated password

Host panels love to generate a random password stuffed with letters, numbers, and symbols. Symbols are exactly where auth quietly breaks. A space, a quote mark, an ampersand, a backslash, a percent sign, or an angle bracket can get mangled the moment you copy it, or get read as part of the connection instead of part of the password. The result is an auth string that no longer matches what the server expects, so Rust rejects it as failed even though it looks perfectly correct on your screen.

The fix is not to hunt for the one bad character. It is to replace the entire password with one that has no symbols at all: 12 to 20 characters, letters and numbers only. That removes the whole class of problem in a single move, and a mix of upper case, lower case, and digits is still plenty strong for an RCON password that never leaves your host panel and your bot.

Cause 2: Rust locks RCON after failed logins, so retrying makes it worse

This is the one that traps people. When RCON receives several failed login attempts in a short window, Rust briefly rate-limits and locks further attempts. During that cooldown it will reject even the correct password. So the natural instinct, hammering Connect again and again, is the single worst thing you can do. Each failed attempt can restart the clock and stretch the lockout longer.

If you have been mashing retry for the last few minutes, your password might already be right and you would have no way to know. Stop completely. Wait a few minutes with zero attempts. Then try exactly once, with a password you are confident in. That patience is the entire fix for the locked-out-after-failed-login case, and it costs you nothing but a short break.

Reset your RCON password the clean way

On G-Portal, which connects by direct WebRCON using an IP, an RCON port, and a password, reset it like this. First, open your host control panel and either stop the server or be ready to restart it. Second, find the RCON or WebRCON password field in your server settings or config. Third, replace it with a clean password of 12 to 20 characters using only A to Z, a to z, and 0 to 9, with no spaces and no symbols.

Fourth, save and restart the server so the new password actually loads. On most hosts a changed RCON password does not take effect until the server restarts, so skipping this step leaves the server still expecting the old one. Fifth, wait until the server is fully back online. Sixth, paste the new password into your bot once and connect a single time. When you copy it, grab the value with no space before or after it. If you are not sure where each value lives, our guide to find your WebRCON IP, port, and password shows exactly where the password sits on both G-Portal and Nitrado.

Rule out the copy-paste and port lookalikes

A few smaller things dress up as a password problem. The most common is trailing whitespace: a single space copied after the password will fail auth every time, and it is invisible in the box. If you suspect it, delete the last character and retype it by hand.

Two more are worth a quick check. If your error is really connection refused rather than auth failed, you may have put the game port where the RCON port belongs. The RCON port, commonly 28016 over TCP, is not the game port server.port, which is 28015 over UDP, and mixing them is the classic case where players can join but the bot cannot. We break this down in the difference between the RCON port and the server port. Finally, some hosts need WebRCON switched on with rcon.web set to 1. If it is left at 0, the bot has no web endpoint to authenticate against no matter how correct the password is.

Stop it happening again with a connection that has no password to break

Every problem above traces back to one thing: a fragile secret you have to copy by hand. Nitrado, one of the two official Rust Console hosts, connects to Vantic with a one-click account link instead. You authorize the connection once from inside your Nitrado account, and there is no IP, port, or password to paste, mistype, or leave a stray symbol in. That is why connecting a bot through Nitrado is the most forgiving path for owners who never want to think about auth again.

On G-Portal you will still use direct WebRCON, so a clean letters-and-numbers password and the one-attempt rule stay your best friends, especially since G-Portal reboots the server on a Facepunch patch and a good bot simply reconnects afterward without you re-entering anything. Either way, the goal is the same: a small auth hiccup should never be able to turn into a dead server.

Frequently asked questions

Keep reading

why WebRCON will not connect · find your WebRCON IP, port, and password · the RCON port versus the server port · connect a bot through Nitrado · connect a bot on G-Portal