Does anybody experienced the same issue? Probably duplicate of https://community.fly.io/t/failed-to-start-remote-builder-heartbeat-server-returned-a-non-200-status-code-500/15860, but this happened last year and should be resolved already.
WARN Failed to start remote builder heartbeat: server returned a non-200 status code: 500
Error: failed to fetch an image or build from source: error connecting to docker: server returned a non-200 status code: 500
Hi !
Had the same issue here : Failed to start remote builder heartbeat - CDG
Try to deploy --local-only like I did, it might work !
Tried already and successfully deployed. Will not work for a CI workflow though (my Github Actions still can’t work 
).
@jonathan-lewerissa can you upgrade to the latest version of flyctl and try again?
Happening to us as well, on v0.2.15. I emailed 2 days ago with the logs but no response yet…
Honestly I’ve run in to numerous issues trying to use the fly builder…destroying the builder and redeploying almost always was the fix. Running concurrent builds in a CI pipeline really makes the builder struggle for some reason. If anyone is curious and uses GitHub Actions, I’ve switched to --local-only and use BuildJet’s builders. Their lowest tier is about twice as fast as the fly builders and cheaper than the GitHub builders. FWIW I’ve only used it for about a month but I haven’t had any partial deployment failures like I did with the Fly Builder.
Retrying on v0.2.17. Destroyed the builder and redeploying, but still having the same problem.
Hi @jonathan-lewerissa - can you please try one more time?
I tweaked a thing on my side and I’d be interested in knowing if it helped.
Retried, redeployed the builder and it works! Will mark this as completed. Thank you 
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.