Kibana-proxy shows "certificate signed by unknown authority" when using custom ingress certificate

Solution Verified - Updated -

Issue

After having replaced the default ingress certificate of the cluster, I get the following message when logging in at the kibana console: 500 Internal Error.
The pods of openshift-logging project seem to be in working order, but I cannot access to kibana.

Environment

OCP 4.2 and 4.4

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