Is there further configuration required to prevent this message? Note that the cube client logs in without any issues on this https configuration, and only the message is coming up under ‘log settings’.
Hi Srikanth,
Can you verify that the hostname that Cube is connecting to matches with the certificate offered by the webserver, and is the same as specified in the MaintenanceSettings.xml?
Can you verify that the Cube Launcher validates this hostname with “HTTPS available”? Or that a system browser (Edge, Chrome, Firefox) can navigate to this hostname without a certificate warning?
Also see the documentation on HTTPS configuration.
Accessing a DataMiner from behind a reverse proxy is not officially supported. This will appear to work in scenarios where it is transparent to the end-user, but other scenarios like displaying embedded webpages in Cube require the DataMiner to know its externally accessible hostname when composing URLs.
Cube client validates the HTTPS and shows as available. However the browser still gives the certificate warning. Please note that this system is configured not using maintenancesettings.xml and IIS bindings. It’s https enabled using a proxy which redirects the requests to http connection on DMA.