I have Qlik Sense single node installed on an Azure VM. There are 2 virtual proxies one Central for accessing over Intranet (http). And other Azure for accessing from public internet (Azure Reverse Proxy). Azure Virtual Proxy comes with a trusted certificated released by themselves.
We wanted to have connection over Central proxy inside our Intranet to be secure (https) so we've issued a SSL certificate. I provided the certificate thumbrint in Central Proxy which is linked to all Virtual Proxies and conection over intranet was working as expected. It's https now, secure. But the Azure Virtual Proxy stopped working. I can still get authenticated but the "Connection lost..." error comes right after logging into the hub. I've run the Websocket Tester and it's indeed not working anymore (Before SSL everything was green).
I've tried running it in all the browser. Whitelisted all the IPs and domain names. DevTools show 2 errors:
- WebSocket connection to 'wss://myurl' failed: createSocket @ hub.js?1343223423:1
- Possibly unhandled rejection: {"isTrusted":true}
From what I can observe the issue is with the conflict of 2 different certificates. Because when I upload it, it goes to Proxy so it applies to all Virtual Proxies. But the Azure one has one by default. When I investigate both URLs site information in Certificate tab there seem to be correct certificates on both. Central has an issued SSL, Azure has Microsoft Certificate.
I will be talking with Microsoft support but it seems to be an issue on the Qlik side since their proxy works ok when I don't import SSL.
I would really appreciate any help on this.
