Fly remote builder keeps going offline after a deploy

Hey there!

It’s been a few hours that after we run a remote-only deploy the remote builder goes offline. This means that when we try to run another deploy we get this message

WARN Remote builder did not start in time. Check remote builder logs with `flyctl logs -a fly-builder-billowing-surf-343`

And the only way to make it work again is to delete the existing builder and let the deploy command create a new one. In the last 1h we deleted the remote builder 5 or 6 times.

Are we doing anything wrong? Is there another possible solution?

This sounds like it might have been related to issues with remote builders becoming inaccessible. Please let us know if you’re still running into this moving forward!

Thanks, will do!

1 Like