Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Apr 10, 2025 8:00:55 AM
Sep 6, 2017 11:39:29 PM
Qlik Sense uses HTTP, HTTPS, and WebSockets to transfer information to and from Qlik Sense.
The attached Webscoket Connectivity tester can be used to verify protocol compliance, indicating if a network policy, firewall, or other perimeter device is blocking any of the required connections.
If the tests return as unsuccessful, please engage your network team.
The QlikSenseWEbsocketConnectivtyTester is not an officially supported application and is provided as is. It is intended to assist in troubleshooting, but further investigation of an unsuccessful test will require your network team's involvement. To run this tool, the Qlik Sense server must have a working internet connection.
Qlik Sense Enterprise on Windows
Since the introduction of extended WebSocket CSRF protection, using the WebSocket Connectivity tester on any version later than November 2024 requires a temporary configuration change.
<add key="WebSocketCSWSHCheckEnabled" value="true"/>
<add key="WebSocketCSWSHCheckEnabled" value="false"/>
Verify that WebSocket is enabled in the network infrastructure, such as firewalls, browsers, reverse proxies, etc.
See the article below under Related Content for additional steps.
This will not work with the default setup of Qlik Sense November 2024 with Patch 5.
You must change the config file of the proxy. Otherwise, WebSockets testing will fail.
As per @vincent_wei
Starting with introduction of Qlik Sense Enterprise on Windows: Extended WebSock... - Qlik Community - 2509211 and option below:
<add key="WebSocketCSWSHCheckEnabled" value="true"/>
in "C:\Program Files\Qlik\Sense\Proxy\Proxy.exe.config" the WebSocket tester will fail.
To be sure no other reasons are preventing the connection set the option to false:
<add key="WebSocketCSWSHCheckEnabled" value="false"/>
restart the proxy and test again.
Revert above option as needed once confirmed it is not related to the missed CSRF WebSocket Token.
Hi,
We have followed the steps to change the Proxy.exe.config. After we revert the change (replace the original proxy.exe.config file) and restart the services, we cant access qlik sense via ssl url link, but able to access via ip address.
The url link cant be open and stuck at this link 4244 during authentication.
https://abc.com:4244/internal_windows_authentication/?targetId=<guid>
What steps that we missed out during revert?