I'm honestly not sure how common it is for people to move ssh off the default port. If you're using key auth and not passwords there's probably not much reason to do so. As for your cap file, try putting "git://" on the front of the repo URL. I bet cap's falling back to ssh there since you don't specify the protocol.
--tek On Thu, Oct 9, 2008 at 2:43 PM, justus ohlhaver <[EMAIL PROTECTED]> wrote: > Hi Tek, thanks for looking into this. > http://gist.github.com/15880 > Is this what you needed? > > BTW. this script is working fine when I use port 22 for my prod server. I > can't imagine that this would be a cap bug since the cap , non-standard port > combination should be pretty common or not? > > Thanks for your help . > Justus > > > > > On Thu, Oct 9, 2008 at 10:29 PM, GitHub Support <[EMAIL PROTECTED]>wrote: > >> Sounds to me like a bug in cap, it's using the same port for your >> connection to the server as the server's connection to the repo. YOu might >> want to poke the cap list on this one: >> http://groups.google.com/group/capistrano >> Could you toss up your cap script on gist for us to look at? There may be >> something else you're overlooking. >> >> --tek >> >> >> On Thu, Oct 9, 2008 at 2:22 PM, justus ohlhaver <[EMAIL PROTECTED]>wrote: >> >>> No I am NOT trying to access github on that port. That's exactly the >>> problem. My production server is on that port (1234) and I would like to >>> continue to connect to github as usual. >>> But for some reason capistrano thinks I want to connect to github on that >>> port (1234) when I try top specify the port for my prod server. >>> >>> How do I tell capistrano that my prod server is on port 1234 but that the >>> repo port should NOT be changed? >>> >>> Thanks for your help, >>> Justus >>> >>> >>> >>> On Thu, Oct 9, 2008 at 10:09 PM, Dustin <[EMAIL PROTECTED]> wrote: >>> >>>> >>>> >>>> Confused. Why are you trying to access github on port 1234? >>>> >>>> On Oct 9, 7:41 am, ohlhaver <[EMAIL PROTECTED]> wrote: >>>> > Hello, >>>> > >>>> > What do I need to change in the deploy.rb or elsewhere in order to use >>>> > a non-default port number? >>>> > >>>> > Everything is working fine when I use the standard port 22 on my >>>> > server. I'm able to deploy my code with capistrano and github. >>>> > >>>> > Now I changed my port number to something higher -say - 1234. >>>> > >>>> > I also updated the deploy.rb with this line: >>>> > >>>> > 'ssh_options[:port] = 1234' >>>> > >>>> > This works if I do a single command such as cap deploy:cleanup >>>> > >>>> > BUT when I try to deploy updated code via GitHub I now get the >>>> > following error: >>>> > >>>> > 'ssh: connect to host github.com port 1234: Connection refused' >>>> > >>>> > When I remove the 'ssh_options[:port] = 1234' line from deploy.rb this >>>> > error doesn't happen but instead: >>>> > >>>> > 'Capistrano::ConnectionError, connection failed for: xx.xx.x.xx >>>> > (Errno::ECONNREFUSED: Connection refused - connect(2))' >>>> > >>>> > So does anybody know how to solve this? >>>> > What do I need to change in the deploy.rb or elsewhere in order to use >>>> > a non-default port number? >>>> > >>>> > Thanks a lot for any help! >>>> > >>>> > Justus >>>> >>>> >>> >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/github?hl=en -~----------~----~----~----~------~----~------~--~---
