Upstash Redis WRONGPASS / NOAUTH: the token is the password, check TLS and which token you used

TL;DR: WRONGPASS or NOAUTH means the password is wrong or missing. With Upstash the password is the console token, and TLS must be on. Run AUTH with the token as the first command on a fresh connection. Confirm REST, with curl: curl -X POST https://YOURRESTURL/ping \ -H "your auth header A {"result":"PONG"} means the token is good and the problem is in your client config.

The error

{ "error": "WRONGPASS invalid password" }

The fix

1. You pasted the wrong token. The password is the token from the console Connect tab. There is no separate password anywhere.
2. You used the read-only token where a write or admin command needs the standard token.
3. Over RESP you skipped AUTH. Run AUTH with the token as the first command on a fresh connection.
4. Over RESP you connected without TLS. The handshake fails before auth and some clients report it as an auth error.
5. Re-copy the token from the console. Tokens are long; a truncated paste is the most common cause.
6. If the token recently leaked or an employee left, the password was probably reset: re-copy the new token everywhere.
7. Use the standard token for AUTH, not the read-only one.

When to use this

• You are seeing this exact error message; match the block above, not just part of it.
• The failing call matches the scenario in the title: Upstash Redis WRONGPASS / NOAUTH.
• You want the fastest verified fix before digging through logs.

When not to use this

• Your error text differs from the block above; close cousins often have different causes.
• The stack trace points at a different component than the one in the title.
• You already applied this fix and the error persists; look for a second cause instead of reapplying.

Compatibility

• Not pinned to a specific version; follows current Upstash behavior.

Also seen as

• WRONGPASS invalid username-password pair

Verified against Upstash docs: REST error example { error: WRONGPASS invalid password }; connect-client docs state the console token is the password (no separate password exists) and TLS is always on; AUTH with the token is required before commands. Sources: https://upstash.com/docs/redis/features/restapi https://upstash.com/docs/redis/howto/connect-client