Hmm, well, I tried that, and I got teh same error, except it was channel 3 this time instead of 2.
I usually just use SSH Tunnel Manager to configure my tunnels, and it always works for email and MySQL, so I figured that I'd try to copy its syntax in to the terminal and see what happened:
/usr/bin/ssh -N -v -p 22 -c 3des
user@host.net -L 8890/localhost/80
And once it connected, an attemp to use a browser on localhost:8890 gave this error in the terminal:
debug1: Connection to port 8890 forwarding to localhost port 80 requested.
debug1: channel 2: new [direct-tcpip]
channel 2: open failed: connect failed: Connection refused
debug1: channel_free: channel 2: direct-tcpip: listening port 8890 for localhost port 80, connect from 127.0.0.1 port 55104, nchannels 3
This exact syntax works fine when used for checking email/using MySQL through, so I am starting to think that it is something specific to Apache, or maybe my web host?
The frustrating part is that I did this previously, a few months ago, and didn't have any problems.....