fly deploy has been failing for over 12 hours when pushing to registry.fly.io

, ,
1

Error:
failed to push registry.fly.io/sifto-api:deployment-...: failed to do request: Head "https://_api.internal:5000/v2/sifto-api/blobs/sha256:... ?ns=registry.fly.io": dial tcp [fdaa::3]:5000: connect: connection refused

What I already tried:

  • fly deploy --depot=false

  • fly deploy --depot=false --recreate-builder

  • fly deploy --local-only

--local-only avoids the remote builder issue, but I still hit the registry push failure on normal deploys. Since this has persisted for 12+ hours, could someone check whether my builder/registry path is stuck in a bad region or if there is an ongoing internal registry issue for this org/app?

3

@support this is still an issue. Can’t push to the image repository. At 12 hours down time.

4

Hi, for now the recommended workaround is to move your builder to another region. Can you tell me which region it’s in first? Then in Sign in to Your Account · Fly go to “settings”, pick a new region under “app builders” and hit “reset builder”. Next build should go through.

We’re looking at this in any case, so we’ll get it fixed soon for everyone!

  • Daniel
5

Thanks for your help. I changed the builder region to NRT, reset the builder, and the deployment worked successfully. It looks like the issue is resolved now.

6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.