+1 for tunnlr. It also works with non-fb apps: I'm using it to talk to the salesforce.com and mechanical turk apis.
On Tue, Jan 26, 2010 at 7:02 AM, Amiruddin Nagri <[email protected]>wrote: > Not sure about your problem, but I am also trying to build a FB app. > > I am using tunnlr.com services, they have config provided if you are > making a FB app. > Have a look, hope it helps. > > Regards, > Amiruddin Nagri, > Bangalore, 560008, KA > India > > Y! IM : [email protected] > GTalk : [email protected] > > > > > On Tue, Jan 26, 2010 at 1:22 PM, Abhishek Manocha < > [email protected]> wrote: > >> I am sure somebody here must have experienced problem of the sorts I >> am facing. >> I am trying to get the ssh tunnel going on heroku for fwding facebook >> requests to my heroku app to my local dev env. >> >> I have tried different sorts of combination on ssh command prompt (I >> am using openSSH on windows XP) >> And also openSSH is looking into ssh_config file (instead of >> sshd_config) mentioned at few places. >> >> These combos I have tried without success of any. >> >> .............................................................................................................................................................. >> ssh -v -p 22 -nNT4 -o "ServerAliveInterval 0" -R *:80:localhost:3003 >> [email protected]@evntize.heroku.com >> >> ssh -v -p 22 -nNT4 -o "ServerAliveInterval 0" -R evntize.heroku.com: >> 80:localhost:3003 [email protected]@evntize.heroku.com >> >> ssh -v -p 22 -nNT4 -o "ServerAliveInterval 0" -R *:80/localhost/3003 >> [email protected]@evntize.heroku.com >> >> ssh -v -p 22 -nNT4 -o "ServerAliveInterval 0" -R 80:localhost:3003 >> [email protected]@evntize.heroku.com >> >> ssh -v -p 22 -nNT4 -o "ServerAliveInterval 0" -R 80:localhost:3003 >> evntize.heroku.com >> >> ............................................................................................................................................................... >> >> All fail with messgae like >> >> >> >> .................................................................................................................................................................. >> OpenSSH_3.8.1p1, OpenSSL 0.9.7d 17 Mar 2004 >> debug1: Reading configuration data /etc/ssh_config >> debug1: Connecting to evntize.heroku.com [174.129.212.2] port 22. >> debug1: Connection established. >> debug1: read PEM private key done: type DSA >> debug1: read PEM private key done: type RSA >> debug1: identity file /home/Abhishek Manocha/.ssh/id_rsa type 1 >> debug1: identity file /home/Abhishek Manocha/.ssh/id2_rsa type 1 >> debug1: identity file /home/Abhishek Manocha/.ssh/id4_rsa type 1 >> debug1: Remote protocol version 2.0, remote software version >> OpenSSH_5.1p1 Debia >> n-5 >> debug1: match: OpenSSH_5.1p1 Debian-5 pat OpenSSH* >> debug1: Enabling compatibility mode for protocol 2.0 >> debug1: Local version string SSH-2.0-OpenSSH_3.8.1p1 >> debug1: SSH2_MSG_KEXINIT sent >> debug1: SSH2_MSG_KEXINIT received >> debug1: kex: server->client aes128-cbc hmac-md5 none >> debug1: kex: client->server aes128-cbc hmac-md5 none >> debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent >> debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP >> debug1: SSH2_MSG_KEX_DH_GEX_INIT sent >> debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY >> debug1: Host 'evntize.heroku.com' is known and matches the RSA host >> key. >> debug1: Found key in /home/Abhishek Manocha/.ssh/known_hosts:2 >> debug1: ssh_rsa_verify: signature correct >> debug1: SSH2_MSG_NEWKEYS sent >> debug1: expecting SSH2_MSG_NEWKEYS >> debug1: SSH2_MSG_NEWKEYS received >> debug1: SSH2_MSG_SERVICE_REQUEST sent >> debug1: SSH2_MSG_SERVICE_ACCEPT received >> debug1: Authentications that can continue: publickey >> debug1: Next authentication method: publickey >> debug1: Offering public key: /home/Abhishek Manocha/.ssh/id_rsa >> debug1: Authentications that can continue: publickey >> debug1: Offering public key: /home/Abhishek Manocha/.ssh/id2_rsa >> debug1: Authentications that can continue: publickey >> debug1: Offering public key: /home/Abhishek Manocha/.ssh/id4_rsa >> debug1: Authentications that can continue: publickey >> debug1: No more authentication methods to try. >> Permission denied (publickey). >> >> .................................................................................................................................................................. >> >> >> >> >> I am almost sure i m missing some config step here, but which one I >> dont know. >> I have already added keys to heroku and heroku keys give me this back >> === 6 keys for [email protected] >> ssh-rsa AAAAB3NzaC...+BLgbBEw== Abhishek >> ssh-rsa AAAAB3NzaC...+zqjIJEwM= >> ssh-rsa AAAAB3NzaC...+BLgbBEw== Abhishek >> ssh-rsa AAAAB3NzaC...+BLgbBEw== [email protected] >> ssh-rsa AAAAB3NzaC...I15R0Pnws= Abhishek >> ssh-rsa AAAAB3NzaC...7eUioiO50= Abhishek >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Heroku" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<heroku%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/heroku?hl=en. >> >> > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<heroku%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > -- You received this message because you are subscribed to the Google Groups "Heroku" 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/heroku?hl=en.
