Deploy failing with registry connection refused error

Questions / Help
, ,
1

Hi, I’m unable to deploy my Elixir app today. Getting this error during the image export phase:

Error: failed to fetch an image or build from source: error building: failed to solve: failed to push registry.fly.io/hologram-prod:deployment-01KFRNV351DMM7TX4D03BJ2EJE: failed to do request: Head “https://_api.internal:5000/v2/hologram-prod/blobs/sha256:…”: dial tcp [fdaa::3]:5000: connect: connection refused

What I’ve tried:

  • flyctl agent restart
  • flyctl doctor - all checks pass except local Docker (shows “Nope”)

WireGuard connection appears healthy. This seems like an issue with Fly’s internal registry connection.

Any suggestions?

1 Like
Connection refused during push to registry
2

Same errors happening here over the past hour or so. Nothing showing up on the status pages, so I guess something internal to Fly ran out of disk space or something like that.

1 Like
3

I’ve been having the same problem for more than 24 hours… I thought it was only me because nobody wrote a message / no info on the status page

2 Likes
4

Hm… Does fly deploy --depot=false work for you? (That will give you one of the freebie legacy builders.)

1 Like
5

it does work. Thank you

1 Like
6

Got the same issue here for the past 24 hours. No one wrote about it so thought it was only on my end as well. Works when doing local only (–local-only) or depot false option as mentioned before

2 Likes
7

Thanks @mayailurus, --depot=false worked for me too!

Given that this seems to be affecting multiple users over 24+ hours, and Fly must be seeing these failures in their error reporting pipelines, it would be really helpful to get an official update or status page entry. Is this a known issue that’s being worked on?

1 Like
8

Experiencing this across multiple apps that I have.
An official response or a timeline would help a lot.

9

this issue is limited in arn, I’m building/deploying a fix now.

4 Likes
Connection refused during push to registry