Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: unable to verify the first certificate #33

Open
tmarrs opened this issue Dec 31, 2015 · 4 comments
Open

Error: unable to verify the first certificate #33

tmarrs opened this issue Dec 31, 2015 · 4 comments

Comments

@tmarrs
Copy link

tmarrs commented Dec 31, 2015

This isn't a defect in apigeetool, but I'm unable to use it behind my corporate firewall.
As long as I'm outside the firewall, apigeetool works properly.

I've tried the following, and no joy:

  • npm config set registry="http://registry.npmjs.org/"
  • npm config set strict-ssl false

Do you have any ideas for helping node get through/past the firewall?

Thanks.

@tmarrs
Copy link
Author

tmarrs commented Dec 31, 2015

I'm wondering if the solution for #6
fixes this too.

@ivan-novakov
Copy link

What exactly goes wrong? And what is exactly the case - are you trying to use apigeetool behind a firewall to connect to the cloud version of Apigee?

@tmarrs
Copy link
Author

tmarrs commented Jan 6, 2016

What exactly goes wrong? I get the following error message:

Error: unable to verify the first certificate

I'm using apigeetool from behind a firewall so that I can deploy my API. I don't know anything about the cloud version of Apigee. All I known is that apigeetool works OK once I get out from behind the firewall.

The solution to #6
doesn't fix the problem.

I''ve also tried to use the -k option to turn off ssl checking, and it still doesn't work - I get other errors.

So, the bottom line is that I need to use apigeetool outside my corporate firewall to make it work.

@stewartmatheson
Copy link

This is similar to the issue I'm having. Apigeetool does not seem to respect the ignore certificate check. In my case the corporate proxy will return a different certificate to what apigeetool is expecting. Setting

npm config set strict-ssl false

should resolve the issue however in apigeetool's case this does not seem to be happening.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants