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

# WRONGPASS / NOAUTH with Upstash Redis

## What you see

REST: `{ "error": "WRONGPASS invalid password" }`
RESP clients: `NOAUTH Authentication required` or `WRONGPASS invalid username-password pair`

## Causes, in order

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.

## Confirm

REST, with curl:

curl -X POST https://YOUR_REST_URL/ping \
  -H "your auth header

A `{"result":"PONG"}` means the token is good and the problem is in
your client config. A 401 means the token itself is wrong.

## Fix

- Re-copy the token from the console. Tokens are long; a truncated
  paste is the most common cause.
- If the token recently leaked or an employee left, the password was
  probably reset: re-copy the new token everywhere.
- Use the standard token for AUTH, not the read-only one.

## Verify

Re-run the ping above, then run one write (SET) and one read (GET)
through your actual client code.