Ingress router pods failing - "unable to load SSL private key from PEM file " in RHOCP 4

Solution Verified - Updated -

Issue

  • After updating the custom certs for the Ingresscontroller the router pods are failing with an error.
E0824 15:26:51.504105       1 limiter.go:165] error reloading router: exit status 1
[ALERT] 235/152651 (18) : parsing [/var/lib/haproxy/conf/haproxy.config:117] : 'bind 127.0.0.1:10444' : unable to load SSL private key from PEM file 
  • Extra characters appended while creating the chain certificate file for replacing the default ingress certificate.
-----BEGIN CERTIFICATE-----^M
MIIFZjCCBE6gAwIBAgIDAyYqMA0GCSqGSIb3DQEBCwUAMIGwMQswCQYDVQQGEwJV^M
UzENMAsGA1UECAwET2hpbzERMA8GA1UEBwwIQ29sdW1idXMxIDAeBgNVBAoMF0Ft^M
...
...
9zaJZvUY0+nwjnwNF6MfXr4kK+NEsJWZ8HPWZqV/IFQymaEnLxVUVGx7XGABnqYn^M
jYKGVLyHZJzHuprEopVtI40IOgGmwXDnjgYBkL0Ne+gYp3FVbsV/MGOYZ4MoKPll^M
HYywuGy+UA1GZsCtazVCbBKNsDUb2t358FQrWYUds7Japq6KkPSV/gVj^M
-----END CERTIFICATE-----

Environment

  • Red Hat OpenShift Container Platform 4.6 or later.

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