---
title: How to use a custom SSL/TLS certificate
description: This article explains how you can set a custom SSL/TLS certificate to replace the default self-signed certificate that ships with Hyperglance.
---

[Skip to content](https://support.hyperglance.com/knowledge/how-to-set-a-custom-https-ssl/tls-certificate#main-content)

English

Show submenu for translations

[More support](https://support.hyperglance.com/knowledge/kb-tickets/new?hsLang=en)

![](https://support.hyperglance.com/hs-fs/hubfs/hyperglance.png?width=100&height=75&name=hyperglance.png)

Open main navigation

Close main navigation

- English
  
  Show submenu for translations
- [More support](https://support.hyperglance.com/knowledge/kb-tickets/new)
- [Contact Us](https://www.hyperglance.com/contact/)

[Contact Us](https://www.hyperglance.com/contact/)

 How can we help you?

- There are no suggestions because the search field is empty.

1. [Hyperglance Support](https://support.hyperglance.com/knowledge?hsLang=en)
2. [Setup & Configuration](https://support.hyperglance.com/knowledge/setup-configuration?hsLang=en)
3. [General](https://support.hyperglance.com/knowledge/setup-configuration?hsLang=en#general)

# How to use a custom SSL/TLS certificate

## This article explains how you can set a custom SSL/TLS certificate to replace the default self-signed certificate that ships with Hyperglance.

The self-signed certificate that ships with Hyperglance may cause browsers to complain that the certificate is not trusted by a Certificate-Authority. To remedy this you can set your own trusted certificate.

If you are running on our legacy Docker-based architecture, see [legacy guide](https://support.hyperglance.com/knowledge/how-to-set-a-custom-https-ssl/tls-certificate-legacydocker?hsLang=en).

 

1\) SSH into Hyperglance

2\) Edit the values.yaml associated with your Hyperglance deployment. A convenient alias is provided. Feel free to replace `nano` with your editor of choice.

`nano $hg_values`

(NOTE: `$hg_values` is an alias for this file: `/var/lib/data/hyperglance_helm_charts/values.yaml` )

3\) Search for, and replace the values for `httpdSSl.certificate` and `httpdSSL.key`

```
httpdSSL:  existingSecretName:   certificate: |    -----BEGIN CERTIFICATE-----    PASTE YOUR KEY HERE AND BE CAREFUL TO USE CORRECT INDENTATION    -----END CERTIFICATE-----  key: |    -----BEGIN PRIVATE KEY-----    PASTE YOUR KEY HERE AND BE CAREFUL TO USE CORRECT INDENTATION    -----END PRIVATE KEY-----
```

Alternatively, you may choose to use an existing secret instead of relying on the values.yaml. This can be accomplished by following the documentation on our [helm chart repo](https://github.com/hyperglance/helm-chart?tab=readme-ov-file#using-existing-secrets).

5\) Redeploy the helm chart for the changes to take effect:

```
sudo hg apply-config
```

- [Before You Start](https://support.hyperglance.com/knowledge/before-you-start?hsLang=en#main-content)

    - [Kubernetes](https://support.hyperglance.com/knowledge/before-you-start?hsLang=en#kubernetes)
    - [GCP](https://support.hyperglance.com/knowledge/before-you-start?hsLang=en#gcp)
    - [AWS](https://support.hyperglance.com/knowledge/before-you-start?hsLang=en#aws)
    - [Azure](https://support.hyperglance.com/knowledge/before-you-start?hsLang=en#azure)
- [Using Hyperglance](https://support.hyperglance.com/knowledge/using-hyperglance?hsLang=en#main-content)

    - [Automations](https://support.hyperglance.com/knowledge/using-hyperglance?hsLang=en#automations)
    - [Inventory & Diagrams](https://support.hyperglance.com/knowledge/using-hyperglance?hsLang=en#inventory-diagrams)
    - [Rules](https://support.hyperglance.com/knowledge/using-hyperglance?hsLang=en#rules)
    - [Cost Management](https://support.hyperglance.com/knowledge/using-hyperglance?hsLang=en#cost-management)
    - [Dashboards](https://support.hyperglance.com/knowledge/using-hyperglance?hsLang=en#dashboards)
    - [Security & Compliance](https://support.hyperglance.com/knowledge/using-hyperglance?hsLang=en#security-compliance)
- [Setup & Configuration](https://support.hyperglance.com/knowledge/setup-configuration?hsLang=en#main-content)

    - [Updating & Migrating](https://support.hyperglance.com/knowledge/setup-configuration?hsLang=en#updating-migrating)
    - [General](https://support.hyperglance.com/knowledge/setup-configuration?hsLang=en#general)
    - [RBAC & Users](https://support.hyperglance.com/knowledge/setup-configuration?hsLang=en#rbac-users)
    - [STIGS & FIPS](https://support.hyperglance.com/knowledge/setup-configuration?hsLang=en#stigs-fips)
    - [AWS](https://support.hyperglance.com/knowledge/setup-configuration?hsLang=en#aws)
    - [Azure](https://support.hyperglance.com/knowledge/setup-configuration?hsLang=en#azure)
    - [Kubernetes](https://support.hyperglance.com/knowledge/setup-configuration?hsLang=en#kubernetes)
    - [GCP](https://support.hyperglance.com/knowledge/setup-configuration?hsLang=en#gcp)
    - [API](https://support.hyperglance.com/knowledge/setup-configuration?hsLang=en#api)
    - [Legacy Docker-based deployments](https://support.hyperglance.com/knowledge/setup-configuration?hsLang=en#legacy-docker-based-deployments)
    - [AI](https://support.hyperglance.com/knowledge/setup-configuration?hsLang=en#ai)

[![Chill listening crop-3](https://support.hyperglance.com/hs-fs/hubfs/hyperglance.png?width=134&height=24&name=hyperglance.png "Chill listening crop-3")](https://www.hyperglance.com/)

2880 Zanker Road, Suite 203, San Jose, CA 95134

<https://www.linkedin.com/company/hyperglance/>

Copyright © 2025 Hyperglance. All rights reserved.