# hzcms install example

It is necessary to immediately run the updater to apply fixes that have not been incorporated into the initial installation.

# hzcms update

Disable the "default" site provided by Debian and then enable the http and https hub sites

# a2dissite 000-default
# a2ensite example example-ssl
# /etc/init.d/apache2 restart

The default SSL certificate is meant for evaluation purposes only. For a production Hub, you will need to obtain a certificate from a provider. A certificate may contain two or three pieces: a public certificate, a private key, and sometimes an intermediate certificate. 

Once you obtain the certificate, install their respective sub-directories in the /etc/ssl directory. 

After the certificates are installed, you will need to modify the Apache configuration template located in /etc/apache/sites-m4/{hubname}-ssl.m4.

Replace SSLCERTFILE on line 184 with the path to your SSL certificate.

    SSLCertificateFile /etc/ssl/path/to/cert

Replace SSLCERTKEYFILE on line 185 with the path to your SSL key.

    SSLCertificateKeyFile /etc/ssl/path/to/key

If you have an intermediate certificate:
    remove line 186: ifdef(`SSLCERTCHAINFILE',`
    remove line 188: ')dnl
    Replace SSLCERTCHAINFILE with the path to your SSL key.

Once the paths have been updated, reconfigure the CMS.

# hzcms reconfigure example
# /etc/init.d/apache2 restart

If you are using the HTML5 VNC Proxy Server, you must update your certificate settings as well.

The default installation of the CMS uses a self signed SSL certificate. Some browers will not accept this certificate and not allow access to the site.
 

https://support.mozilla.org/en-US/questions/1012036

You will need to install a proper SSL certificate.