Deploy failing: registry _api.internal:5000 connection refused

All deploy attempts for my app aelu-app fail at the registry push step. Every layer pushes successfully, but the final HEAD verification fails with:

failed to push registry.fly.io/aelu-app: dial tcp [fdaa::3]:5000: connect: connection refused

What I’ve tried:

  • flyctl agent restart

  • WireGuard reset (fly wireguard reset)

  • Multiple builder regions (ewr, ord)

  • --no-cache rebuild

  • fly doctor — all checks pass

Environment:

  • flyctl v0.4.27 (latest)

  • Account in good standing

  • App running fine on v49, just can’t push new versions

This looks identical to the resolved issue in Connection refused during push to registry, which was fixed server-side.

Any help appreciated — blocked on deploying.

Same here, started a few hours ago.

=> ERROR exporting to image

Then, later, a similar connection failure to https://_api.internal:5000.

My workaround for now has been to either build via my local Docker, or use one of the old build servers (found the latter tip on another community post).

fly deploy --local-only

fly deploy -c infra/fly.toml --depot=false

2 Likes

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

I’m in FRA and have the same issue currently since yesterday, please fix

Hi folks, can you change your builder’s region and retry?

it’s in fly./io/dashboard settings → app builders.

1 Like

This should be fixed now!

@roadmr changed it from a US region to FRA in settings as you suggested and it deployed successfully, thank you so much!

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