2 months ago
Hello,
I am experiencing connectivity issues with my n8n instance and its worker. While attempting to use queue mode, both the primary instance and the worker fail to connect to Redis.
To recover, I temporarily disabled the queue and switched back to the default mode, which allowed n8n to start successfully. However, when enabling queue mode again:
- Redis logs indicate that the server is running and ready to accept connections.
- Despite this, the n8n primary instance and the worker cannot connect.
I have verified the Redis host, port, and credentials, and they appear correct. It seems that n8n is not establishing a proper connection to Redis even though it is running.
Could you assist me in identifying why the primary and worker cannot connect to Redis, and how to properly configure queue mode so that both instances can connect?
Thank you,
Jean
4 Replies
2 months ago
Your Worker service is currently in a crashed state. n8n uses ioredis (via BullMQ) for queue mode, and in legacy environments (created before October 16, 2025), the private network is IPv6-only, which causes ioredis to fail DNS resolution since it defaults to IPv4. You can fix this by appending ?family=0 to your REDIS_URL to enable dual-stack lookup, as described in our troubleshooting guide. We also notice you have two Redis services ("Redis" and "Redis-b-_7") in the project, so make sure your n8n Primary and Worker are both pointing to the same Redis instance using the correct internal URL.
Status changed to Awaiting User Response Railway • about 2 months ago
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • about 2 months ago
2 months ago
up
2 months ago
Hey, it looks like you're missing some env vars for queue mode to work correctly, there's this template that uses queue mode and external runners: https://railway.com/deploy/n8n-w-workers-task-runner
You can base yourself from the env vars on that template (or just deploy that template if you're using a fresh n8n instance)
medim
Hey, it looks like you're missing some env vars for queue mode to work correctly, there's this template that uses queue mode and external runners: <https://railway.com/deploy/n8n-w-workers-task-runner> You can base yourself from the env vars on that template (or just deploy that template if you're using a fresh n8n instance)
2 months ago
Hey! I tested using the env vars from that template (queue mode + external runners), but it’s still not working — no jobs are being processed.
What’s strange is that everything was working fine before, and it suddenly stopped without any changes on my side.
Have you seen this happen before or is there anything else I should check (logs, specific vars, runner connection, etc.)?