Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Can you be more specific about "SSH hanging"?</p> <p>It sounds like your ssh <strong>client</strong> hangs after losing the connection and you are unable to do anything in the terminal. To get around this, you can use the ssh escape character (default: ‘~’) to begin an escape sequence, and use the the '.' to terminate the connection.</p> <p>You can get a list of other ssh escape sequences using ~?, here's the one for OpenSSH SSH client:</p> <pre><code>Supported escape sequences: ~. - terminate connection ~B - send a BREAK to the remote system ~C - open a command line ~R - Request rekey (SSH protocol 2 only) ~^Z - suspend ssh ~# - list forwarded connections ~&amp; - background ssh (when waiting for connections to terminate) ~? - this message ~~ - send the escape character by typing it twice (Note that escapes are only recognized immediately after newline.) </code></pre> <p>If typing ~. does not work, it could be that you have the escape character disabled, in which case you can put</p> <pre><code>EscapeChar ~ </code></pre> <p>inside <em>~/.ssh/config</em> or <em>/etc/ssh_config</em></p> <p>Even when the escape character is disabled, you can simply pull up another Terminal window and type</p> <pre><code>killall ssh </code></pre> <p>to end all running ssh processes, allowing you to connect out again.</p> <p>Restarting the SSH daemon would not correct this problem because sshd allows other clients to connect in to your machine, and does not affect your ssh clients connecting out to some other machine.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload