a month ago
Hello Railway Support,
I am experiencing a persistent deployment failure with my production service, MAGNA-Unificado.
The build fails during the Railpack image-building process with the following error:
failed to authorize: failed to fetch auth token: unexpected status from GET request to https://auth.docker.io/token: 504 Gateway Timeout
Previously, the same operation also returned a 500 Internal Server Error.
I have retried the deployment multiple times, but the error persists.
The failure occurs before npm install or npm run build starts. My previous successful deployment is still active, and I need to deploy an updated version without affecting my production data or the persistent volume mounted at /data.
Could you please investigate the builder's connection to Docker Hub and advise whether the build can be retried using a different builder, registry mirror, or cache?
Thank you for your assistance.
3 Replies
a month ago
We're sorry for the trouble. We're aware of an issue causing builds and deploys to fail when they pull images from Docker Hub, and we're working on it. Builds that reach Docker Hub can error out before your install and build steps run, which matches the failure you're seeing. You can follow updates here: Builds and deploys failing to pull images from Docker Hub.
A failed build doesn't replace your current deployment, so your previous successful deployment keeps serving, and your volume at /data stays attached to it.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Quick update: this is caused by an ongoing Docker Hub incident that's making image pulls fail. You can follow their updates here: https://www.dockerstatus.com/incidents/01M4HA1E00AH6NXA276AW0CK2V
Once it's resolved, redeploying should go through. We'll let you know here when pulls are working again.
a month ago
Docker Hub's incident is resolved, so the auth errors should be gone. Redeploying MAGNA-Unificado should work. A failed build never touches the running deployment, so your volume at /data was not affected.
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 • about 1 month ago