TLS redis failing

[luisfilipe575]

<Hello, I would like to know if the n8n has provision for adjusting the redis TLS configuration. as we cannot enable TLS, but it turns out to be a security hole.>

[MutedJam]

Hi @luisfilipe575, welcome to the community!

I am afraid at the moment n8n does not have support for TLS connections to Redis

You might want to leave a vote on the respective feature request over here to have this implemented:

Redis TLS support for Bull in queue mode

The idea is: Add Bull Redis configuration for supporting secure Redis(AWS Elsaticache) TLS connection. My use case: Scalable n8n cluster deployment in AWS I think it would be beneficial to add this because: Secure Bull Redis Any resources to support this? Patch --- packages/cli/config/schema.ts | 50 +++++++++++++++++++++++++++++++++++ packages/cli/src/Queue.ts | 35 +++++++++++++++++++++++- 2 files changed, 84 insertions(+), 1 deletion(-) diff --git a/packages/cli/config/schema.ts…

[luisfilipe575]

Hi @MutedJam, I understand that n8n does not support TLS Redis connections, but is there a future development to fix this vulnerability?

while there is no support is there another way to fix it?

[Jon]

Hey @luisfilipe575,

There is already a PR that implements it and it is just waiting for the review process which will involve testing. If you don’t want to use Redis without TLS you can make your own docker image that implements the changes or if you are using npm you could look at using an SSH tunnel.

This is assuming you are referring to queue mode and not the Redis node.

[luisfilipe575]

Hi @Jon, I’m using k8s to provision my n8n, always using the last image to get the corrections and improvements of the tool. As new versions of n8n always come out, I would have to constantly update my images. In that case I’ll wait for the correction PR.

Thanks!