builder stopped working, destroyed it, now it won't restart because of API errors?

My last builder didn’t really do anything anymore, it just kept endlessly in the releasing step, also the logs of that builder didn’t show anything.

So I read, I could just destroy it, and there would be another one created if needed. So I destroyed it.

But now only this happens:

==> Verifying app config
--> Verified app config
==> Building image
WARN Failed to start remote builder heartbeat: You hit a Fly API error with request ID: 01GGF244F4D6N7XG160FA1MM01-fra
Error failed to fetch an image or build from source: error connecting to docker: You hit a Fly API error with request ID: 01GGF24MZ3X7HQ48DDTSTRC71J-fra

Is there a way to force a creation or some other trick to do? I desperately need to deploy stuff…

Fly doctor says all green/passed.

I also tried removing the yml files in the ~/.fly directory and reauthenticating, but that didn’t help either.


Alas as of right now “Deployments are broken” :frowning:

Keep an eye on the status page and once the issue is resolved, you should then be able to deploy:

You are right that normally you could delete the builder and a new one would then be created on the next deploy. But that current issue will be preventing that.

1 Like