I have added virtio-win.repo according to this guide. The content of /etc/yum.repo.d/virtio-win.repo is now

name=virtio-win builds roughly matching what was shipped in latest RHEL


The last two [] have similar options as the first (which are not my problem). Now, when I run yum makecache, I get this error

http://fedorapeople.org/groups/virt/virtio-win/repo/stable/repodata/repomd.xml: [Errno 14] problem making ssl connection

I tried running wget http://fedorapeople.org/groups/virt/virtio-win/repo/stable/repodata/repomd.xml manually, but it recommends me to add --no-check-certificate to wget which will solve the problem.

I want to know how can I add that option in the /etc/yum.repo.d/virtio-win.repo?


For one repo you can add the following in the repo configuration:


For all repos, you can add the following to "/etc/yum.conf":

| improve this answer | |
  • 4
    No. it has no effect – mahmood Mar 27 '16 at 17:36
  • 1
    Try also changing back to https for the URL. Be aware that by changing sslverify to off you are foregoing protection against MITM attacks. – davidgo Mar 28 '16 at 2:23
  • Do you guys know if this applies to scenarios where I'm trying to disable SSL for URLs: I'm trying to run yum install <URL>, but disabling sslverify in the yum.conf, doesn't seem to do the trick. – Pablo Fallas Nov 12 '19 at 22:25
  • Worked great for me on CentOS Linux release 7.2.1511. – user674669 Sep 16 at 8:44

On CentOS 7.5, running this worked:

yum-config-manager --save --setopt=<REPONAME>.sslverify=false
| improve this answer | |

On Centos 6, need to update nss

yum update nss

The error "... [Errno 14] problem making ssl connection" no longer occurs

| improve this answer | |
  • 1
    Why? I think nss has nothing to do to that. It is about resolving names (mostly, hostnames). – peterh - Reinstate Monica Apr 24 at 0:12
  • URL : mozilla.org/projects/security/pki/nss Summary : Network Security Services Description : Network Security Services (NSS) is a set of libraries designed to support cross-platform development of security-enabled client and server applications. Applications built with NSS can support SSL v2 and v3, TLS, PKCS #5, PKCS #7, PKCS #11, PKCS #12, S/MIME, X.509 v3 certificates, and other security standards. – Michael Apr 24 at 7:51

The ssl check is there for a reason. It is really dangerous to disable ssl certificate check. I prefer this approach: One of my customer's environment is not set u properly, where the SSL certificate of the proxy server signs every ssl cert of every site. To verify that this is the problem, I run

curl https://www.google.com

It fails, so, get the certificate with one command using openssl-client

openssl s_client -showcerts -servername www.google.com -connect www.google.com:443 > cacert.pem

The big file has the server cert in the middle, copy it, and save it to new file, we will call it mycert.pem. The cert starts with Begin Certificate, and ends with End of Certificate

Let's test it to verify

curl https://www.google.com --cacert mycert.pem

It it works, then the problem is resolved. All what we need to do is to add it to the repository where curl uses as trusted repository. To get the location of the certificates, do the following

strace curl https://www.google.com |& grep open

Lots of output, but right near the end I see: open("/etc/ssl/certs/578d5c04.0", O_RDONLY) = 4

Which is where my certificates are stored. Then simply append the file got earlier.

echo "#Added by me , the client\'s certificate" >> /etc/pki/tls/certs/ca-bundle.crt
cat mycert.pem >> /etc/pki/tls/certs/ca-bundle.crt

Then test again with curl, now without the certificate as an option

curl https://www.google.com

It should get the certificate.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.