When TLS is not enabled, library tying to connect to local host

[tudugampala]

I'm not sure whether this is a bug or not. I have spun up a docker Redis cluster (No TLS) in my local Docker environment. I'm trying to connect to the cluster with the following configurations in my Node application (another container). But, what I can see in my node application logs is,
"Redis Cluster Error Error: connect ECONNREFUSED 127.0.0.1:6379".
It seems this library is trying to connect to the localhost. But I have tried with a different library and it worked for the Redis Clustor.
Here are my configs.

const cluster = createCluster({ 
            rootNodes: [
                { url: 'redis://173.18.0.2:6379' },
                { url: 'redis://173.18.0.3:6379' },
                { url: 'redis://173.18.0.4:6379' }
            ],
            nodeAddressMap: {
                'redis://173.18.0.2:6379': { host: 'redis_1', port: 6379 },
                'redis://173.18.0.3:6379': { host: 'redis_2', port: 6379 },
                'redis://173.18.0.4:6379': { host: 'redis_3', port: 6379 }
            },
            defaults: {
                socket: {
                    host: 'redis',
                    connectTimeout: 5000,
                    tls: false
                },
                password: ''
            },
            useReplicas: true
        });

Am I missing any config here? Why does it try to connect to localhost?

[leibale]

Remove the "redis://" from nodeAddressMap keys:

const cluster = createCluster({
  rootNodes: [
    { url: 'redis://173.18.0.2:6379' },
    { url: 'redis://173.18.0.3:6379' },
    { url: 'redis://173.18.0.4:6379' }
  ],
  nodeAddressMap: {
    '173.18.0.2:6379': { host: 'redis_1', port: 6379 },
    '173.18.0.3:6379': { host: 'redis_2', port: 6379 },
    '173.18.0.4:6379': { host: 'redis_3', port: 6379 }
  },
  defaults: {
    socket: {
      host: 'redis',
      connectTimeout: 5000,
      tls: false
    },
    password: ''
  },
  useReplicas: true
});

Also, please make sure that the addresses in nodeAddressMap match the addresses returned from CLUSTER NODES

[tudugampala]

Thank you for the quick response @leibale .
I tried your solution. But I got the same error message. Then I tried the following solution and it gives
"Invalid URL: 173.18.0.2" error message. Any idea?

const cluster = createCluster({
            rootNodes: [
                { url: '173.18.0.2' },
                { url: '173.18.0.3' },
                { url: '173.18.0.4' }
            ],
            nodeAddressMap: {
                '173.18.0.2:6379': { host: 'redis_1', port: 6379 },
                '173.18.0.3:6379': { host: 'redis_2', port: 6379 },
                '173.18.0.4:6379': { host: 'redis_3', port: 6379 }
            },
            defaults: {
                socket: {
                    host: 'redis',
                    connectTimeout: 5000,
                    tls: false
                },
                password: ''
            },
            useReplicas: true
        });

(removed "redis://") from both nodeAddressMap and rootNodes.

[tudugampala]

And I checked the network info of "173.18.0.2" container. This is how it looks like. @leibale

"Networks": {
    "wel-sdl-platform_app-network": {
        "IPAMConfig": {
            "IPv4Address": "173.18.0.2"
        },
        "Links": null,
        "Aliases": [
            "redis_1",
            "redis_1",
            "9a19f7111547"
        ],
        "NetworkID": "dc3ee2556a94db2031385cc01f8fe1f17c549c6331d26da7cded6f678a4091fa",
        "EndpointID": "58106bd4d1265f4e34fabae8703f49b41276dc54cacc55b558cd2b75404e5e03",
        "Gateway": "173.18.0.1",
        "IPAddress": "173.18.0.2",
        "IPPrefixLen": 16,
        "IPv6Gateway": "",
        "GlobalIPv6Address": "",
        "GlobalIPv6PrefixLen": 0,
        "DriverOpts": null
    }
}

[tudugampala]

@leibale
I tried this too ... But it gives "Connection timeout app | at TLSSocket" even I have turned off TLS in configs.

Redis Cluster Error ConnectionTimeoutError: Connection timeout
app | at TLSSocket. (/home/node/app/node_modules/@node-redis/client/dist/lib/client/socket.js:169:124)

const cluster = createCluster({
    rootNodes: [
        { url: 'rediss://173.18.0.2:6379' },
        { url: 'rediss://173.18.0.3:6379' },
        { url: 'rediss://173.18.0.4:6379' }
    ],
    nodeAddressMap: {
        '173.18.0.2:6379': { host: 'redis_1', port: 6379 },
        '173.18.0.3:6379': { host: 'redis_2', port: 6379 },
        '173.18.0.4:6379': { host: 'redis_3', port: 6379 }
    },
    defaults: {
        socket: {
            host: 'redis',
            connectTimeout: 5000,
            tls: false
        },
        password: ''
    },
    useReplicas: true
});

[leibale]

@tudugampala please run CLUSTER NODES using redis-cli and share the reply

[tudugampala]

@leibale I will let you know the result. Also, I want to mention that the Redis-commander UI is being run as a separate container and it is also able to connect to the cluster. As I mentioned earlier I was able to connect to the cluster with the library that uses redis-commander UI. But I need to find out what is going on with this lib.