To close a frozen SSH connection, just type in the following order…

Enter
~
.


This bugs the hell out of me daily, so thanks John!

Basically, you can use a handy short memorable alias for a long and possible complicated one in terminal by doing the following.

Open terminal, go to root ( cd ~/ ) and see if a file under the name .bash_login exists… if not create it.

Open this file in vim, enter your aliases like so…
alias dev1=’ssh username@serverhostname.com’
alias dev2=’ssh username@anotherserverhostname.com’

So now each time I enter dev1 into the terminal, I will be ssh’ing into my server, or dev2 to ssh into another one without having to recall the hostname and such… sweet.

You can add as many as you like for any command.

HANDY TIP: Enter the alias !=history and now you each time you type ! plus some text, the terminal will  figure out which command to call based on your terminal history and the text you entered.

HANDY TIP #2: Use CTRL+R to search through any of your previous commands, you can insert any part of the command… super!
Thanks Donncha

Once you have your new private OpenSSH key, copy it to your Mac.

Open terminal, and go to your root… usually does this automatically, but type cd ~/ just in case.

Create a .ssh directory if it does not already exist and copy the private key in here.

You may need to check that the key has the right permissions, type chmod -R g0-rx ~/.ssh

Enter your ssh command, ssh username@serverhostname.com and hit enter, you should get now have a SSH tunnel to your server.

HANDY TIP: use the vvv flag to debug the ssh command  (looks odd but thats 3 v’s by the way!).

So type ssh username@serverhostname.com -vvv to receive a load of debug info that can be really useful in determining where you are screwing up.

Also I found this guide useful.

So firstly, I need to set up PuTTY, a free and open source terminal emulator that will allow me to SSH into my remote web server.

Download PuTTY here.

Once downloaded, I need to generate a public/private key to authenticate the SSH connection from my machine to the web server.

Use another tool – PuTTYGen to generate the keys for you.

Download PuTTYGen here.

Here’s a pretty straightforward guide that I cannot be arsed to repeat on how to create the key. One difference for me was we use DSA encryption.

HANDY TIP: If you wish to use this key on a Mac (like I did once it was repaired) so that you can connect from either machine (windows or mac), then do the following.

Once you have your key created you need to export the key as an OpenSSL key and save it for later.

On with the guide…

By now you should have your keys, your public one should be up on your server, your sacred private key should be in on your local machine.

You now open PuTTY to connect to your server.

Enter you host name / ip address to your server. So something like…

username@dev.serverhostname.com

Now to add your private key to the equation. On your right you will see an SSH option, click it to reveal more options… select the ‘Auth’ option.

Now use the Browse button to select your newly created private key.

Now return to the initial screen, Session (where you entered your development web server’s hostname )… give the session a name and save… then Load and BOOM, you should have a new terminal window to your server.

Okay, now the port forwarding. In my case, remote access is not permitted to our development database. However you can connect to it from your development web server.

So, if I can use port forwarding to make a MySql client connect to the development database through the web server then I can access the database locally… which is handy.

The following guide helped me.

Now I know, what the heck… that’s a better guide than this one, but bare with me. I tried to follow that guide and I got stuck. Some of you may not have, but I think there is something in guides like this that do not nail home.

Umm something like, “What IP address and what port do I use and where do I put it!“…

I guess I got confused over source and destination fields.

To safe you the bother, your Source address is 127.0.0.1  (or localhost) and your source can use any Port you wish, like 3006 in the example given in the guide above.

The Destination address is the address you normally use to connect to your database from your web server ( probably in some config file ). Looks something like  dev.db.servername.com:3000, or 201.002.11.33:3000…

You insert this hostname/port into the destination field below (where the confusing 127.0.0.1:3006 is now), and whatever port you wish to use as part of your source address, in our case we’ll stick with 3006

Then open your MySql client and insert your source address details, 127.0.0.1 and port 3006, enter your Username/password and click the connect button… and all going well you have local access to your remote database server through a secure SSH Tunnel… sweet!