Ahh ok, that makes sense. We have had some known intermittent issues with SSH that can cause some weirdness. Just to rule that out, could you try running the command a couple times to see if anything changes?
Ok, that’s not weird, that just means you’re running it from a directory other than the one your fly.toml is in. I don’t know the name of your app, but flyctl -a my-app-name dig txt _apps.internal should work (or give us a more enlightening error).
(We’re working on automating all this troubleshooting stuff right now, so, thanks for helping us guinea-pig it).
Well! We fixed the WireGuard thing. (The most recent flyctl has a single command that resets your WireGuard, so you don’t ever have to touch config.yml, and should soon do so preemptively so this just doesn’t come up at all).
We spotted an issue on our backend with your instance; a cleanup script may have fired in between the time we pulled the container for your db instance and the time your container started up, which may have zapped its network interface. Shaun I think resolved that?