This is odd… I wonder if it has something to do with the network you are on/using? Your network could be blocking UDP. What happens if you run fly wireguard websockets enable followed by fly agent restart, and then run fly doctor again. Since running fly wireguard reset didn’t seem to work.
Hmm! Looks like the combo of those two commands unwedged things.
I wonder if it was the agent. Since nothing (to my knowledge) has changed about the network, I did a fly wireguard websockets disable & fly agent restart subsequently and things still work.
Will wait to hear back from support, at the very least (if it is the agent) the failure mode could be much better.
Oh that’s good to know that nothing about the network changed! I’m glad those two commands helped fix the issue. Like you said, it might have just been the agent that was the culprit. If anything else arises, definitely give us a holler!