By: philpirj

philpirj — Wed, 19 Jan 2011 20:24:40 +0000

ssh -f -N -L 5432:localhost:5432 user@host.com

what’s the point of verbose output when running in background? either set -v either -f

By: robertjmoore

robertjmoore — Tue, 06 Jan 2009 16:55:30 +0000

I grappled with this issue for several hours yesterday and this post helped a lot– thank you. I eventually got it working by matching the “remote address” in the SSH command to the bind-address value in the my.cnf file on the remote server. For most people, the bind-address value is 127.0.0.1, but I have my MySQL server bound to a local network address (192.168.0.x). The correct command for me, therefore, was:

ssh -v -f -N -L 3307:192.168.0.1:3306 user@host.server.com

It seems that the “remote address” in the SSH command is the value used by MySQL to associate the tunneled user with an IP address. Depending on your configuration, MySQL likely either refuses connections from remote IPs or only allows the user you are logging in as to log in from locahost. Since we can’t self-identify as “localhost” (we have to force TCP activity) we need to use an IP address, and that IP address needs to be whatever MySQL identifies as its own. This is the value of bind-address. In many cases, this is going to be 127.0.0.1 (that’s why you see this proposed solution everywhere), but that’s not always the case. Check your bind-address value!

In short, if you’re getting an error in the the “Channel x open failed: connect failed: Connection refused” universe, make sure that the “remote address” in your ssh command matches the bind-address value on your remote machine.

Here are my full notes from yesterday: http://themetricsystem.rjmetrics.com/2009/01/06/php-mysql-and-ssh-tunneling-port-forwarding/

I hope this is helpful to someone.

Comments on: Ssh Port Forwarding and “channel 3: open failed: connect failed: Connection refused”

By: philpirj

By: robertjmoore