redis / redis/node-redis

Cluster connection error [ErrorReply: ERR Protocol error: unauthenticated multibulk length]

Open
#2,286 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bug stale
Dominant language
TypeScript
Stars
17.6k
Forks
2k
Avg merge
2d 3h
Merged PRs (30d)
40

Description

I am getting an error with these connection settings. Related to the previous error but different, this one is connected directly with the node-redis cluster connection:

The error I keep getting is this. [ErrorReply: ERR Protocol error: unauthenticated multibulk length]

this.client = createCluster({
        rootNodes: [
          {
            url: 'redis://ip.address.here:6379',
            username: 'default',
            password: 'password'
          },
          {
            url: 'redis://ip.address.here:6379',
            username: 'default',
            password: 'password'
          },
          {
            url: 'redis://ip.address.here:6379',
            username: 'default',
            password: 'password'
          },
          {
            url: 'redis://ip.address.here:6379',
            username: 'default',
            password: 'password'
          },
          {
            url: 'redis://ip.address.here:6379',
            username: 'default',
            password: 'password'
          },
          {
            url: 'redis://ip.address.here:6379',
            username: 'default',
            password: 'password'
          },
        ]
			});

Environment:

  • Node.js Version: 16
  • Redis Server Version: 7.0.4
  • Node Redis Version: 4.+ latest
  • Platform: linux/ubuntu

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository files or tests are named. Start by reproducing the createCluster connection with the supplied rootNodes, authentication settings, and Node.js, Redis, and node-redis versions; inspect the cluster connection and authentication path. Done means identifying whether the protocol error comes from the client or server configuration and documenting or fixing the confirmed cause.

Written by the indexing model from the issue text.

Assessment

Tech stack
redis, typescript
Domain
backend, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.