Unable to use flyctl proxy - timeout probing 'personal'

[popescuionutgabriel]

I’m unable to use flyctl proxy due to a persistent timeout issue when probing the personal organization.

The error I receive is:

Error: tunnel unavailable for organization personal: Error contacting Fly.io API when probing “personal”: timed out (context deadline exceeded)

This used to work fine, but recently stopped functioning.

Things I’ve already tried:

• flyctl wireguard reset
• flyctl wireguard websockets enable
• flyctl agent restart
• Running flyctl from Docker (flyio/flyctl)
• Changing networks (Wi-Fi, VPN, mobile hotspot)
• Disabling IPv6
• Using both flyctl v0.3.127 and v0.3.129
• Running flyctl doctor, which reports:
  Pinging WireGuard gateway… FAILED

Despite all these efforts, the tunnel consistently fails to establish.

Related:

I found this thread describing the exact same issue:

Can't connect to Fly.io tunnel / attach Postgres - timeout probing "personal" from HKG

I’m getting tunnel unavailable: timeout probing "personal" on all Fly commands from Hong Kong, even basic fly proxy and fly ssh. Ping to api.fly.io is fine. Logs below. ping api.fly.io Pinging api.fly.io [77.83.143.220] with 32 bytes of data: Reply from 77.83.143.220: bytes=32 time=4ms TTL=58 Reply from 77.83.143.220: bytes=32 time=4ms TTL=58 Reply from 77.83.143.220: bytes=32 time=4ms TTL=58 Reply from 77.83.143.220: bytes=32 time=4ms TTL=58 Ping statistics for 77.83.143.220: Packets: S…

It looks like this might be a backend issue affecting the personal organization.

Could you please investigate or provide a workaround?

Thanks,
Ionuț

[lillian]

what region is your wireguard peer created in? (you can check in ~/.fly/config.yml)