3 months ago
Hi everyone,
I’m currently experiencing Redis connection errors that are causing my n8n instance on Railway to crash completely.
I’ve now had two unexpected crashes recently without any configuration changes on my side.
I have attached a screenshot of the logs for reference.
This issue is business-critical for me.
When n8n crashes, my workflows stop and this can directly impact my customers.
I also want to mention the following:
- I created a previous thread about this issue 5 days ago but have not received any response yet.
- I am on the Pro plan with Priority Support, so I would really appreciate urgent assistance.
- I also created a post earlier today, but it appears to have been removed unexpectedly.
Because of the impact this can have on my customers, I would appreciate help as soon as possible.
Thanks in advance for your help.
Attachments
10 Replies
3 months ago
Are there any errors or crash logs in your Redis service?
3 months ago
The screenshot you sent is from the 19th, Railway had networking issues so that may be the reason you couldn't connect to your Redis instance and making your n8n crash: https://discord.com/channels/713503345364697088/846875565357006878/1474056187610665081
3 months ago
If you are on Pro, the ideal flow is to open a Private thread on https://station.railway.com/
3 months ago
Are you still having this issue with your DB?
Idk, it happened 2 times now. Is there a way to increase the timeout from 10s to higher?
3 months ago
Not on Railway's side of things, but afaik there's a QUEUE_BULL_REDIS_TIMEOUT_THRESHOLD env var that you can set on your primary/worker service
3 months ago
But if Redis is basically unreachable then I don't think it will fix your issue.
Status changed to Solved medim • 3 months ago