Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Redis NOAUTH Authentication required and WRONGPASS invalid username-password pair

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

NOAUTH Authentication required. means a command arrived on a connection that has not authenticated, and the server needs authentication. WRONGPASS invalid username-password pair or user is disabled. means an AUTH or HELLO attempt named a user and password that the server did not accept. The two errors point in different directions. NOAUTH is a missing login on the client. WRONGPASS is a wrong or disabled login.

What the errors mean

The AUTH page says the command authenticates the current connection in two cases: when the server is password protected through requirepass, and when a Redis 6.0 or later instance uses the ACL system. With ACLs, "the single argument form of the command, where only the password is specified, assumes that the implicit username is "default"." The redis.conf file says that since Redis 6 requirepass "is just a compatibility layer on top of the new ACL system", and its effect "will be just setting the password for the default user."

The two message texts come from the Redis source code, releases 8.0.6 and 7.2.17, not from the documentation pages. In that source code, -NOAUTH Authentication required. is returned for any command except AUTH, HELLO and the other no-auth commands when the connection is not authenticated. -WRONGPASS invalid username-password pair or user is disabled. is returned when authentication fails. The ACL LOG page's example of a failed attempt shows a shorter form, WRONGPASS invalid username-password pair.

The ACL page describes a user that is turned off: off means "it's no longer possible to authenticate with this user; however, previously authenticated connections will still work." For the default user it adds that if the default user is flagged off, new connections "will start as not authenticated and will require" AUTH or HELLO.

Likely causes

Cause What you see How to confirm
Client has no password configured NOAUTH on the first command redis-cli -h host PING without a password returns NOAUTH; ACL LIST shows the default user without nopass
Someone added a password to a running service Applications worked yesterday and now all get NOAUTH The redis.conf has requirepass, or the default user has a password hash
Wrong password WRONGPASS ACL LOG shows an entry with reason auth and the user name
Wrong or missing user name WRONGPASS from a client that sends a name ACL LIST has no such user
User flagged off WRONGPASS with the right password The user's line in ACL LIST contains off
requirepass is ignored The default user keeps nopass The redis.conf says requirepass "is not compatible with aclfile option and the ACL LOAD command"
ACL change was not saved Works until the next restart, then WRONGPASS The user's password hash differs from before the restart

Prove the cause before changing anything

All of these are read-only. Some show password hashes; keep the output private.

1. Reproduce without a password.

redis-cli -h 192.0.2.20 PING

A reply of NOAUTH Authentication required proves the server wants a login and the client sent none. PONG means no login is needed.

2. Test the login the application uses. The redis-cli manual says the password can be passed "more safely" through the REDISCLI_AUTH environment variable than with -a, and that --askpass reads it from the terminal with a mask:

redis-cli -h 192.0.2.20 --askpass PING

That form tries the default user. The redis-cli manual says --user "Needs -a", while --askpass says "'-a' and REDISCLI_AUTH environment variable will be ignored", and the page does not say that the two options work together. A named user can also be tested by opening a session, as the redis-cli manual's AUTH some_admin_user ... example does, and typing the two-argument AUTH at its prompt. Open the session from the shell:

redis-cli -h 192.0.2.20

Then type this at the redis-cli prompt, not in the shell, with the user name and then the password:

AUTH alice <password>

A good result is OK. The redis-cli source code (release 8.0.6) does not write AUTH lines, or ACL SETUSER, ACL GETUSER and ACL DELUSER lines, to the history file once it has split the line into arguments; its comment lists them as commands that "shouldn't be put in the history file". A line it cannot split, such as one with an unbalanced quote, is still saved to the history file, so type the password carefully.

3. Read the users and recent failures on the server. Run these as a user allowed to use them:

redis-cli ACL WHOAMI
redis-cli ACL LIST
redis-cli ACL LOG

ACL WHOAMI returns the user the connection is authenticated with. ACL LIST prints one line per user: on or off, nopass or password hashes, and permissions. ACL LOG lists recent security events, including failed authentications, which show reason auth. By default it returns up to ten entries, newest first, and each entry names the username, so you can see which name the client sent. If the default user has a password, add --askpass to each of these commands to authenticate as the default user, as in step 2.

4. Look for settings that override each other.

grep -n -e requirepass -e aclfile -e '^user ' /etc/redis/redis.conf

This prints any password set with requirepass in clear text. Run it where nobody can read your screen. Use the config_file value from redis-cli INFO server if your file is elsewhere.

Fix

NOAUTH: give the client the login

The client needs the user name (if the server uses ACL users) and the password in the application's own settings. The AUTH page says a password can be one the server holds through requirepass, or the user's password under ACLs.

First save the current settings file. The path is an example; use the file your application reads:

cp -p /etc/webapp/redis.env /etc/webapp/redis.env.2026-11-22

Disruptive step: the next edit and the application restart that follows drop the application's open Redis connections and its sessions.

Edit the file so it carries the password or the user name and password, then restart the application (the unit name webapp is an example):

systemctl restart webapp

To back out: put the saved file back under its own name and restart again.

cp -p /etc/webapp/redis.env.2026-11-22 /etc/webapp/redis.env
systemctl restart webapp

WRONGPASS: the user is off

First print the user's current definition and keep the output:

redis-cli ACL GETUSER alice

Risk: the next command lets the named user authenticate again with every permission it holds. Check the permissions in the output you kept first.

redis-cli ACL SETUSER alice on

The ACL SETUSER page lists on and off as the rules that enable and disable a user. To undo it: run redis-cli ACL SETUSER alice off, which stops new logins for that user. Connections already authenticated keep working, as the ACL page says.

WRONGPASS: nobody knows the password

First print the users and keep the line for this user, which holds its password hashes:

redis-cli ACL LIST

Copy the line that begins user alice somewhere safe. The ACL pages say #hash adds a SHA-256 hash as a valid password, >password adds a clear-text password, and resetpass removes all passwords and the nopass status.

Risk: the next command removes every existing password of the user, so any client using an old password gets WRONGPASS until it is updated.

Open a session from the shell:

redis-cli --askpass

Then type the command at the redis-cli prompt, not on the shell command line, because in a shell >newpassword would be a redirection that creates a file:

ACL SETUSER alice resetpass >newpassword

To undo it: in a session, restore every password hash shown on the saved ACL LIST line, because a user can hold any number of passwords. With two hashes on the saved line, the command has this form, with each hash copied from that line:

ACL SETUSER alice resetpass #<first-hash> #<second-hash>

If the saved line showed nopass instead of hashes, use ACL SETUSER alice nopass.

Use a long password. The AUTH page says "it is possible to try a lot of passwords in parallel in very short time", and suggests ACL GENPASS to generate one.

Make the change survive a restart

ACL SETUSER changes memory only. The ACL page says that with users defined in redis.conf you can use CONFIG REWRITE, and with an external ACL file you use ACL SAVE. It adds that CONFIG REWRITE "does not also trigger ACL SAVE". With an ACL file:

First copy the file (the path is an example; use your aclfile value):

cp -p /etc/redis/users.acl /etc/redis/users.acl.2026-11-22

Risk: the next command overwrites the ACL file with the users now in memory. Manual edits in the file that were not loaded are lost.

redis-cli ACL SAVE

To back out: put the copy back and reload it. ACL LOAD replaces all current rules with the file's. This also drops any user change made since the copy, so run it only if you want the state of the copy back.

cp -p /etc/redis/users.acl.2026-11-22 /etc/redis/users.acl
redis-cli ACL LOAD

Example (illustrative): redis01 (192.0.2.20) serves app.example.com. A maintenance change adds requirepass and restarts Redis. The application starts logging NOAUTH Authentication required. redis-cli -h 192.0.2.20 PING returns the same text, and ACL LIST shows the default user without nopass. A second service, which uses user alice, logs WRONGPASS. ACL LOG shows reason auth with username alice, and ACL LIST shows user alice off. The engineer saves the application file, adds the password and restarts the application, saves the output of ACL GETUSER alice, enables the user, and runs ACL SAVE after copying the ACL file.

Confirm the fix

  1. redis-cli -h 192.0.2.20 --askpass PING returns PONG.
  2. The application logs no new NOAUTH or WRONGPASS lines after restart.
  3. redis-cli ACL LOG shows no new entries with reason auth after the change.
  4. After a restart of Redis, the same login still works.

What to watch afterwards

  • Store the password once, in your secrets store, and have each application read it from there.
  • Give each application its own ACL user, so ACL LOG shows which one fails.
  • Check ACL LOG after every planned change to passwords.
  • Do not combine requirepass with an ACL file and expect both to apply.

Risks and limits

  • These commands have not been run or lab-tested.
  • Message wording is from the Redis source code at releases 8.0.6 and 7.2.17. Other releases may word them differently, and Redis before 6.0 understands only the one-argument form of AUTH.
  • The password is sent unencrypted unless TLS is used. The AUTH command, like every other, is sent unencrypted, as the security page says.
  • Redis Software, Redis Cloud and managed services manage users in their own consoles.

Sources

  • AUTH — Redis documentation, page metadata modified 2026-09-18, accessed 22 November 2026
  • ACL — Redis documentation, page metadata modified 2026-10-13, accessed 22 November 2026
  • Redis security — Redis documentation, page metadata modified 2026-09-30, accessed 22 November 2026
  • ACL SETUSER — Redis documentation, page metadata modified 2026-09-18, accessed 22 November 2026
  • ACL LIST — Redis documentation, page metadata modified 2026-09-18, accessed 22 November 2026
  • ACL LOG — Redis documentation, page metadata modified 2026-09-18, accessed 22 November 2026
  • ACL GETUSER — Redis documentation, page metadata modified 2026-09-18, accessed 22 November 2026
  • ACL WHOAMI — Redis documentation, page metadata modified 2026-09-18, accessed 22 November 2026
  • ACL SAVE — Redis documentation, page metadata modified 2026-01-30, accessed 22 November 2026
  • ACL LOAD — Redis documentation, page metadata modified 2026-05-25, accessed 22 November 2026
  • redis-cli — Redis documentation, page metadata modified 2026-09-11, accessed 22 November 2026
  • redis-cli.c — Redis source code, release tag 8.0.6, no date shown, accessed 22 November 2026
  • redis.conf (release 8.0.6) — Redis source code, release tag 8.0.6, no date shown, accessed 22 November 2026
  • server.c and acl.c — Redis source code, release tag 8.0.6 (same lines at 7.2.17), no date shown, accessed 22 November 2026
  • grep(1) — GNU grep manual page, 2025-03-21, accessed 22 November 2026
  • cp(1) — GNU coreutils 9.11 manual page, April 2026, accessed 22 November 2026
  • systemctl — systemd manual, no date shown, accessed 22 November 2026