Redis Node Connection Timeout

Describe the problem/error/question

I’m using the Redis Node to implement rate limiting on my n8n workflow, this used to work without problems until recently, I started to experience a lot of workflow errors with the node displaying a connection timeout.

The problem is eratic, sometimes the workflow runs smoothly, and at other times not. The Redis DB is hosted on Redis Cloud, where I have a reasonable paid subscription. There are no errors recorded in the Redis logs and when I look at the n8n run history, I don’t see anything to suggest too many requests are being sent to the server.

I am using the simplest implementation to increment a key with a timeout.

Hoping that somebody here might have had a similar experience and may be able to offer some support. Another user describes a similar issue here - however unlike them, the database doesn’t contain unexpired keys (and I’m not sure why that would cause a connection timeout anyway).

How can I verify if this is a problem with n8n or my workflow, or with my Redis configuration?

What is the error message (if any)?

n8n version

1.37.0 (Cloud)

Stack trace

Error: Connection timeout at Socket.<anonymous> (/usr/local/lib/node_modules/n8n/node_modules/@redis/client/dist/lib/client/socket.js:178:124) at Object.onceWrapper (node:events:631:28) at Socket.emit (node:events:517:28) at Socket.emit (node:domain:489:12) at Socket._onTimeout (node:net:598:8) at listOnTimeout (node:internal/timers:569:17) at processTimers (node:internal/timers:512:7)

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

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

Hey @Felix_is_stuck,

It sounds like we are timing out when connecting to the redis instance, Where are you running it?

I suspect a good possible starting point would be if we actually had a timeout option for the connection that could be increased.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.