WRONGPASS invalid username-password pair

[leobeosab]

Issue

Hi, I wish I had more time to fill this out but I'm making this for others who are having this issue. Our Node applications started crashing on startup when we updated (without realizing) to 3.1.0. Thankfully this only happened on our stage servers so no harm was done! But hopefully, others find this helpful!

The error is as follows

ReplyError: WRONGPASS invalid username-password pair
    at parseError (redacted.../node_modules/redis/node_modules/redis-parser/lib/parser.js:179:12)
    at parseType (redacted.../node_modules/redis/node_modules/redis-parser/lib/parser.js:302:14) {
  command: 'AUTH',
  args: [ 'redacted', 'redacted' ],
  code: 'WRONGPASS'
}

The username-password pair is correct and works before 3.1.0 to fix this for now we downgraded to 3.0.2

---

Environment

• Node.js Version: 14.15.4

• Redis Version: Unkown (I can add once I find out)

• Platform: MacOS 11.0.1, Heroku Node, Arch Linux

[darklight147]

UP, i can confirm that this issue exists an encountered it just now, trying to connect to my remote redis database

[leibale]

@lebseu @darklight147 are you using the default user or a custom ACL user?
If you're using the default user, make sure the set the username to "default" or just leave it empty.

[darklight147]

@leibale resolved issue by reverting to version 3.0.2, although this would work for a higher version expect latest, am using this code to connect to my remote redis db:

export const redisClient = redis.createClient({
	url: redisUri,
});

my redisUri is formated this way: redis://username:password@host-domain:15601

[leibale]

@darklight147 try to change the "username" to "default"

[darklight147]

@leibale that can't be right, because those are the credentials to my database

[leibale]

@darklight147 until version 3.1.0 the username part was ignored, so please try to set it to "default" (or leave it empty) and check if that's help

[bamse16]

I have the same issue as @darklight147. Setting the username to redis://default:password@ip or empty string redis://:password@ip does not help.

The only thing that helps is setting the connection string as redis://password@ip, no username: part.

When a username is present, even if named default, the auth command is sent as auth 'default', 'password' and redis 3.0.6 rejects that.

Edit: The error I get is: Redis connection error: ReplyError: ERR wrong number of arguments for 'auth' command..

[darklight147]

@bamse16 3.0.2 works fine for now, give it a shot

[bamse16]

Thanks @darklight147. Forgot to mention that 3.0.2 works for me as well. I'm trying to get the latest version to work.

[leibale]

I tried reproducing it with

redis-server --requirepass password

require('redis').createClient('redis://:password@localhost:6379');

and it fired

AUTH password

@leobeosab @darklight147 @bamse16 what am I missing?

[bamse16]

I've tried redis://:password@localhost:6379 and that works for me as well. Previously, a package that was parsing the URI would not handle empty username, so that was not related to this package.

[n1k0sv]

Heroku deployments are broken at 3.1.0, initializing the client using:

require('redis').createClient(process.env.REDIS_URL)

where REDIS_URL is set automatically by Heroku using the format redis://h:<password>@<host>:<port>

The error is:

Uncaught ReplyError: Ready check failed: NOAUTH Authentication required.
    at parseError (/app/node_modules/redis-parser/lib/parser.js:179:12)
    at parseType (/app/node_modules/redis-parser/lib/parser.js:302:14)

This renders the latest version unusable on Heroku, everything is working fine at 3.0.2 though.

[gkorland]

@bamse16 using redis://:password@localhost:6379 should do the trick.
@nbasili you should try without the username h --> redis://:<password>@<host>:<port>

[neemah]

So the 3.1.0 breaking production for many users due to it stopped supporting URL with a username.

Is this something needed to be mentioned in the changelog or is there a fix to, for example, ignore username in the URL so this won't be a matter? :-)

[jonabantao]

We're having this issue as well. Like others said, 3.0.2 resolves it for us.
We're reading the redis connection string from whatever the cloud environment gives us, which for right now is rediss://<username>:<password>@<ip>:<port>

The error we got was 'wrong number of arguments for 'auth' command'.