Since the metrics incident yesterday, I’m seeing lots of disconnects whenever I try to use flyctl now.
I got lucky with a fly deploy in the morning which worked fine. Since then, nothing is really working. I managed to reinstall flyctl after one of these connection issues had left me with a non-existing flyctl.exe due to a broken auto update.
Now that my flyctl.exe is in place again, no matter which command I use, I keep getting connection errors like this:
fly status
Error: failed to get app: Post "https://api.fly.io/graphql": read tcp [2a10:bcc4:2001:6a5c:4571:2a51:8036:3f18]:51348->[2a09:8280:1:f28:246e:d6a:949:dbbf]:443: wsarecv: An existing connection was forcibly closed by the remote host.
Sometimes I get this warning first
WARN failed querying for new release: Get "https://api.fly.io/app/flyctl_releases/windows/amd64/latest": read tcp [2a10:bcc4:2001:6a5c:4571:2a51:8036:3f18]:51323->[2a09:8280:1:f28:246e:d6a:949:dbbf]:443: wsarecv: An existing connection was forcibly closed by the remote host.
I’m basically dead in the water and can’t do any new deployments. I managed to reauthenticate using fly auth login after a lot of attempts but that didn’t change anything.
My version is
fly.exe v0.2.17 windows/amd64 Commit: 3a51f42f15355928eb7f51c620f599328cadfa55 BuildDate: 2024-03-11T21:27:36Z