Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
After installation of Qlik Sense Server, everything works fine. However, there is the annoying message when trying to connect to the Hub indicating that your connection is not private.... (not a trusted site issue). So to make this a trusted site, I installed a server certificate on the server. This certificate is a wildcard certificate (*.XXXX.com). I then modified the proxy and added the thumbprint for the new certificate and restarted the proxy. Now when I try to connect using the new trusted site name, I receive the following error:
The NODE host name at installation was: ehlqliksense.XXXX.internal
A DNS entry was created for ehlqliksense.XXXX.com
Does the Node name have to match the certificate name?
Are wildcard certificates usable in Qlik Sense?
How do we make this a trusted site and not use the default untrusted certificate created at installation?
Accepted Solutions
Hi Kevin,
Please try the followings:
1. If you can RDP to the server to open the QMC:
a. under "Proxies", there's option to enable "http" (This will allow you to go back to QMC in case SSL Certificate installation went wrong).
b. if you cannot login to QMC at all, you may need to undo the SSL Certificate process, and once done so, you can then try step 1a.
2. Once you enable the http, under either "Virtual Proxies" or "Security" section (I forget which one), there's a whitelist section. You can enter your URL here.
3. Try to reconnnect now. If all good then, you can try to re-import your SSL Certification and try again to see if you're okay now or having other issue 
Cheers,
-Anton
Anton,
Thanks for the info but I have already tried what you suggested without success.
This process shouldn't be so complicated. You can have users accessing the Hub and having to deal with the untrusted site issue.
I can connect to the HUB and QMC however I can not connect via HTTPS using the trusted certificate I applied.
When connecting to the QMC, You can see that the certificate is being served it's just not being used. However, it does not work at all when trying to connect to the Hub.
Hi Kevin,
We have similar issue, and in fact, you're probably ahead of us since you're able to reach QMC. I have issue on both reaching QMC & Hub (both always show "There's problem with website security certificate" msg):
I agree with you, that this supposed to be simple; Once SSL Certificate is imported, take the thumbprint, and place it on the QMC. Sadly, we're still experiencing some issues around this area ourselves.
Just wondering, do you have your server hosted on premise, or is it on the cloud such as Amazon Web Service (AWS) or Microsoft Azure environment? Not sure if it makes a difference, but ours was installed within Microsoft Azure. I also found this article, that shares similar issue like yours (He tried to access it from outside the server).
I don't have access to hub or qmc out of the server
Sorry if I cannot be much of a help at this point. I'll try to dig in more and post it back here. Stay tuned.
Cheers,
Anton
Anton,
Sense is installed on a VM in-house.
Like I mentioned earlier, there are no issues with QMC. It gets the correct certificate information and is connected securely. Our only issue is the hub. The only thing I can think of is that the server name is different.
For us, the server name is ehlqliksense.embracehomeloans.internal. We created a DNS entry called ehlqliksense.embracehomeloans.com. The certificate installed is a wildcard certificate *.embracehomeloans.com. When I connect to the hub, it connects securely but the hub application is throwing the error.
This is annoying and shouldn't be a difficult issue to resolve! At this point, we are unable to push anything out to the user community so we are at a standstill.
I'll let you know if I find a resolution