search

heroku / legacy-cli

Heroku CLI
https://cli.heroku.com
MIT License
1.37k stars 381 forks source link

Heroku client internal error. connect timeout reached #1973

Open goyalshubham13 opened 8 years ago

goyalshubham13 commented 8 years ago

Hi,

I just installed heroku toolbelt and on very first run it failed saying that connect timeout reached. heroku

Please suggest any solution.

Thanks.

goyalshubham13 commented 8 years ago

@dickeyxxx please help with this issue. Let me know what URLs I need to add into my firewall if required.

jdx commented 8 years ago

You need to whitelist *.heroku.com On Tue, Jun 28, 2016 at 3:31 AM Shubham Goyal notifications@github.com wrote:

@dickeyxxx https://github.com/dickeyxxx please help with this issue. Let me know what URLs I need to add into my firewall if required.

— You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub https://github.com/heroku/heroku/issues/1973#issuecomment-229012392, or mute the thread https://github.com/notifications/unsubscribe/AANMfOPb8YybZ22oRs0I-ERn2dqrdjhoks5qQPf3gaJpZM4I_1lv .

goyalshubham13 commented 8 years ago

Thanks @dickeyxxx for your help. Above issue is resolved at my end. Now while creating new app on heroku, I am getting "SELF_SIGNED_CERT_IN_CHAIN: self signed certificate in certificate chain".

I am not able to understand how to go about it. Can you please help with this?

Thanks again.

heroku

jdx commented 8 years ago

this means you have a MITM proxy. I'm not sure how to make it work, you'll probably have to set SSL_CERT_FILE to a certificate for your internet.