The server name in the url you are typing in to access the hub from the server where sense is installed is not the same server name as referenced during the Qlik Sense install. If you go to MMC and open the certificates snap-in for local computer, you can identify the name of the cert and it likely matches what you need to type in for the server name in the url.
Thanks. Let's say QlikSer is my Qlik Server. The certificate's "Issued By" name is "QlikSer.domain.com-CA", and "Issued To" is "QlikSer.domain.com".
Only when I access the site from within QlikSer and I type "QlikSer.domain.com" in URL bar, would the certificate turn green (good).
But when I access same "QlikSer.domain.com" from another computer, it is still showing wrong certificate :-/
BTW, I am trying to access the certificate information by clicking on that red-crossed lock on URL bar. Which MMC.exe are you referring to, is it on the QlikSer.domain.com or on the client side? If on the server side, which folder and certificate should I look into: there is QlikClient, QlikSer.domain.com.
So the reason you are getting a cert privacy warning on another computer is a result of not having the client certificate installed on that machine, or not having a certificate installed on that other machine that has a relationship with the cert used by the Qlik Sense server.
Here is an article that explains how certificates work in general terms.
Simply put: How does certificate-based authentication work? | Network World
The question eventually becomes how you intend to deploy. What is a likely scenario for you? If you have a web server sitting in front of the Qlik Sense server with a certificate trust between them you can potentially, and I emphasize potentially, have the web server side ignore client certificate requests.