I’ve been having a lot of trouble trying to remove wireguard connections with:
flyctl wireguard remove <org> <id>
I’m getting the following error after a long timeout:
Error Post "https://api.fly.io/graphql": http2: server sent GOAWAY and closed the connection; LastStreamID=<id>, ErrCode=NO_ERROR, debug=""
I have a very long list of wireguard connections (most of them I have no idea how they were created) and I’d like to clean them up.
I’ve been looking around but didn’t find any similar issue so here I am.
Note that it’s the only issue I’m having with flyctl and I don’t have any other network related issue on my machine.
Thanks for your help.
1 Like
A good step would be to have a look at whether you have any network connectivity issues by running fly doctor
Fly doctor runs basic connectivity tests which include pinging the wireguard gateway and testing flyctl agent
I’ve run Fly doctor and everything is fine.
~ ❯ fly doctor
Testing authentication token... PASSED
Testing flyctl agent... PASSED
Testing local Docker instance... PASSED
Pinging WireGuard gateway (give us a sec)... PASSED
I’ve tried to remove the same wireguard connection by using the GraphQL API directly (and not flyctl) and I’m having the same issue with a timeout after ~30 seconds of hanging.
Hi again!
So I just double checked with someone else in the Fly team and the wireguard deletion being slow is something we are aware off and we have some overloaded gateways that we are currently working on optimising deletions. 
1 Like