Unable to deploy due to builder 500 error

Questions / Help Build debugging
1

Hello!

This evening I’ve been unable to deploy due to this error:

$ fly deploy
==> Verifying app config
Validating /Users/louis/src/lpil/puck/fly.toml
Platform: machines
✓ Configuration is valid
--> Verified app config
==> Building image
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

I tried deleting the builder but no joy. How do I get around this?

Thanks,
Louis

2

This is an issue on our end and should be fixed shortly. We’ll follow up.

3

Thank you

4

Heads up, this was fixed about 40 minutes ago.

5

I still experience this error. Is there anything I can do on my end?
It happened in both London and Amsterdam region.

6

I am also suffering from this issue. Not sure what the fix is?

7

I got this error a few minutes ago on multiple apps:

Trying again now and…

Looks like it’s working now? add promotification · kentcdodds/kentcdodds.com@b341d65 · GitHub

So hopefully it’s all settled now.

8

Same issue here too! It’s a Node app. Exact error:

image
image1196×282 24.1 KB

9

Same. I recreated the builder but still seeing the WARN Failed to start remote builder heartbeat: server returned a non-200 status code: 500 error.

10

This is a really big pain. The issue was raised in another thread about 7 days ago. Deployment not working is a big problem and surprisingly status page is all green: https://status.flyio.net

This is why we don’t use fly for production deployment.

11

Same issue here for at least 24 hours. In fly apps list the builder shows up with “pending” status. If i delete the builder, a new builder gets created when i try to deploy but it sill has the “pending” status as well.