a month ago
Project ID: cbdb94b4-fb68-4897-86e1-0f6f2d7fee0c
Postgres deployments are failing with DEADLINE_EXCEEDED timeouts when pulling container images. The issue persists across both GHCR and Docker Hub sources.
Failed deployment IDs: eb14079e, 6b49cc25
Error from build logs: "DEADLINE_EXCEEDED: ctrd: failed to pull/unpack image: failed to resolve reference ghcr.io/railwayapp-templates/postgres-ssl:18: failed to do request: dial tcp 140.82.116.33:443: i/o timeout"
Your support bot updated the service config to pull from Docker Hub (postgres:18) but the deployment still attempted the old GHCR image, suggesting a stale cache or pipeline issue.
Current state: Postgres service shows "Online" in the dashboard but has no active deployment running. The public TCP proxy at nozomi.proxy.rlwy.net:54838 returns ECONNRESET on all connections because there is no container to route to.
This is blocking all five services in the project (GMB audit, review monitor, digest, content engine, CRO audit).
Request: Please clear any stale deployment caches and retry the Postgres deployment, or migrate the service to a different region if us-west2 has persistent connectivity issues to container registries.
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
The image pull timeouts were caused by AWS intentionally blocking outbound networking, which has since been resolved. Please redeploy your Postgres service and it should pull the image successfully now. If you're still seeing the stale GHCR image reference after switching to Docker Hub, try creating a fresh deployment rather than retrying the failed one.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 • 28 days ago