Qlik Sense (ports 4248 and 4248)

[#1]

I have a new installation env of Qlik Sense for a new project. It’s a licensed copy that the company just brought.

While trying to login to port 80, it also trying to connect to 4248. If using https(443), it is also trying to connect to 4248. My office has a tight network env where only port 80 and 443 are opened. Other ports have to be explicitly put up a formal request with justification why these additional ports are needed. Anyone knows if ports 4248 and 4248 are really really necessary. i.e. Can two ports 80 and 443 work?

Can someone share on their experience to make Qlik Sense Enterprise Server work with just ports 80 and 443 (if any)?

Thanks.

[#2]

Correction, when accessing to Port 80, it try to connect to 4248. For 443, it attempt 4244. Thanks.

[Thomas_Hopp]

Hi,

those two ports are used as long as you are using NTLM based Windwos authentication. Depending on the usage of https or only http one of those ports needs to be open.

4244	Default Qlik Sense Proxy Service (QPS) authentication listen port. This port is used by the internal authentication module in the QPS when using NTLM in Microsoft Windows. This port uses HTTPS for communication.
4248	Optional Qlik Sense Proxy Service (QPS) authentication listen port. The port is used by the internal authentication module in the QPS when using NTLM in Microsoft Windows. This port uses HTTP for communication. This port is only available when client-side HTTP communication is enabled. This is managed in theQlik Management Console (QMC).

If you are not using NTLM in your scenario, it looks a little bit different as you can see on this overview:

http://help.qlik.com/sense/2.0/en-US/online/#../Subsystems/PlanningQlikSenseDeployments/Content/Serv...

I hope this helps. Best regards,

Thomas

[ernstblaauw]

thp‌

At my company, we cannot open port 4244 due to firewall policies which I fully understand: I would expect a web server to just run on the standard 443 port. Can you advise me how to set up the authentication so it just uses the standard 443 port?

[#5]

At my company have similar problem.

It's very bad that application must force the use of non standard ports to function

[TKendrick20]

Was anyone able to figure this out? It's very annoying to have to ask every new client to create a custom firewall rule so that they can access our application.