Github Action and local deploy have stopped working today "failed to fetch an image or build from source: error building: timed out connecting to machine: failed to list workers"

Deploying via the fly.io Github Actions integration is broken for me as of today.

Yesterday deploys were working fine. I have not changed any fly.io config since then.

What is happening? Can I file a bug somewhere for live incidents?

Run flyctl deploy --remote-only
==> Verifying app config
Validating /home/runner/work/<my_app>/<my_app>/fly.toml
✓ Configuration is valid
--> Verified app config
==> Building image
Waiting for depot builder...

==> Building image
Waiting for depot builder...

Error: failed to fetch an image or build from source: error building: timed out connecting to machine: failed to list workers: Unavailable: connection error: desc = "transport: authentication handshake failed: EOF"
Error: Process completed with exit code 1.

Update: my app is also stalling on the same step when i run fly deploy on my local machine

Hi… fly deploy --depot=false is another workaround.

This will give you one of the free legacy builders…

(At least for now.)

1 Like

Awesome I will try that, thank you!

(After the current Network outage is over :grinning: Maybe the fix is going out today…)

Ok using --depot=false does solve the issue for now.

I’d rather not be using a legacy product indefinitely. (Also I’m curious if there is any functional difference I should be aware of between legacy and current versions?)

I know the team is likely dealing with the fallout from the outage today but will there be an investigation/fix on this issue as well?

1 Like

˙sɯǝlqoɹd ɐɹɟuı ƃuıʌɐɥ ʇodǝp s,ʇI ˙puǝ s,ʎlℲ uo ʇ,usı ǝnssı ǝɥʇ ʎlǝʇɐunʇɹoɟu∩

2 Likes

Following up here @Team . This is still an issue for me :confused:

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.