OpenShift 4 Authentication - failed to load SNI cert and key - Cluster API server unavailable after API certificate update

Solution Verified - Updated -

Issue

  • After updating the API and Ingress certificates, the API and Console became unavailable.
  • OpenShift oAuth API server cannot connect to etcd.
  • Authentication pods stuck in CrashLoopBackoff state and shows a message like the following ones:

    failed to load SNI cert and key: tls: found a certificate rather than a key in the PEM for the private key
    
    failed to load SNI cert and key: tls: failed to find any PEM data in certificate input
    

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • Ingress custom certificate

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