Periodic issues with Redis

Questions
1

I’ve set up n8n with one main server and two workers. I’m using https://upstash.com/ as the Redis server. Everything runs fine, the workflows are being distributed and executed correctly.

However, every 6 hours Redis seems to be timing out for a short amount of time. Both the main server and the workers at the same time show a “Redis unavailable - trying to reconnect…” message in the logs.

Upstash shows a full uptime status (https://status.upstash.com/) and I couldn’t find anything in the logs that looks suspicious. So I guess it’s something up with n8n.

I found this post Periodic "Redis unavailable" messages - but unfortunately there was no real solution available.

  • n8n version: 1.59.4
  • Database (default: SQLite): postgres (Supabase cloud)
  • n8n EXECUTIONS_PROCESS setting (default: own, main): not specified
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Linux
2

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:
3

If the timeouts are short enough for n8n to recover, and if you have not changed the default timeout, then your timeouts are shorter than 10 seconds, which might be why they are not being reported as downtime by Upstash. Can you deploy Redis elsewhere to rule it out?

4

After trying out different Redis server, I was able to resolve this issue.

My first server was from upstash.com, which had those connectivity issues. I then tried self-hosting Redis. This resulted in even more connectivity issues. Lastly, I tried redis.com. This worked flawlessly.

I don’t know what I did wrong and I’d be happy if someone knows why the self-hosted Redis instance didn’t work.

5

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