QuickHMI uses its own self-signed SSL certificate by default. This has the advantage that you do not have to worry about obtaining your own certificate, but can still take advantage of a secure SSL connection.

The disadvantage of a self-signed certificate is that a warning message appears when the visualization is opened, indicating that the connection is not secure because the identity of the server could not be verified.

This error message only appears the first time the visualization is opened. After you have confirmed the warning once, only a note remains in the address bar that the connection is not secure. Despite this warning, all communication between client and server is encrypted. Only the identity of the server could not be conclusively verified.

Use of your own certificate

The problem described above can be solved by using your own certificate signed by a trustworthy source. There are also free providers for this, such as Let’s Encrypt.

If you have received such a certificate, you can load it into the QuickHMI server via the RuntimeManager.

Certificate import in the Console RuntimeManager

If you are in the main menu of the Console RuntimeManager, select option 6 to configure the SSL certificate.

What would you like to do?
1: Exit
2: Start instance
3: Load project
4: Change project settings
5: Change datasource settings
6: Change SSL certificate
7: Change OPC application certificate
8: Change MQTT certificates
9: Delete instance

Option: 6

You will then be asked to enter the path to the .p12 or .pfx file and then the passwords for the keystore and the key.

A successful import is confirmed by the message “Import successful”.

Supported extensions are '.p12' and '.pfx'.
Certificate path: "C:\ProgramData\QuickHMI\QuickHMI Server Jellyfish\certificates\QuickHMI_SSL.p12"
Keystore password:
Key password:
Import successful

Certificate import in the graphical RuntimeManager

To import a new certificate, first switch to the “Servers” page in the RuntimeManager by clicking on the “Servers” button (1).

You will then be in the “Certificates” tab, click on the “Select” button in the SSL certificate area (2).

In the dialog that opens, select the certificate file and enter the passwords for the keystore and key. Click on the “Save” button to load the new certificate and use it from the next instance start.