There’s a lot more information on this topic as well: flyctl ssh console: Waiting for host... and nothing happens - #31 by nickolay.loshkarev
The first debugging steps are:
- Are you on a corporate network or a VPN? Your corporate network provider may be blocking WireGuard connectivity; your VPN almost definitely is. Have you tried connecting with VPNs disabled?
- Do you have a peer set up to connect to? You can check with with
fly wg list
to see your list of peers. - Are your instances currently accessible to you? If you follow the steps outlined in Private Networking are you able to get a successful connection into the VPN using your favourite WireGuard client?
- Do you see a valid instance address when you do
dig aaaa <app>.internal @fdaa:<xxx>
(where@fdaa:xxx
is your DNS server address from yourwireguard.conf
)