CondaHTTPError: HTTP 000 CONNECTION FAILED URL Problem on WIndows - anaconda

I have a problem installing python packages, I've already tried to deactivate the SSL verification but I still have the same problem. Any ideas?
enter image description here

Related

Self-Signed Certificate Issue in Windows 7 - Alternative Solution/Hint

I wanted to write out this question here for anyone looking to resolve issues related to SSL certificate. I know that there are a lot of solutions out there (setting any form of sslVerify = false IS NOT the solution people!) for both Windows and Linux-based machines, but none of them works out for me at my company. This has been an on and off issue for the past year, so I'm hoping this might help out someone else.
If you've seen anything similar to the following errors, this might be a good stepping point to a solution:
curl (60) SSL certificate problem: unable to get local issuer certificate
PHP Warning: no valid certs found cafile stream
Composer: The [repo] file could not be downloaded: SSL operation failed with code 1. OpenSSL Error messages: error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed
Then check out Matt Ferderer's post (https://mattferderer.com/fix-git-self-signed-certificate-in-certificate-chain-on-windows) and pay specific attention to the certificate path (image).
For me, there were a good number of posts about how a company's firewall might cause an issue. But the idea that a company's IT department may have other applications that intercept the request you're sending out is something to consider. It was Matt's specific post that was the turning point in my hunt for a solution. I hope it might help you out.
Specifically for me, after viewing the certificate path (described in Matt's post), I noticed that my company's cloud security application was, for some reason, altering the certificates, causing the SSL verification error. The IT department was able to update the settings of the application, and then immediately all of the errors stopped.

Cannot add Meteor package SELF_SIGNED_CERT_IN_CHAIN

I just installed Meteor on OS X 10.10 and was able to create a new project, but I cannot add any packages.
Unable to update package catalog (are you offline?)
If you are using Meteor behind a proxy, set HTTP_PROXY and HTTPS_PROXY environment variables or
see this page for more details:
https://github.com/meteor/meteor/wiki/Using-Meteor-behind-a-proxy
=> Errors while adding packages:
While downloading numtel:mysql#1.0.3...:
error: SELF_SIGNED_CERT_IN_CHAIN
Your package catalog may be out of date.
Please connect to the internet and try again.
First of all, I am behind a corporate firewall and I have the company's CA cert (which all the devices' certificates are signed with) installed in the System and login keychains. Everything else works fine: curl, npm, Chrome, etc. The only time I ever came close to something like this was using Python's pip command, but even that I was able to use the --cert option to point it to the CA cert to bypass the self signed certificate errors it was throwing.
After seeing several other postings from those with the same issue, people have been able to set the HTTP_PROXY and HTTPS_PROXY environment variables with some success. However, this is not a viable option for me, as the company has dozens of these devices and you never connect to the same one twice it seems.
I tried it anyways after finally discovering the correct port to use on one of them, and alas, I am greeted with the following error:
Unable to update package catalog (are you offline?)
If you are using Meteor behind a proxy, set HTTP_PROXY and HTTPS_PROXY environment variables or
see this page for more details:
https://github.com/meteor/meteor/wiki/Using-Meteor-behind-a-proxy
=> Errors while adding packages:
While downloading numtel:mysql#1.0.3...:
error: tunneling socket could not be established, cause=SELF_SIGNED_CERT_IN_CHAIN
Your package catalog may be out of date.
Please connect to the internet and try again.
Notice how this time you see "error: tunneling socket could not be established" in addition to the "SELF_SIGNED_CERT_IN_CHAIN" error.
Short of manually downloading and installing the packages from Atmosphere via Chrome (not a good idea) or trying this outside the firewall (not going to happen unfortunately), I'm not sure what I can do here to make this work. Any ideas? Thanks.
I had lot of issue of self signed certificate with my corporate laptop, I found the magic "NODE_TLS_REJECT_UNAUTHORIZED=0" env variable which allow me to fix any issue.
Warn it is totaly unsafe because there is no more certifcate verification, unfortunetly this is the only thing I could do.
On windows I use the command $env:NODE_TLS_REJECT_UNAUTHORIZED=0 before launching any command with npm.

Having trouble authenticating in Drush with SSL

My Drupal site is hosted at Pantheon (getpantheon.com), I'm using Drush on a Windows 7 x64 machine. I was reading this article on commands using Drush + Terminus (a special Drush extension for Pantheon sites):
https://www.getpantheon.com/blog/five-steps-feeling-drush
I want to be able to use both Drush and Terminus to quickly and efficiently manage my Pantheon Drupal sites.
I installed Terminus fine and was able to issue all the drush-related commands and connect to the server. However, when I got to the part about using 'pauth' to authenticate and use the actual Terminus commands my authentication was successful but then on the part where it's supposed to say 'Success!' :) It says instead:
Dashboard unavailable: SSL certificate problem: unable to get local issuer certificate
Pantheon told me:
This is due to Windows not bundling an Internet-friendly set of Certificate Authority (CA) certs with curl. Check Stack Overflow or the like for a bunch of solutions
Any suggestions on how to proceed? I'm not familiar with cURL at all, so something basic would be great, thanks.
Still new here...figuring this out. I should have done more research :p I found the answer here:
AWS SSL security error : [curl] 60: SSL certificate prob...: unable to get local issuer certificate
Once I'd downloaded the .pem file and saved it in a directory and referenced it from php.ini I was good to go.

xcode - Bot creation failed with error: An SSL error has occurred and a secure connection to the server cannot be made

I am trying to create a bot on my server running 10.9, and I keep getting the following error:
Bot creation failed with error: An SSL error has occurred and a secure
connection to the server cannot be made.
I just updated my SSL cert from the self signed to one from GoDaddy. My https://servername connects fine with a green https.
How do I get it to recognize my certificate?
I never was able to find a solution. I ended up doing a clean install, add my GoDaddy SSL certificates again, and the problem was resolved.

Using Sparkle Updater with download hosted on GitHub

I'm hosting my downloads on GitHub, to save bandwidth on my own server, but when Sparkle updater tries to download updates from GitHub, it fails with error:
Sparkle Error (continued): The operation couldn’t be completed. (NSURLErrorDomain error -1100.)
I figured out that this is due to a certificate mismatch from GitHub, as you can see from this attempt to use wget to download my app from GitHub:
$ wget http://github.com/downloads/chetan51/sidestep/Sidestep%20v0.2.1.zip
--2010-11-21 16:29:26-- http://github.com/downloads/chetan51/sidestep/Sidestep%20v0.2.1.zip
Resolving github.com... 207.97.227.239
Connecting to github.com|207.97.227.239|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://github.com/downloads/chetan51/sidestep/Sidestep%20v0.2.1.zip [following]
--2010-11-21 16:29:27-- https://github.com/downloads/chetan51/sidestep/Sidestep%20v0.2.1.zip
Connecting to github.com|207.97.227.239|:443... connected.
ERROR: certificate common name `*.github.com' doesn't match requested host name `github.com'.
To connect to github.com insecurely, use `--no-check-certificate'.
Unable to establish SSL connection.
Are there any workarounds for this problem?
I suspect you’re not actually getting as far as the certificate error. I had a similar error this weekend, and found that Sparkle (incorrectly) performs %-escaping on attachment URLs. If you change the %20 to a plain space, you’ll probably get a different error indicating the problem you thought you were having.
Not really very helpful, I know.

Resources