On Fri, Jul 5, 2013 at 3:00 AM, Brice Vandeputte <[email protected]> wrote: > i didn't know the hostname(s) used in this case > so by adding some ruby trace i show that (gems excon) socket.rb attempt to > open a socket on an amazon instance (port 443) > > do you know what (socks) ssh configuration should i set to make heroku bash > working ? is it as simple as heroku push ?
Unfortunately for you, it uses a completely different mechanism that relies on port 5000. Your case is documented here: https://devcenter.heroku.com/articles/one-off-dynos#timeout-awaiting-process. The general facility is called 'rendezvous'. There's a (closed) issue about this here https://github.com/heroku/heroku/issues/407. So...how to make SOCKS work...hmm Well, the problem is the rendezvous endpoint is dynamic and hard to configure beforehand, AFAIK. If you see this code in the CLI: https://github.com/heroku/heroku/blob/68a0734e19e42427d90e38141492ef14360aa308/lib/heroku/command/run.rb#L109-L120 The client connects to the Heroku api, asks for an attached process, and in the response includes its rendezvous URL. The second step is to connect to that URL for rendezvous. So, to make it work with SOCKS, I surmise one would have to deftly map a new SOCKS route right between these two steps. Not easy, but I think that's probably what would have to happen right now. -- -- You received this message because you are subscribed to the Google Groups "Heroku" group. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups "Heroku Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
