Rediss connection

[Antonio1]

Describe the problem/error/question

cant connect to Redic from n8n credentials settings

What is the error message (if any)?

keep spinning

Please share your workflow

I tried to put USER:PASSWD to “Password” field - no luck

I can connect using CLI
redis-cli -u ‘rediss://USER:[email protected]:21275’

Information on your n8n setup

• n8n version: n8nio/n8n:latest
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via Docker,
• **Operating system: Debian 11

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[Antonio1]

any advice?

[Antonio1]

still here

[jan]

Welcome to the community @Antonio1 !

Can the n8n Docker container reach redis? So did you configure it accordingly? For example setting network=host or having both containers in the same “Docker-Network”?

[netroy]

The extra s in rediss:// implies a TLS connection, which the Redis node currently does not support.

However, we just created a PR yesterday to add TLS support, and simply haven’t gotten around to testing it properly yet.

If you want to help us expedite this PR, you could test the docker image n8nio/n8n:redis-node-tls-support and let us know if this fixes the issue for you.

[Antonio1]

I tried putting default:PASS into Password field

for some reason, it is trying to connect. to. 6379. port according to screendhot

[Antonio1]

yes im accessing Redis from same local network

[netroy]

The error ECONNREFUSED ::1:6379 implies that not only is the port incorrect, but also the host (::1 is localhost in IPv6).
Unfortunately I’m not able to reproduce this issue.
Can you please try creating a new Redis credential, and see if you can still reproduce this?

[netroy]

BTW, for SSL to work, you also need to use the hostname of the Redis instance to make sure that the hostname matches the domain in the TLS certificate. using just the IP will likely return a TLS error.

[Antonio1]

thanks for reply
what i did

1- disable IP v6 on host OS
2-reboot
3-check that IPv6 is not used anymore with docker

4- inside n8n web interface i delete Redis credentials
and recreate new one but same issue

P.S
Checked TCPDUMP and noticed when i did not set SSL on Redis Cred config
there is a traffic to 21275 port

but when I switch SSL tougle → NO traffic in tcpdump
So node is not sending traffic at all

P.S.S
I tested and I can see traffic in tcpdump
when I’m using redis-cli with rediss://

[netroy]

Sorry, this was due to a stupid mistake on my part.
When SSL was enabled, the code I changed was overwriting the host and port values being passed into the redis client options.
I’ve updated the PR, and also create a new docker image with the same tag.
Can you please pull the docker image, and try again ?

[Antonio1]

it is working now!!!
thanks

when this nightly update will be in the latest ?

FYI
I just had to put password (without login) in a password field

[netroy]

It’s good to hear that it’s working now.
I’ve updated the PR and added some tests. Unfortunately this won’t make it into today’s release, but you should be able to use this via the nightly image soon, and the change should be in the 1.41 release scheduled for next Wednesday.

[Antonio1]

perfect
thanks again
have a great day

[jan]

New version [email protected] got released which includes the GitHub PR 9266.