Previously, there was an issue connecting n8n to Redis over the internal network.

I requested support for connecting to Redis over Railway’s IPv6-only internal network (n8n GitHub Issue #13117), and now it’s fully supported in n8n.

With this update, you won’t be charged for egress usage anymore. Plus, it’s more secure since your Redis instance is no longer exposed to the public network. And of course no more errors.

You can use this template with the fix implemented:

n8n (with workers + internal Redis)

---

The only similar thread I found is archived, so I can’t post there. I’m creating a new one to help others who might face the same issue.