6 months ago
My n8n instance on Railway has been running fine until today when I updated the Primary container with the latest version of n8n.
After Redeploy, both the Primary and Worker containers cannot connect to the Redis server.
2 Replies
6 months ago
Hey there! We've found the following might help you get unblocked faster:
- 🧵 n8n crash ENOTFOUND Redis
- 🧵 N8N crash after deploy
- 🧵 Postgres Volume Migration Failed After Railway Metal Rollback – Production n8n Instance Down
If you find the answer from one of these, please let us know by solving the thread!
Railway
Hey there! We've found the following might help you get unblocked faster: - [🧵 n8n crash ENOTFOUND Redis](https://station.railway.com/questions/n8n-crash-enotfound-redis-785768fa) - [🧵 N8N crash after deploy](https://station.railway.com/questions/n8n-crash-after-deploy-1d9f0917) - [🧵 Postgres Volume Migration Failed After Railway Metal Rollback – Production n8n Instance Down](https://station.railway.com/questions/postgres-volume-migration-failed-after-r-b4a611ed) If you find the answer from one of these, please let us know by solving the thread!
6 months ago
I have already reviewed these threads and they do not have a solution for my problem.