More often than not when I leave an SSH session running for a period of time without input the session will hang. By this I mean I can type whatever I want and nothing will echo back. It can be very annoying, especially since I would have to open up a new terminal on my machine, SSH to the server I was on and kill that process. There is, however, another trick that I just discovered and can save a lot of extra work. Lets look at the documentation real quick though for SSH to understand how this trick will work: By default a pseudo-terminal is always allocated to SSH sessions but if you wish to enforce this pass the "-t" switch when running SSH. Above is a list of all the special codes you can use. The one we're interested in is the "~." command. If you notice above the list of codes there must be a newline before using the code. Luckily all this means is you hit Enter then the code you want to use (~. in our case). So what you would do is this: Hit the Enter key Hold shift and hit ` (so you send the ~ key) Hit . (period) Your session will terminate and you'll be brought back to your regular shell prompt on your local machine.