On 10/16/07, Kenneth Kalmer <[EMAIL PROTECTED]> wrote: > On 10/15/07, Jamis Buck <[EMAIL PROTECTED]> wrote: > > It's not the authentication that is failing, it is the lower-level > > attempt to open a forwarded port to the remote host. > > > > I wonder if your gateway's SSH implementation is somehow not > > configured to allow port forwarding. That, or maybe the SSH server on > > the remote host is not running on port 22? Or maybe there is a > > permission's issue on the gateway? I've never encountered this error > > before, so I'm just shooting in the dark, but maybe it'll give you > > something more to investigate. > > I'm getting the same issue here, but my remote servers' SSH ports run > on 222. I tried setting "ssh_options[:port] = 222" and appending > ":222" to the server names without luck. Maybe cap doesn't respect the > ssh_options when setting up the gateway? Having a look now... > > Cap version 2.0.0
Ignore the above please! A simple typo in one of the roles where I forgot to add the port to the hostname. Works perfectly as advertised... Best -- Kenneth Kalmer [EMAIL PROTECTED] [EMAIL PROTECTED] stats http://fah-web.stanford.edu/cgi-bin/main.py?qtype=userpage&username=kenneth%2Ekalmer --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
