build failed with error of 502 - Railway Central Station

build failed with error of 502

neolee98

PROOP

4 months ago

Build Failed: build daemon returned an error &lt; failed to solve: failed to resolve source metadata for ghcr.io/railwayapp/railpack-frontend:v0.27.0: failed to authorize: failed to fetch oauth token: unexpected status from GET request to https://ghcr.io/token?scope=repository%3Arailwayapp%2Frailpack-frontend%3Apull&amp;service=ghcr.io: 502 Bad Gateway: 


  
... (54634 bytes truncated) &gt;

Closed

10 Replies

4 months ago

Try redeploying the service.

neolee98

PROOP

4 months ago

now it works, wired that 2 services failed with this error twice

neolee98

PROOP

4 months ago

btw do we have a wait for service in railway?

4 months ago

Could've been a one off thing. I was able to pull that image just fine locally.

4 months ago

What do you mean?

neolee98

PROOP

4 months ago

so when auto redeploy from github push, serviceA wait for serviceB before rebuild

neolee98

PROOP

4 months ago

cause serviceA have something need from B during build

4 months ago

I'd suggest building a custom CI/CD pipeline that waits for service B to finish deploying, as well as disabling automatic deployments on service A.

neolee98

PROOP

4 months ago

ah like a CI/CD that use railway api to trigger build?

4 months ago

Yes, via Github Actions.

You can also use Railway's webhooks to call Railway functions to trigger a deployment.

Welcome!

Sign in to your Railway account to join the conversation.