Closed prongs closed 11 years ago
Does it work when you are not behind the proxy?
I don't know. On Feb 24, 2013 7:50 PM, "Rob Reynolds" notifications@github.com wrote:
Does it work when you are not behind the proxy?
— Reply to this email directly or view it on GitHubhttps://github.com/chocolatey/chocolatey/issues/252#issuecomment-14009009.
Try cinst jivkik.dev1 -debug
I have sockss proxy enabled.
You may have an incompatible proxy for nuget.exe. You may want to do some searching around to see what is required to work with socks proxies.
Chocolatey doesn't use IE's proxy settings. It rather uses http_proxy
environment variable. So I used polipo to wrap socks proxy with an http proxy and set the env variable. Worked like a charm!
Cool. It might be a good idea if we add a proxy wiki page.
Sure. Let me know how I can help. On Feb 25, 2013 12:23 AM, "Rob Reynolds" notifications@github.com wrote:
Cool. It might be a good idea if we add a proxy wiki page.
— Reply to this email directly or view it on GitHubhttps://github.com/chocolatey/chocolatey/issues/252#issuecomment-14013502.
If you want to take a stab at creating a page on the wiki with proxy related information, I can review it. If not, I'll create one later.
Cool - thanks!
I saw seeing this error when trying to install command It was fixed if I use http: instead of https: in the URL.
Just for information, after struggling with the exact same error message for a few hours, it turned out that the certificate of the root CA that delivered the chocolatey.org certificate (Go Daddy Root Certificate Authority - G2) was not present int my Windows trusted root CA certificate store (although present in Firefox own's trust store). Importing it manually in the Windows store fixed the issue.
@ggrussenmeyer thank you for the information. I had the same issue on Windows XP. Importing the GoDaddy Class 2 Certification Authority Root Certificate - G2 (https://certs.godaddy.com/repository/gdroot-g2.crt) solved the issue.
I had this problem on a clean windows install. I opened internet explorer. Allowed it to update (presumably updating it's certificates). That solved the problem.
For anyone else that comes across this link - https://github.com/chocolatey/choco/wiki/Proxy-Settings-for-Chocolatey#still-having-trust-issues
Any idea why this might be happening? I am behind a proxy. Could that be causing any problems?