Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
Senor_Dai
Partner - Creator II
Partner - Creator II

SSL on new Qlikview Server Deployment

Hi,

I've created a new Qlikview deployment in AWS .  If I set the port to 80 in the QMC I can access the AP externally with no problems.  Ive carried out the usual process outlined here :https://community.qlik.com/t5/Knowledge/How-To-Setup-HTTPS-SSL-with-QlikView-AccessPoint-WebServer-a...

So, after entering this cmd 

netsh http add sslcert ipport=MyPublicIPAddress:443 certhash=0ca71e2ecef0ff3e6cxxxxxxxxxxxxxxxxx appid={99999999-9999-9999-9999-9999999999999}

and then run the cmd netsh http show ssl

gives the following :
Screenshot 2021-09-13 at 16.34.42.png

 

However, when I switch to 443 and https on the QMC - the access point doesnt respond (even after a server restart).

Ive also double checked that 443 is allowed inbound on our AWS Security group:

Screenshot 2021-09-13 at 16.57.17.png

Also to add,  ive installed QV Server version 12.60.20000.0

Is there anything Ive missed?

Many thanks,

Dai

 

Labels (1)
  • Other

1 Solution

Accepted Solutions
Sebastian_Linser

Hello @Senor_Dai 

have you checked the logs here? 

 (C:\ProgramData\QlikTech\WebServer\Log)

 

one thing i would have changed in the command line above is the interface IP

netsh http add sslcert ipport=MyPublicIPAddress:443 certhash=0ca71e2ecef0ff3e6cxxxxxxxxxxxxxxxxx appid={99999999-9999-9999-9999-9999999999999}

to 

netsh http add sslcert ipport=0.0.0.0:443 certhash=0ca71e2ecef0ff3e6cxxxxxxxxxxxxxxxxx appid={99999999-9999-9999-9999-9999999999999}

That would make it possible also to test the accesspoint from localhost https://localhost/qlikview alternativly https://servername/qlikview, and it will still listen to the external IP.

Before you are able to add it the second way you need to remove it with

netsh http delete sslcert ipport=MyPublicIP:443

 

best regards

Sebastian

Help users find answers! Don't forget to mark a solution that worked for you! 🙂

View solution in original post

1 Reply
Sebastian_Linser

Hello @Senor_Dai 

have you checked the logs here? 

 (C:\ProgramData\QlikTech\WebServer\Log)

 

one thing i would have changed in the command line above is the interface IP

netsh http add sslcert ipport=MyPublicIPAddress:443 certhash=0ca71e2ecef0ff3e6cxxxxxxxxxxxxxxxxx appid={99999999-9999-9999-9999-9999999999999}

to 

netsh http add sslcert ipport=0.0.0.0:443 certhash=0ca71e2ecef0ff3e6cxxxxxxxxxxxxxxxxx appid={99999999-9999-9999-9999-9999999999999}

That would make it possible also to test the accesspoint from localhost https://localhost/qlikview alternativly https://servername/qlikview, and it will still listen to the external IP.

Before you are able to add it the second way you need to remove it with

netsh http delete sslcert ipport=MyPublicIP:443

 

best regards

Sebastian

Help users find answers! Don't forget to mark a solution that worked for you! 🙂