> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.13/troubleshoot-and-reference/troubleshoot/renew-internal-cluster-certificates.md).

# Renew internal cluster certificates

Manage and maintain internal Kubernetes cluster certificates for Cortex XSOAR On-prem.

In Cortex XSOAR, internal Kubernetes control-plane PKI certificates are used for secure communication between cluster components. These internal certificates have a default validity period of 365 days and are distinct from the external HTTPS certificates managed via the `set_ssl_certificate` script.

{% hint style="warning" %}

### Important

To ensure these certificates are rotated and to avoid service disruptions, perform at least one upgrade per year via the textual UI (TUI). The upgrade process automatically executes the necessary renewal mechanisms for the internal cluster PKI.

If your tenant remains on a static release for more than 12 months without an upgrade, the internal certificates will expire, leading to a complete service outage upon the next host reboot.

Downloading upgrade artifacts via the TUI without executing the upgrade does not renew the internal certificates. You must actively run the upgrade process to rotate the certificates and ensure system stability.
{% endhint %}

#### Troubleshoot internal certificate expiration

After a host reboot or power failure, you can tell if the certificates have expired if you see the following:

| Issue                        | Description                                                                                                                                                                                |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Connection refused           | Attempting to access the WebUI (port 443) returns a `Connection Refused` error, even if the VM is confirmed as **Running** in the hypervisor.                                              |
| Blank cluster administration | The **Cluster Administration** page in the TUI appears empty and fails to list any nodes or node status.                                                                                   |
| Missing VM networking        | The hypervisor (for example, VMware or vSphere) fails to display the VM IP address or DNS information because the underlying kubelet cannot register the node with the expired API server. |
| Failed API server            | Backend Kubernetes services fail to accept connections on the internal API port (6443) .                                                                                                   |

If you encounter these issues, contact Palo Alto Networks Support for a manual certificate recovery session. To prevent future issues, ensure you maintain a regular upgrade schedule.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.13/troubleshoot-and-reference/troubleshoot/renew-internal-cluster-certificates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
