3 months ago
I am having issues with my postgress deployment and database. I wasn't able to connect for 10 minutes straight (kept getting ""We are unable to connect to the database via SSH. The database container is starting up or transitioning. Please wait a moment and try again.") so I tried restart and redeploy.
Now my new deplyment instance is stucked in "Creating container" phase for the past 30 minutes and I still can't connect to the active one for the same reason above.
My volume might be corrupted, because I tried mounting it on a healthy postgress instance and got the same 30 minutes wait on deployment
7 Replies
3 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
3 months ago
This is a known issue at the moment: https://station.railway.com/community/the-great-build-speedup-of-2025-5f38c59b
Are you still experiencing issues with Postgres?
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
Yes, everything related to postgress seems quite unstable. Also deployments are taking unusually long, my service took 15 minutes and when I changed a shared variable it got stucked on "Applying one change"
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
I just changed a variable of my service and it's stucked in this "will deploy" and apply one change state for the past 1 h.
Attachments
3 months ago
Thats definitely not ideal and not what we're going for with user experience here!
I will note that we do have a project we're working on soon which will be fixing up a bunch of slow parts from the "push code" -> "get it live" process.
All appears to be well now but if you do see this again try removing the stuck deploy and starting it again. If that doesnt fix, feel free to raise again!
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
Still unstable. I don't understand why connection strings given by Railway copied and pasted into terminal / env are throwing "failed: FATAL: password authentication failed for user "postgres""
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
Well that's a bit odd. Do you have a link to the database having this issue? The current database looks normal.
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 3 months ago