SUSE Support

Here When You Need Us

Registration of RedHat 6.2 server fails under SuseManager 3.0: "[Errno 14] Peer cert cannot be verified or peer cert invalid".

This document (7020969) is provided subject to the disclaimer at the end of this document.


SUSE Manager 3


Trying to register a Red Hat 6.2 (or previous RH 6.X versions) server to SUSE Manager 3.0 using salt fails.
Newer Red Hat versions may work though.


The bootstrap script should be edited in order to make sure the following changes are applied:

ORG_GPG entry should be set:


The following lines should be commented out:

#echo "* removing TLS certificate used for bootstrap"
#echo "  (will be re-added via salt state)"


The current bootstrap script has a section to remove the certificate and instead allow it to be salt maintained.
While this is a nice thought, right now it causes the issue described for traditional clients.

In addition, outdated versions of openssl can also cause this SSL certificate error. Unless a newer version of openssl is installed, the problem cannot be bypassed.

More information available in this related TID:


Additional Information

The full output of the registration will be similar to this:

* check for necessary packages being installed...
* client codebase is res-6
package salt is not installed
package salt-minion is not installed
* going to install missing packages...
WARNING: cannot verify XXXXXX’s certificate, issued by “/C=GB/ST=xxx/L=yyy/O=zzz/OU=IT/”:
  Unable to locally verify the issuer’s authority.
2017-05-25 16:57:13 URL: [1509/1509] -> "repomd.xml" [1]
FINISHED --2017-05-25 16:57:13--
Downloaded: 1 files, 1.5K in 0s (2811 GB/s)
 adding client software repository at
Loaded plugins: product-id, refresh-packagekit, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Setting up Install Process [Errno 14] Peer cert cannot be verified or peer cert invalid
Trying other mirror.
It was impossible to connect to the Red Hat 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.


This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7020969
  • Creation Date: 15-Jun-2017
  • Modified Date:16-Jan-2021
    • SUSE Manager

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.