Er … 
I’m afraid I don’t know what to suggest. My hack/fix is to delete the remote builder and hope its replacement works … but you’ve tried that and it hasn’t helped here. Hmm. I don’t know Fly’s innards. If the issue only started yesterday I wonder if there is some temporary issue with Fly in that region? Hopefully someone will be able to look up that API request ID to debug.
I have successfully deploy my app using fly deploy --local-only, this will use local docker to build the image instead of remote builder. If you want to try it, make sure you have docker running in your machine.
Ah, that’s a good idea to bypass the remote builder step entirely @pyk .
Perhaps there is an issue with sin. Only other people have mentioned issues with that region too e.g
Hey thanks for the suggestion!
But the issue has been resolved and I’m able to deploy using the fly CLI…
Will surely try your solution next time if issues with remote-builder persist!
Hello again,it seems sin region is down again!
This saved me today!
(Used the --local-only flag)
Thanks @greg. I had the same issue in AMS today. I destroyed the builder with fly destroy BUILDER_APP_NAME and ran fly deploy --remote-only and that worked for me 
Having issues with fly machines… I’ve tried @PeterUllrich’s solution. Doesn’t seem to work for machines…
"errors": [
{
"message": "You hit a Fly API error with request ID: 01GRDXG0NEXE08M8XC0G3ZCZV7-ams",
"extensions": {
"code": "SERVER_ERROR",
"fly_request_id": "01GRDXG0NEXE08M8XC0G3ZCZV7-ams"
}
}
],
"data": {}
}
DEBUG result image:<nil> error:error connecting to docker: You hit a Fly API error with request ID: 01GRDXG0NEXE08M8XC0G3ZCZV7-ams
DEBUG --> POST https://api.fly.io/graphql```
```Testing authentication token... PASSED
Testing flyctl agent... PASSED
Testing local Docker instance... PASSED
Pinging WireGuard gateway (give us a sec)... PASSED
App specific checks for <app>:
Checking that app has ip addresses allocated... PASSED
Checking A record for <app>... PASSED
Oops, something went wrong! Could you try that again?```Deleting the builder machine does not help:
$ /root/.fly/bin/flyctl deploy
==> Verifying app config
--> Verified app config
==> Building image
WARN Failed to start remote builder heartbeat: You hit a Fly API error with request ID: 01GRDYGMW93AXWZ81HDNBDA0B2-iad
Error failed to fetch an image or build from source: error connecting to docker: You hit a Fly API error with request ID: 01GRDYGQSSXJS0772T6CCDZR4P-iad
To be honest this is unacceptable. Fly is doing around for a few years already, but stability issues like this still popping up out of nowhere. I’ve used to recommend fly in my community but I can not anymore. While I’m capable of figuring out and troubleshooting issues like this, a lot of folks isn’t.
I know that in a large scale those errors are rare, but I’ve never had issues with Heroku, for example. Issues like this make experience very bad and made me think to move out.
Random builder failures, capacity issues in regions, random DNS failures, things like these… I know you guys doing a very good job on developing your own software to orchestrate all the things, and I really appreciate your work, but when I need to deploy my stuff and something is not working makes me super disappointed.
Could you try @pyk 's solution?(Docker must be installed & configured for this to work)
I have successfully deploy my app using
fly deploy --local-only, this will use local docker to build the image instead of remote builder. If you want to try it, make sure you have docker running in your machine.
so after destroying the builder 100 times, now am able to update my machines…
i tried pushing manually to fly registry and update the image through cli, but it’s a pain in the ass since am on osx and fly won’t accept arm64 builds. had to set up docker buildx.
anyway, the whole thing was a waste of time. this is just disappointing even though it worked after a few hours.
Could you try @pyk 's solution?(Docker must be installed & configured for this to work)
Yeah, it didn’t worked at the time, but now it is; thank you. But remote build & deploy still didn’t, and frankly, it’s unacceptable.
I have the same error in a GitHub Actions deploy. You can see the full run here:
WARN Failed to start remote builder heartbeat: You hit a Fly API error with request ID: 01GREZ8KPGWD4KYFE9DBB5KJA3-iad
Error failed to fetch an image or build from source: error connecting to docker: You hit a Fly API error with request ID: 01GREZ8MY6R7Y3QME9KYAPT6NH-iad
Looks like sin region is down today too!
Hey, can you paste that with request ID: ..... here. Text is generally more accessible and easier to search.
==> Verifying app config
Validating /Volumes/workspace/SWorkspace/onewheel-blog/fly.toml
Platform: machines
✓ Configuration is valid
→ Verified app config
==> Building image
WARN Failed to start remote builder heartbeat: You hit a Fly API error with request ID: 01H47VMMPPTDA1MYNNCSDSHASC-nrt
Error: failed to fetch an image or build from source: error connecting to docker: You hit a Fly API error with request ID: 01H47VMNR6WEZ1QQCQG4C26ATX-nrt
I still have this issue. I just want to subscript the pro plan. But look like I will change my mind.
There is something definitely fishy going on with your builder app. I’ll look into it, but you can delete your fly-builder-* app, which should unblock you.
I’m having a similar issue:
WARN Failed to start remote builder heartbeat: You hit a Fly API error with request ID: 01H52KTFBKNEBT02VP3JWACADB-yyz
Error: failed to fetch an image or build from source: error connecting to docker: You hit a Fly API error with request ID: 01H52KTGMHBVK02KWPGKRZG2K7-yyz
Destroyed the builder multiple times and tried redeploying but get same error over and over again.
Hey, do you happen to have docker running locally? If so you might be able to deploy with --local-only so the builder isn’t blocking you.