Redis

NOAUTH Authentication required.

NOAUTH Authentication required: what requirepass and ACLs have to do with it, and the exact AUTH command to fix it.

What it means

NOAUTH Authentication required. means the Redis (or Valkey/Dragonfly/KeyDB) server has a password set — either the simple requirepass option or the newer ACL system — and the client sent a command before authenticating. Redis refuses every command from an unauthenticated connection (apart from a few like AUTH and HELLO) until authentication succeeds; there’s no partial access, so this shows up on the very first real command, not gradually.

Common causes

  • Connecting to a server with requirepass set, using a client or script that never sends AUTH.
  • A managed Redis/Valkey service that ships with a password turned on, catching developers used to a local, unauthenticated Redis instance.
  • The Redis ACL system (Redis 6+) enabled with a non-default user, where a connection needs both a username and a password, not just a password.
  • A password rotated or changed (by a teammate, a secrets manager, or an infrastructure change) without updating every client’s configuration.
  • A connection pool or proxy that reuses connections without re-authenticating each one, if authentication state isn’t preserved correctly across pooled connections.

How to fix it

  1. Authenticate explicitly before any other command: AUTH yourpassword (with requirepass), or AUTH yourusername yourpassword (with ACLs) — most clients accept credentials in the connection URL or options rather than as a separate command.
  2. In redis-cli, either pass it upfront (redis-cli -a yourpassword, or --user / --pass with ACLs) or run AUTH as the first command in the session.
  3. If you don’t know the current password, look for requirepass in the server’s redis.conf (or the users in its ACL file), or in whatever secrets store your infrastructure keeps it in. ACL LIST from an admin session shows ACL users, but their passwords only as SHA-256 hashes.
  4. If ACLs are in use, confirm which username the client should authenticate as — omitting it implicitly means default, which may not have the permissions (or the password) you’re using.
  5. Double-check any connection pooling layer re-sends AUTH on each new physical connection, not just the first one the pool opens.
  6. If the server is reachable over TLS only, confirm the client negotiates TLS before it sends AUTH — a plaintext connection to a TLS-only port fails at the handshake, before authentication even has a chance to run.

In Tablyne

Tablyne’s connection form has a password field (and a username field for ACL users) so authentication happens as part of connecting — the password is then stored in your OS keychain, not typed again on every session, and TLS with its own SNI is configured in the same form if the server requires it.

Connect once, authenticated every time after. Download Tablyne or open the Redis & Valkey GUI.

Sources

Frequently asked questions

Why did this start happening after a hosting change? +

Many managed Redis and Valkey services turn on a password (requirepass) or ACL users for new instances, while a local development install usually has none. Moving from local Redis to a hosted one is a very common trigger.

Is NOAUTH the same as a wrong password? +

No. NOAUTH means no AUTH was sent at all before a command that requires it. A wrong password produces a different error after an AUTH attempt was actually made: on Redis 6 and later, 'WRONGPASS invalid username-password pair or user is disabled.'

Do I need a username, or just a password? +

It depends on whether the server uses plain requirepass or the ACL system (Redis 6+). With requirepass alone, AUTH <password> is enough. With ACLs, AUTH <username> <password> authenticates as that specific ACL user; omitting the username implicitly means the 'default' user.

Related errors