25 days ago
Since the May 19 outage, my API service cannot reach my Postgres database over either private or public networking. Postgres shows green in the dashboard and I've restarted it, but my API crash-loops on startup because the DB connection fails every time.
What I've tried:
Private URL (postgres.railway.internal:5432) → connection timed out
Public URL (centerbeam.proxy.rlwy.net:19856) → "server closed the connection unexpectedly"
Public URL with ?sslmode=require → same "server closed the connection unexpectedly"
Restarted Postgres (went green)
Redeployed API service multiple times
Nothing changed in my code or env vars — was working fine before the outage
API error on every startup:
psycopg2.OperationalError: connection to server at "centerbeam.proxy.rlwy.net" (66.33.22.245), port 19856 failed: server closed the connection unexpectedly
Project ID: 30079ff5-d633-416e-9e10-65c66edc2462
Any help appreciated — my app is completely down for users right now.
1 Replies
25 days ago
Your Postgres service is currently showing as crashed, which is why your API cannot connect to it. This is related to the ongoing service disruption that is now in the recovery phase. We are automatically redeploying workloads we detect as unhealthy, but if your Postgres does not recover on its own, please trigger a fresh redeploy of the Postgres service from the dashboard, and once it is healthy, redeploy the API service as well.
Status changed to Awaiting User Response Railway • 25 days ago
Status changed to Solved shlonkadonk1 • 24 days ago