How to use a custom SSL/TLS certificate

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.

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.

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

sudo hg apply-config

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.