assuming you might have added everything in virtual proxy whitelist.
do you have any thing between your external machine and Sense server? Like TMG/Identity provider?
then you have to add those to your white list and needs to copy those certificates over to sense server If it is HTTPS.
Have you tried both HTTP and HTTPS?
and are you getting login screen and when you enter your credentials you are seeing this screen?
usually since it is a Windows login format you have to enter with DOMAIN\UserID format.
In your second screenshot the Engine should only listen on port 4747. That is a internal port used for communication between the Qlik Sense services so nothing that would impact external access.
However, looking at your screenshots it seems your are trying to access the Hub from a different url.
Make sure that url is in the Websocket white list for the proxy. QMC > Virtual Proxy > Your Proxy > Advanced > Websocket origin white list.
Also port 4248 for http based authentication or 4244 for https based authentication has to be opened in the firewall on the server and clients.
This is a good overview of the different ports you need to open, https://help.qlik.com/sense/2.0/en-US/online/Subsystems/PlanningQlikSenseDeployments/Content/Server/Server-Deployment-Po…
I would like to thank the intersection.
As you can see, access the server at https, this ok. But when I try to external access via http is not working.
When trying to use the domain / userId the following error appears.
When I use domain / userId, the following error appears.
The IP already whitelisted and the doors have been released in the firewall, as reported.
When libero access instead of http to https, the error of I believe because they do not have a digital certificate.
I'm almost asking to buy a digital certificate, but my concern is not work with the digital certificate as well.
Hi Jorge. If you flagged Kerberos you checked the proxies (Single Sign On with Qlik Sense) and besides that how is the DNS subdomain handling ? On Server you can access from the internal link ( it has a desktop shortcut on Server to access the hub) If you can access on server, probably you have an issue with redirecting URLs.
From what I can see in your screenshots, it is actually working. One of your screenshots clearly shows that you can access the server over https. Sofar the problem seems to be solved.
But if I understand you right, you want to use http instead of https when accessing the server externally. I would strongly advice against it, unless ofcourse you have a setup in mind which sufficiently protects your traffic instead of TLS.
If you really want to use http instead of https, when accessing the server externally (I'll advice against it once again) then you need to click the checkbox "Allow HTTP", which can be seen on the next to last screenshot you have. The one with the arror pointing towards Kerberos authentication.
Once that is done, it's basically down to your network setup. Any firewalls/routers in place which may affect the access from the outside perhaps?