> For the complete documentation index, see [llms.txt](https://docs.weka.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.weka.io/4.3/operation-guide/security/tls-certificate-management/manage-the-tls-certificate-using-the-gui.md).

# Manage the TLS certificate using the GUI

Upon system installation, the cluster's TLS certificate is activated with an auto-generated self-signed certificate, enabling access to the GUI, CLI, and API via HTTPS. If you have a custom TLS certificate, you may replace the auto-generated self-signed certificate with your own. Additionally, you can download the existing TLS certificate for integration with other applications that require communication with the cluster, such as Local WEKA Home.

![TLS Certificate](/files/Tj26TWLcPz3k2ip3J1D3)

**Procedure**

1. From the menu, select **Configure > Cluster Settings**.
2. From the left pane, select **Security**.
3. In the TLS Certificate section, select **Set TLS certificate**.
4. In the Set Custom TLS Certificate dialog, do one of the following:
   * Select **Upload TLS certificate files**, and upload the TLS certificate and private key files.
   * Select **Paste the custom certificate content**, and paste the content of the TLS certificate and private key.

![Set Custom TLS Certificate](/files/5N0VcGn2zkzZIvJQh1v5)

5. To download the existing TLS certificate, select **Download TLS certificate**. \
    In the dialog, set a name for the certificate and select **Download**.

![Download a TLS certificate](/files/nkvVclzVinIGj3xYdBHp)

**Related topic**

[Deploy Local WEKA Home v3.0 or higher](/4.3/monitor-the-weka-cluster/the-wekaio-support-cloud/local-weka-home-deployment.md)

[Deploy Local WEKA Home v2.x](/4.3/monitor-the-weka-cluster/the-wekaio-support-cloud/deploy-local-weka-home-v2.x.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.weka.io/4.3/operation-guide/security/tls-certificate-management/manage-the-tls-certificate-using-the-gui.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.