a month ago
My Postgres instance is stuck in:
Database Connection
Attempting to connect to the database...
I restarted -> didn't work
Deployed -> It taking more than 15 minutes and then failed
Was working yesterday
Thanks
7 Replies
a month ago
Your Postgres deployment failed with a transient infrastructure error during container creation, and the current redeploy is stuck at the same stage. Your volume and data are intact. Try using the command palette (Cmd/Ctrl+K) and selecting "Redeploy source image" to force a fresh image pull, as a normal redeploy reuses the cached image and may hit the same issue.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
Your Postgres deployment failed with a transient infrastructure error during container creation, and the current redeploy is stuck at the same stage. Your volume and data are intact. Try using the command palette (Cmd/Ctrl+K) and selecting "Redeploy source image" to force a fresh image pull, as a normal redeploy reuses the cached image and may hit the same issue.
a month ago
I did the "Redeploy source image", but the deployment is stuck in "Creating containers" step
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
The redeployment is still stuck at container creation with no logs produced, confirming this is a transient infrastructure-side issue. Your volume and data are safe. We recommend cancelling any queued deployments and waiting rather than retrying, as additional redeploys can compound the queue. We are actively working on resolving these issues.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
The redeployment is still stuck at container creation with no logs produced, confirming this is a transient infrastructure-side issue. Your volume and data are safe. We recommend cancelling any queued deployments and waiting rather than retrying, as additional redeploys can compound the queue. We are actively working on resolving these issues.
a month ago
Cancelled queued deployments, still,not working
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Your Postgres deployment is still failing at container creation, which is an infrastructure-side issue that we're actively working to resolve. Your volume and data remain intact. Once the underlying issue is cleared, a fresh deploy should succeed normally.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
Your Postgres deployment is still failing at container creation, which is an infrastructure-side issue that we're actively working to resolve. Your volume and data remain intact. Once the underlying issue is cleared, a fresh deploy should succeed normally.
a month ago
When Will I be notified of this fix? how much time will take?
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Thanks for working through the steps. To answer your timing question directly: I don't have a firm ETA yet — this is a known platform-side issue from today's US West networking disruption affecting multiple services, and the container-creation/volume side is being recovered on our end. Your data volume is intact and safe.
In the meantime, if your Postgres container is still serving, you can get connected again now: in your Postgres service → Variables, copy DATABASE_PUBLIC_URL, then set your app's DATABASE_URL to that value instead of the internal hostname. That routes through the TCP proxy and bypasses the broken private network (small egress cost; switch back once private networking is restored). If the Postgres container itself is failing to start, that's the platform-recovery case and a workaround won't apply — your volume stays safe and we'll follow up here.
Status changed to Awaiting User Response Railway • about 1 month ago
25 days 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 • 25 days ago