`fly ssh console -s` keeps showing old VMs

A few seconds is what I’d expect.

I dug further and, based on your other post, it looks like you’re connecting to one of our “backup” gateways which is using an older, slower-to-replicate, version of our DNS server.

Can you try fly wireguard reset for the same org that app you’re playing with is in? This will get you a new wireguard peer, in a primary region.

I’m going to be investigating how you got a peer on that specific gateway so it doesn’t happen again.

2 Likes