---
name: openshift-ts-ingress-essvc
title: 'Ingress error: ESSVC'
description: Troubleshoot Ingress ESSVC (Exposed Service Set Virtual Cluster) errors.
last-updated: 2026-08-12
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/openshift?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Ingress error: ESSVC
{: #ts-ingress-essvc}
{: troubleshoot}
{: support}

[Virtual Private Cloud]{: tag-vpc} [Classic infrastructure]{: tag-classic-inf} [Satellite]{: tag-satellite}

Troubleshoot Ingress ESSVC (Exposed Service Set Virtual Cluster) errors.
{: shortdesc}


When you check the status of your cluster's Ingress components by running the `ibmcloud oc ingress status-report get` command, you see an error similar to the following example.
{: tsSymptoms}

```sh
The CRN does not match the default secret with the same domain (ESSVC).
```
{: screen}

There are secrets in multiple namespaces for the same domain in your cluster but they reference different IBM Cloud Secrets Manager CRNs.
{: tsCauses}

Ensure all secrets that share the same domain have the same CRN.
{: tsResolve}

1. View all the Ingress secrets for your cluster by running the following command.

    ```sh
    ibmcloud oc ingress secret ls --show-crn
    ```
    {: pre}

1. In the output, ensure that secrets that have the same domain also have the same CRN. For secrets that have a different CRN, update them with the correct CRN by running the following command.
    ```sh
    ibmcloud oc ingress secret update -c <cluster> --name <secret_name> --namespace <secret_namespace> --cert-crn <new_crn>
    ```
    {: pre}

    To find the correct CRN for the Red Hat OpenShift on IBM Cloud managed domains look for the secret in the `openshift-ingress`, or `ibm-cert-store` namespaces.
    {: tip}


1. If the issue persists, contact support. Open a [support case](https://cloud.ibm.com/docs/support?topic=support-using-avatar&format=markdown). In the case details, be sure to include any relevant log files, error messages, or command outputs.