a month ago
Production-down on US West, multiple consecutive deploys failing at CREATE_CONTAINER with persistent infrastructure errors per Railway's own diagnose. Community thread: https://station.railway.com/questions/container-creation-failing-after-us-west-136e3c67. Service trial running for beta vendors who are actively impacted. Any chance of a manual nudge from the infra team?
4 Replies
Here's what fixed it for me after hours of failed deploys:
The root cause turned out to be that Railway's internal networking (postgres.railway.internal) was broken by the outage — but the error message ("password authentication failed") was misleading. The password was fine; the private network just couldn't route to Postgres.
Fix: Switch DATABASE_URL in your app service's Variables from the internal URL to the public/external URL.
- Go to your Postgres service → Variables tab
- Copy the value of
DATABASE_PUBLIC_URL(looks likepostgresql://postgres:...@.proxy.rlwy.net:/railway) - Go to your app service → Variables → edit
DATABASE_URL→ paste the public URL - Save — service restarts automatically
The public URL routes through Railway's TCP proxy instead of the broken private network. Your app will connect fine and your data is untouched.
Note: this will incur small egress fees (Railway warns about this with a yellow icon) but it's negligible — fractions of a cent per connection. You can switch back to the internal URL once Railway confirms private networking is fully restored in US West.