The solution is to be sure to have ope the port 4747 to avoid the Qlikview go using tunneling.
QV Server Reference Manual:
17.2 QlikView Server Tunnel
If the standard communication port to QlikView Server (4747) is blocked in any way (typically by a
firewall limitation), the Windows Clients will attempt to re-route their connection through port 80 (http).
This connection path must then include the QVWS so that the QlikView Tunnel communication can be
established. All communication through the QVS Tunnel must include the secure communication packet,
so this will significantly increase the network traffic (along with response times) required between the
QlikView Server and the client. The infrastructure might also interfere, for example, if the traffic is routed
through proxy servers. This is especially true if tunneling using HTTPS. It is recommended to set up rules
to bypass proxy servers when tunneling using HTTPS.