Our DMS (one failover pair) is IP address based, so no hostnames are in place. We use IP addresses only at this moment.
I have configured the https as per user guide with the self signed certificate that lists the VIP IP address (and other IP addresses of that server) in SAN. The CN configured is the primary IP address of the server. First I kept the http binding in place too. With that configured I can properly connect from a WEB client over https. Cube app works well.
Secondly I removed the http binding. The WEB still works OK, but now I can’t connect with cube app.
I noticed that the previously opened cube app (one opened and logged in before http binding removal) is working fine and normally interact with the DMS.
So it seems the cube app uses http in the initial stage (probably downloading actual version). How to change this initial cube communication to https so cube app will work well?
Hi Miloš,
If you are on a recent version of the Cube Launcher, you can modify the settings for the button and select "HTTPS only" as the transport.
Alternatively, you can add the button again. In the dialog, it will be checked if HTTPS is working correctly and if so, the new button will be added with the "HTTPS only" option. If not, you will be able to see details about what is wrong with the HTTPS configuration.
