I’m not aware of any widespread issue that could be causing this, but it worked before; I’ll do my best to help unbreak it!
I checked really quickly to rule out it being just now broken everywhere-- what region are your instances in?
If nothing has changed on your end, configuration-wise, the following steps might help us find a good place to start investigating:
- you can try connecting over TCP, instead, with
fly wireguard websockets enable - you can try changing out wireguard peers with
fly wireguard reset,fly wireguard remove, andfly wireguard create
For additional context on the above flyctl commands, the troubleshooting in this thread might help too:
If you’re stuck please feel free to let us know! It would help us check on our end if we knew whether this is app-specific, and if so, what the output of fly status is for it.