n8n keeps crashing due to Redis connection timeout (ETIMEDOUT)
herocovers
PROOP

17 days ago

Hi Support Team,

I’m encountering a persistent issue where my n8n instance repeatedly crashes due to Redis connection timeouts.

n8n starts successfully, but shortly after startup it fails to connect to Redis, retries for 10 seconds, and then exits the process. This causes a crash loop and prevents n8n from staying online.

Observed Behavior:

  • n8n starts normally

  • Task Broker initializes

  • Redis connection attempts fail with ETIMEDOUT

  • n8n retries for 10 seconds

  • Process exits due to Redis connection error

  • Session restarts and crashes again

Relevant Logs:

2026-02-21T00:51:20.147Z [inf] n8n Task Broker ready on 127.0.0.1, port 5679

2026-02-21T00:51:22.016Z [inf] [Redis client] connect ETIMEDOUT

2026-02-21T00:51:23.099Z [inf] Lost Redis connection. Trying to reconnect in 1s... (0s/10s)

2026-02-21T00:51:32.537Z [inf] Unable to connect to Redis after trying to connect for 10s

2026-02-21T00:51:32.537Z [inf] Exiting process due to Redis connection error

2026-02-21T00:51:36.648Z [inf] Last session crashed

This pattern repeats continuously.

$10 Bounty

7 Replies

angelo-railway

I have fixed this, this was due to our outage here https://blog.railway.com/p/incident-report-february-11-2026 - I restarted Redis and restored your N8N.

herocovers
PROOP

17 days ago

Same issue. Need help asap. Thank you


Are you still experiencing this issue?


0x5b62656e5d

Are you still experiencing this issue?

herocovers
PROOP

15 days ago

I am still experiencing the issue


Status changed to Open brody 15 days ago


Is your Redis online and running?


herocovers
PROOP

15 days ago

Its online but it says The database deployment has stopped running.

Attachments


0x5b62656e5d

Is your Redis online and running?

herocovers
PROOP

15 days ago

online but not running


Try redeploying your Redis database, then your n8n workers if Redis starts successfully. This may be related to the following incident: https://blog.railway.com/p/incident-report-february-11-2026


Loading...