Hi, everything was working fine yesterday but suddenly I can not use flyctl proxy command, Im getting the error Tunnel unavailable for organization xxx: tunnel unavailable.
Flyctl version: flyctl v0.3.216 linux/amd64 Commit: 8cc3435567be3ea0cbca0bba4e9427dc2cd4a7f2 BuildDate: 2025-11-14T16:34:22Z
The build date leads me to think that its a bug in the new version?
@Mine07 The flyctl 0.3.214 release had an issue with wireguard, though that should be fixed in the 0.3.216 release.
You might need to reset your wireguard connection for the fix to take up. Can you try resetting it with fly wg reset followed by fly agent restart? Do you see the proxy commands working after that?
If not, if you could share the output of fly doctor that should help.
Did both and still the same error, heres the output from fly doctor
Testing authentication token… PASSED
Testing flyctl agent… PASSED
Testing local Docker instance… PASSED
Pinging WireGuard gateway (give us a sec)… PASSED
Testing WireGuard DNS… PASSED
Testing WireGuard Flaps… PASSED
App specific checks for xxxx:
Checking that app has ip addresses allocated… Nope
No ip addresses assigned to this app. If the app is not intended to receive traffic, this is fine.
Otherwise, it likely means that the services configuration is not correctly setup to receive http, tls, tcp, or udp traffic.
No public ipv4 or ipv6 ip addresses allocated to app xxx
Build checks for xxx:
Checking docker context size (this may take little bit)… PASSED (32 B)
I dont know if a configuration or something is missing from my app? I mean its a database and as far as I remember it had no ip addresses allocated and was working fine till today.
Thanks. We’re taking a look but in the meantime, can you try downgrading to 0.2.213 using the install script (curl -L https://fly.io/install.sh | sh -s 0.3.213) and then trying those again?
You might want to disable autoupdate with fly settings autoupdate disable to avoid it trying to update past that