SSH Disconnected in unhealthy way

1

With a typical SSH connection, if the server dies you can issue an ssh escape sequence to instruct the local connection to quit without waiting for a timeout or resorting to a kill command. Often that looks like this: [enter]~. –

I noticed today that when using fly ssh console to inspect a running vm and the vm is terminated (for example because of a failed deploy) my local console is hosed until I manually open another window and kill the process. Would it be possible to forward ssh escape sequences to whatever ssh process is being wrapped by flyctl?

2

Sure, I’d like to make that work. Can you file a ticket on GitHub - superfly/flyctl: Command line tools for fly.io services about that, so we can prioritize it? Thanks for the suggestion.

3

Oh great, done. Thanks