25 days ago
Deployments for service deorganizedapi (project "deorganized web", production, service id 388e186b-cea9-4554-aa5a-e8f77f60ed4d) have failed twice today at the "Deploy > Create container" step with: The image "production-dpams.railway-registry.com/388e186b-cea9-4554-aa5a-e8f77f60ed4d:34f7f6e5-a12f-4979-8231-ba641f937627" could not be pulled from the registry. If the image is private, check that the registry credentials saved for this service are still valid. The build completes and the image push finishes; the pull then fails. We use Railway's own registry, not a private one, and have never set registry credentials for this service. We received your notice that our account matches the data class involved in the recent incident and are rotating secrets; this deploy was triggered by a variable change. Please check whether the registry credentials Railway holds for this service need to be refreshed, and confirm whether deploys for this account are otherwise unrestricted. The previous deployment is still running, so the service is up but cannot pick up the new variables.
1 Reply
25 days ago
This service has no registry credentials saved, and none are needed: builds push to and pull from our own registry without any credentials on your side. We also see no restrictions on your account, so deploys are not limited.
Both failed deployments today, at 11:58 UTC and 12:24 UTC, built and pushed successfully and then failed when the new image was pulled to start the container. Your current deployment from 12:50 UTC is still building. Your service runs in EU West (Amsterdam), where we have an open incident slowing builds right now, so this build may take longer than usual to finish. Your previous deployment keeps serving traffic until a new one succeeds.
Status changed to Awaiting User Response Railway • 25 days ago
18 days 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 • 18 days ago
