3 months ago
Classic error during at deploy time:
Error: P1001: Can't reach database server at postgres.railway.internal:5432
Please make sure your database server is running at postgres.railway.internal:5432.
So I moved the bunx prisma migrate deploy to pre-deploy but still, during Build time:
Error: P1001: Can't reach database server at postgres.railway.internal:5432
Please make sure your database server is running at postgres.railway.internal:5432.
5 Replies
3 months ago
It might also be linked to: https://blog.railway.com/p/incident-report-february-11-2026
But then I need some admin to fix it.
3 months ago
Hello,
We had an incident earlier that caused some running workloads to be unexpectedly terminated while the status in the UI didn't properly update. This has since been resolved, but in some cases, you may need to redeploy your services.
You can find the post-mortem for the incident here: https://blog.railway.com/p/incident-report-february-11-2026
Our deepest apologies for the inconvenience this has caused.
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
Thanks, all good now.
Good communication, but honestly this is freaking me out that production DB could crash in the middle of the night for 8h..
Status changed to Awaiting Railway Response Railway • 3 months ago
Status changed to Solved marcados • 3 months ago
3 months ago
Update: fail.
The pre-deploy command is spinning indefinitely without error log.
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
Third manual re-deploy worked. Very concerning issues.
Status changed to Solved marcados • 3 months ago