Since 2026-09-27 15:09 UTC, every deployment of one service fails at the pre-deploy step with: "The image "production-dpsjc-b.railway-registry.com/0e293b8d-e89e-417b-adf3-41ebe0662c85: " could not be pulled from the registry. If the image is private, check that the registry credentials saved for this service are still valid." - Project: CER (6d5b18be-612a-48b5-8736-d34ae1a8c7f8), environment Development, service cer-app (0e293b8d-e89e-417b-adf3-41ebe0662c85). The build is from a GitHub repo with Railpack; no custom image or registry credentials are configured. - The build and image publish succeed; the failure is when the pre-deploy step pulls the image. - The last success was at 13:39 UTC the same day. Redeploying that exact successful deployment now fails the same way, so it isn't the code. - The project's event log shows no configuration or variable changes between the last success and the first failure. - Another service in the same project, which has no pre-deploy command, deploys normally. - Six failed deployments so far, e.g. 23df04da-16b7-4352-ab2d-1d9e12f3f2bf and fa5524c2-3263-40e5-8ae9-0c0a7dcaedc2. Could you check the registry or pull credentials for this service?

Pre-deploy fails: image could not be pulled from the registry, even when redeploying a past success

porusdaruvala

HOBBYOP

6 hours ago

Since 2026-09-27 15:09 UTC, every deployment of one service fails at the pre-deploy step with:

"The image "production-dpsjc-b.railway-registry.com/0e293b8d-e89e-417b-adf3-41ebe0662c85:" could not be pulled from the registry. If the image is private, check that the registry credentials saved for this service are still valid."

Project: CER (6d5b18be-612a-48b5-8736-d34ae1a8c7f8), environment Development, service cer-app (0e293b8d-e89e-417b-adf3-41ebe0662c85). The build is from a GitHub repo with Railpack; no custom image or registry credentials are configured.
The build and image publish succeed; the failure is when the pre-deploy step pulls the image.
The last success was at 13:39 UTC the same day. Redeploying that exact successful deployment now fails the same way, so it isn't the code.
The project's event log shows no configuration or variable changes between the last success and the first failure.
Another service in the same project, which has no pre-deploy command, deploys normally.
Six failed deployments so far, e.g. 23df04da-16b7-4352-ab2d-1d9e12f3f2bf and fa5524c2-3263-40e5-8ae9-0c0a7dcaedc2.

Could you check the registry or pull credentials for this service?

$10 Bounty

2 Replies

Railway

BOT

6 hours ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • about 6 hours ago

0x5b62656e5d

MODERATOR

6 hours ago

Try adding the variable NO_CACHE=1 and redeploy. Also try selecting the service, press Cmd/Ctrl + K, and deploy latest commit.

porusdaruvala

HOBBYOP

4 hours ago

Thanks. I tried both, and both fail the same way.

Set NO_CACHE=1 on the service and redeployed. The build ran fully uncached (every package reinstalled), then PRE_DEPLOY_COMMAND failed with the same "could not be pulled from the registry" error. Deployment 433c80b5-f6dd-4a7c-b870-cb4b716825be.
Deployed the latest commit (the Cmd/Ctrl + K action). Same result: build and image publish succeed, then the same pull error at PRE_DEPLOY_COMMAND. Deployment 42b826f8-a81f-4b23-bdb2-472366248d11.

I've removed NO_CACHE again. Since even a redeploy of the last successful deployment fails, this looks like the registry or pull path for this one service. Could someone on the Railway team look at it?

Welcome!