We have the option of setting https (secure) connection between the CCM (PC) and the LQ box. This is different to the actual audio & data flow between the LQ link boxes CCM uses HTTP or HTTPS to communicate with LQ.  

LQ linking uses either HTTP or HTTPS to initially setup a tunnel on TCP/UDP IP port 655. Once the tunnel is setup, there is no more communication between LQs on port 80 (http) or 443 (https - or whatever port you might have redirected). 

Audio and Data all go through port 655 in an encrypted tunnel after the initial setup. HTTPS port is always available on LQ.

“Force HTTPS = Enabled” returns “302” on HTTP requests coming in on port 80 indicating that the browser/LQ should retry with HTTPS on port 443.

In a link group you can have a mix of LQ with HTTP and HTTPS. You can have a mix of certificates as well. CCM can access any LQ in a group with HTTPS. If you try with HTTP, the ones with “Force HTTPS = Enabled” will redirect the CCM to HTTPS, the others will stay HTTP. When linking, a LQ Link-Member tries to contact the Link-Master with HTTP or HTTPS, depending on what has been put in the IP address box. Then it configures a tunnel on port 655 and stops using the initial HTTP/HTTPS port. Helixnet does not support HTTPS, only HTTP. So Helixnet Link-Member initially contact Helixnet Link-Master with HTTP. LQ linking to Helixnet Link-Master must use HTTP in the linking IP address.