YUM command failed with [Errno 14] curl#60 - “SSL certificate : unable to get local issuer certificate” in REDHAT

8,026

This is directly from the Centos wiki listed in the error message

  1. Validate the system can see things on the internet.

    ping google.com

  2. This issue can also occur due to corruption of the local machine cache, try to clear cache on system:

    yum clean all

    rm -rf /var/cache/yum/*

  3. If you have a proxy server, validate it is configured properly in /etc/yum.conf. Here is an example (your names, passwords, and port numbers will obviously be different).

    proxy=http://mystuff.mydomain.com:1234
    proxy_username=proxy-user
    proxy_password=proxy-password

  4. Temporarily comment out the mirror= line in the the .repo file, then:

    yum clean all; yum makecache

Share:
8,026
harsha rachith
Author by

harsha rachith

Updated on September 18, 2022

Comments

  • harsha rachith
    harsha rachith over 1 year

    i'm getting an error [Errno 14] curl#60 - "SSL certificate problem: unable to get local issuer certificate" when i use yum command to install or update any package.

    Ex:

    yum install curl
    

    then it gives and output like this

    [root@dtetestmaster svradmin]# yum install curl
    Loaded plugins: fastestmirror, product-id, search-disabled-repos, subscription-manager
    
    This system is not registered with an entitlement server. You can use subscription-manager to register.
    
    DialogRHSCLRepo                                                                                                          | 3.4 kB  00:00:00     
    DialogRepo                                                                                                               | 3.5 kB  00:00:00     
    https://download.docker.com/linux/centos/7/x86_64/stable/repodata/repomd.xml: [Errno 14] curl#60 - "SSL certificate problem: unable to get local issuer certificate"
    Trying other mirror.
    It was impossible to connect to the CentOS servers.
    This could mean a connectivity issue in your environment, such as the requirement to configure a proxy,
    or a transparent proxy that tampers with TLS security, or an incorrect system clock.
    You can try to solve this issue by using the instructions on https://wiki.centos.org/yum-errors
    If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
    
    
    
     One of the configured repositories failed (Docker CE Stable - x86_64),
     and yum doesn't have enough cached data to continue. At this point the only
     safe thing yum can do is fail. There are a few ways to work "fix" this:
    
         1. Contact the upstream for the repository and get them to fix the problem.
    
         2. Reconfigure the baseurl/etc. for the repository, to point to a working
            upstream. This is most often useful if you are using a newer
            distribution release than is supported by the repository (and the
            packages for the previous distribution release still work).
    
         3. Run the command with the repository temporarily disabled
                yum --disablerepo=docker-ce-stable ...
    
         4. Disable the repository permanently, so yum won't use it by default. Yum
            will then just ignore the repository until you permanently enable it
            again or use --enablerepo for temporary usage:
    
                yum-config-manager --disable docker-ce-stable
            or
                subscription-manager repos --disable=docker-ce-stable
    
         5. Configure the failing repository to be skipped, if it is unavailable.
            Note that yum will try to contact the repo. when it runs most commands,
            so will have to try and fail each time (and thus. yum will be be much
            slower). If it is a very temporary problem though, this is often a nice
            compromise:
    
                yum-config-manager --save --setopt=docker-ce-stable.skip_if_unavailable=true
    
    failure: repodata/repomd.xml from docker-ce-stable: [Errno 256] No more mirrors to try.
    https://download.docker.com/linux/centos/7/x86_64/stable/repodata/repomd.xml: [Errno 14] curl#60 - "SSL certificate problem: unable to get local issuer certificate"
    

    Please help to resolve this error, Thanks!

    • Michael Hampton
      Michael Hampton over 3 years
      Exactly what Linux distribution is this? How was it installed?
    • Gordster
      Gordster over 3 years
      Have you tried to solve this issue by using the instructions on https://wiki.centos.org/yum-errors? What version of Centos7 are you running? Use cat /etc/system-release and place this information in your question above?
  • harsha rachith
    harsha rachith over 3 years
    that's not a solution. it stop only getting from docker. it fails all https links
  • harsha rachith
    harsha rachith over 3 years
    packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/…: [Errno 14] curl#60 - "SSL certificate problem: unable to get local issuer certificate" Trying other mirror. It was impossible to connect to the CentOS servers.
  • harsha rachith
    harsha rachith over 3 years
    regarding your update: are there any solutions to fix those certificate errors?
  • kofemann
    kofemann over 3 years
    run openssl s_client -connect download.docker.com:443 --showcerts and check the result
  • harsha rachith
    harsha rachith over 3 years
    [root@dtetestmaster svradmin]# openssl s_client -connect download.docker.com:443 CONNECTED(00000003) 139890983536528:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:s23_clnt.c:794: --- no peer certificate available --- No client certificate CA names sent --- SSL handshake has read 7 bytes and written 289 bytes --- New, (NONE), Cipher is (NONE) Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE No ALPN negotiated SSL-Session: Protocol : TLSv1.2 Cipher : 0000 Session-ID: Session-ID-ctx: *cannot add all output here
  • Gordster
    Gordster over 3 years
    @kofemann in Centos7 it's -showcerts rather than two dashes like in Ubuntu. What is very strange is that Centos7 handles SSL certificates very differently than Centos8 and newer versions of Ubuntu. We just went through this with one of our self hosted repos. It turns out we were missing a key usage "Key Encipherment" in a cert that was recently installed. We would not experience issues in the latest OS versions but anything Centos7 and below would fail.