a month ago
Hi, my Postgres service has been failing to deploy for the past few hours. The deployment fails at the "Create container" step with the following error:
ctrd: failed to pull/unpack image: failed to resolve reference "ghcr.io/railwayapp-templates/postgres-ssl:18": failed to do request: Head "https://ghcr.io/v2/railwayapp-templates/postgres-ssl/manifests/18": dial tcp 140.82.116.33:443: i/o timeout
Project ID:94943aff-2e4e-4704-ba7f-48f6a65c7baaService: Postgres (using ghcr.io/railwayapp-templates/postgres-ssl:18) Region: Europe West 4 Error type:DEADLINE_EXCEEDED during Deploy → Create container
It appears Railway's worker nodes cannot reach ghcr.io (140.82.116.33:443) to pull the image. I have tried redeploying multiple times. The database was running fine before this and crashed earlier today (around 08:58 UTC), and now it cannot come back up.
This is blocking my production backend from connecting to the database. Could you please investigate?
Update: I was able to resolve the issue by deploying a new PostgreSQL service in a different region. The original service in Europe West 4 was stuck in a failed deployment loop — Railway's worker nodes in that region could not pull the ghcr.io/railwayapp-templates/postgres-ssl:18 image due to a network timeout (dial tcp 140.82.116.33:443: i/o timeout).
After switching regions, the Postgres service deployed successfully and the backend is now connecting without issues.
It would be worth investigating why ghcr.io is unreachable from Railway's Europe West 4 region, as this caused several hours of downtime with no way to recover the service without manual intervention.
4 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
I am also having the same issue /orchestrator.RouterLegacyService/CreateDeployment DEADLINE_EXCEEDED: ctrd: failed to pull/unpack image: failed to resolve reference "ghcr.io/railwayapp-templates/postgres-ssl:18.3": failed to do request: Head "https://ghcr.io/v2/railwayapp-templates/postgres-ssl/manifests/18.3": dial tcp 140.82.116.33:443: i/o timeout
a month ago
Try redeploying the service. The deployment failed because Railway could not pull the container image from GitHub Container Registry (ghcr.io) due to a network timeout. Multiple consecutive deployments on April 9th hit the same issue, but the service was working successfully before this date.
a month ago
orchestrator.RouterLegacyService/CreateDeployment DEADLINE_EXCEEDED: ctrd: failed to pull/unpack image: failed to resolve reference "docker.io/library/redis:8.2.5-bookworm": failed to do request: Head "https://registry-1.docker.io/v2/library/redis/manifests/8.2.5-bookworm": dial tcp [2600:1f18:2148:bc01:80b2:ae0d:663b:68de]:443: i/o timeout I can pull the same image on my laptop
Should I really buy the service or look for another cloud provider? I just started testing... lucky it is not production yet.
a month ago
I think us-west and some other regions are affected , I moved my apps to us-east and it now works. @gurvemark
Status changed to Solved brody • about 1 month ago
