Fly will be able to help more than me (like if it’s a host/region/API etc issue at their end), but in the meantime this is my go-to list of things that seem to fix various errors. Can’t hurt to try them while you wait:
-
Run
fly version update
to get the latest version of the CLI and try another deploy -
Run
fly doctor
to see if it can diagnose any errors -
Try restarting the agent:
fly agent stop; fly agent start
and try another deploy -
Enable CLI websockets (instead of the default UDP):
fly wireguard websockets enable
and try another deploy -
Try removing the latest wireguard peer:
fly wireguard list
fly wireguard reset
fly wireguard remove
... remove the one that was initially listed from the list command
- If using a remote builder, try destroying that remote builder in case there’s a random fault/disk full etc) with that one:
fly apps list
(to get its random name) then fly destroy builder-name-here
. And try another deploy
If none of those help, I’m out of ideas. But hopefully one of them may.