Executing "yum repolist" on clients fails with "14: curl#51 - "Unable to communicate securely with peer: requested domain name does not match the server's certificate."

Solution Verified - Updated -

Issue

  • Unable to communicate securely with peer: requested domain name does not match the server's certificate. error is observed when executing yum repolist on client systems.

  • Executing yum repolist on clients fails with the below error:

# yum repolist
Loaded plugins: search-disabled-repos
Could not retrieve mirrorlist https://cds01.example.com/pulp/mirror//content/dist/rhel/rhui/server/7/7Server/x86_64/os error was
14: curl#51 - "Unable to communicate securely with peer: requested domain name does not match the server's certificate."
repo id                                                                                  repo name                                                                                       status
rhui-rhel-7-server-rhui-rpms/7Server/x86_64                                              Red Hat Enterprise Linux 7 Server from RHUI (RPMs)                                              0
# yum update
Loaded plugins: search-disabled-repos
Could not retrieve mirrorlist https://cds01.example.com/pulp/mirror//content/dist/rhel/rhui/server/7/7Server/x86_64/os error was
14: curl#51 - "Unable to communicate securely with peer: requested domain name does not match the server's certificate."


 One of the configured repositories failed (Unknown),
 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=<repoid> ...

     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 <repoid>
        or
            subscription-manager repos --disable=<repoid>

     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=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: rhui-rhel-7-server-rhui-rpms/7Server/x86_64

Environment

  • Red Hat Update Infrastructure 3.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content