3 months ago
Both services are in EU West, same project, same environment (production). postgres.railway.internal:5432 is completely unreachable from the app container.
ProjectID: 977ad5df-e23e-4b18-84ca-7282d6fa4320
WhatI'vetried:
- pg_isready -h postgres.railway.internal -p 5432 → no response
- Added retry loop (10 attempts, 3s apart) — all fail with connection timeout
- Redeploying both services
- Verified both services are in EU West
Deploylogs:
Starting Container
Waiting for database connectivity...
Attempt 1: database not ready, waiting 3s...
...
Attempt 10: database not ready, waiting 3s...
db:prepareerror:
ActiveRecord::ConnectionNotEstablished: connection to server at
"fd12:d5d:6325:1:1000:4a:5828:593", port 5432 failed: Connection timed out
connection to server at "10.168.5.147", port 5432 failed: Connection timed out
DATABASE_URL is set via ${{Postgres.DATABASE_URL}} reference variable. Postgres service shows as online in dashboard.
2 Replies
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
Not sure why that worked when earlier redeploys didn't address this, but it's working now.
Status changed to Awaiting Railway Response Railway • 3 months ago
Status changed to Solved gentschev • 3 months ago