Hey there! We've found the following might help you get unblocked faster:

• 🧵 Postgres Database is not ready - n8n
• 🧵 n8n crash
• 🧵 n8n crash ENOTFOUND Redis
• 🧵 502 Bad Gateway Error

If you find the answer from one of these, please let us know by solving the thread!

Hey, can you please elaborate more on the issue or provide the error message/logs? If this is related to Postgres being on version 17 while it was on 16, then please try changing the source to ghcr.io/railwayapp-templates/postgres-ssl:16, as this is how another user solved this particular issue.

I'm not sure what I'm doing, so I'll describe as best as I can. I host n8n on Railway. When I auto launched it, it added 3 other workers, Redis, Worker and Postgres. Today I went to update n8n and as a procedure I also update any of the other workers (what I am calling the 3 other boxes). I update them by clicking on the n8n or the worker, clicking deployments, clicking the 3 dots on the right of the last deployment, and clicking redeploy. It's always run and deployed the latest update. Today, Postgres crashed during the update. I tried to restart, redeply and tried rolling an old deployment back. Now I see n8n has also crashed, I'm not sure if this is related.

I tried your solution above, and also tried the above replacing :16 with :17. Here is the last log.

I think you’re gonna need to redeploy the Postgres service for the change to take effect.

I've tried that multiple times, unless I'm doing it wrong.

Maybe. Just to be sure, after changing the image to the right one, you clicked on the three dots, and then hit "Redeploy"?

@shxkm I did that, but based on your note, I looked for other ways and noticed a warning that there was a Deploy Box above the group. So I went back to :16 anf that worked!

Solution: Update the image to ghcr.io/railwayapp-templates/postgres-ssl:16, save, then deploy from the main screen. Let's hope the next time it doesn't crash. 🙂. I