article Enabling TCP Keep Alive Functionality In Qlik Sense in Official Support Articles

Enabling TCP Keep Alive Functionality In Qlik Sense

Andre_Sostizzo — Thu, 19 Mar 2026 06:08:47 GMT

For Qlik Sense Enterprise for Business (Cloud), see Loading of an app is hanging when using Qlik Cloud.

Working in a Qlik Sense app after remaining inactive causes fails with the error:

Connection to the Qlik Sense engine failed for unspecified reasons. Refresh your browser or contact our system administrator

The issue specifically affects external users who have been inactive until a network device's (Firewall, Router, etc.) idle timeout was reached. This is followed by a connection reset for the TCP WebSocket session.

Cause:

TCP WebSocket connection is terminated by the firewall because the firewall is not receiving any TCP traffic such as keep-alive packets from client browser (e.g. Firefox, older Chrome versions). Specific web browsers have their own tcp keep-alive behavior.

This issue may be found with less frequency with IE because it sends the TCP Websocket keep-alive more frequent than any other main stream browser. Here are the default intervals for the three main browsers latest releases as of September 2020:

Default TCP-Keep-Alive intervals:

Chrome: 45 sec
Edge: 45 sec
Internet Explorer: 30 sec (see IE: Change Keep-Alive timeout)
FireFox 81.0: 10sec for ~2 minutes (115sec) period, then a keep-alive packet every 10 minutes; More details under Mozilla Networking Preferences.

General Information

This functionality is by default switched off not to affect any existing customers. Customers who do not experience any issues with web sockets terminated by the network due to inactive SHOULD NOT switch this feature ON since it will send unnecessary traffic on the network. See How are WebSockets used in QlikSense ? for more information.

How to configure?

Stop the Qlik Sense Proxy Service
Edit the file C:\Program Files\Qlik\Sense\Proxy\Proxy.exe.config This location may not be available if Qlik Sense was not installed in the default location.
Add the configuration key:
<add key="WebSocketPingInterval" value="0"/> <!-- Interval in seconds for the web socket ping to the client (a value of "0" is disabling the ping)–>Where value is a suitable positive number depending on the inactive web socket timeout setting in the network. The effective interval that the Qlik Sense Proxy server will send keep-alive messages towards the client my oscillate between 2 x value and 1 x value, since it also takes into account backend inter-process socket activity. Eg: setting the value of WebSocketPingInterval to 30 may lead to keep-alive messages sent to the client every 30 or 60 seconds.

Note: The Qlik Sense Proxy service may not send keep-alive packets if it detects activity on that client's Websocket tcp session.

Recommended is 60-300 second range, shorter interval generates more load on Proxy CPU and network. It should be set as high as possible, meaning it's best to identify at which interval an intermediate proxy cuts the connection when it perceives it as idle, and then set the ping interval to a slightly smaller value.

A too small number (e.g. less than 30) will load the proxy and the network and IS NOT recommended. Suitable numbers could be 60 to 300 (i.e. 1 minute to 5 minutes), but it all depends on the network configuration (if the network removes web sockets that have been inactive for more than 5 minutes then, of course, the value must be set something less than 5 minutes (i.e. less than 300)). If a lower value is required, it is recommended to investigate the components involved in the connection, such as third party proxies and network load balancers to configure them with less restrictive timeouts.

It is possible that the same WebSocketPingInterval value has different behaviors in each Qlik Sense Hub section due to third party network device. The value may keep the connection live in Dashboardbut, but still lose connection in Data Load Editor. You may test with a lower WebSocketPingInterval value until the proper value is found to keep connection in all sections. For example, when connectingCloudFlare as web application firewall, theWebSocketPingInterval value may need to set to 10 seconds otherwise "connection lost" may still be received in Data Load Editor even the rest of Qlik Sense Hub keeps connected.
Restart the Qlik Sense Proxy Service.

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

RajanKasbe_Expo — Thu, 25 Jun 2020 08:22:24 GMT

After performing the step 1-4 mentioned above, how to validate the thing for which have performed those step. Or how to identify that NPrinting server is connecting to Qliksense server

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

Andre_Sostizzo — Thu, 25 Jun 2020 13:46:15 GMT

@RajanKasbe_Expo , are you performing this task to troubleshoot the connection setup on the NPrinting server? It is not clear how this post would assist with that task.

TCP Keep alive packets are sent to the server as long as you have an app open in Hub. These packets will show in a network capture.

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

john_oll — Thu, 30 Sep 2021 09:30:29 GMT

@Andre_Sostizzo
is there a similar feature for keep alive for Qlikview?
I found only the SocketTimeOutInSeconds Setting, which is not the same as a Ping interval.

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

Sonja_Bauernfeind — Fri, 01 Oct 2021 11:40:46 GMT

Hello @john_oll !

No equivalent exists for QlikView, as QlikView does not have that specific need. Extending the timeouts is generally sufficient, as we do not use WebSockets that will disconnect on inactivity.

However, third party tools (browsers, firewalls, proxies,..) can interfere here and cut the connection.

All the best,
Sonja

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

SaturnV — Wed, 31 Aug 2022 07:59:25 GMT

If you have a multinode environment. On which server should this be done?

We have 4 hosting nodes (where our customers are connected to the HUB), 2 Proxy nodes, 3 reload nodes (engine nodes which reload apps daily) and the central node. Is this necessary on all nodes or just some?

Thanks and regards
Julian

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

Sonja_Bauernfeind — Wed, 31 Aug 2022 08:25:25 GMT

Hello @SaturnV

This article is specifically aimed at the proxy service (hub connection), so any of the proxy nodes in your environment would need to have these changes made.

All the best,
Sonja

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

SaturnV — Wed, 31 Aug 2022 12:07:21 GMT

Hey @Sonja_Bauernfeind,

I just changed the proxy config for our Proxy nodes and restartet the Services but it still disconnects after about 100s.
Shouldn't there now be visible Websocket requests which can be viewed in the browsers network traffic for the specific Qlik WS?

Best
Julian

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

Sonja_Bauernfeind — Fri, 02 Sep 2022 10:43:10 GMT

Hello @SaturnV

You would be seeing WebSocket traffic in your browser debug tools regardless of whether or not you've set this setting. Here is some general information on how to debug WebSocket traffic: Debugging WebSocket in Google Chrome.

Here's also one of ours: How to time a Qlik Sense WebSocket connection.

If your connection still times out, I'd recommend reviewing the relevant log files (not only Qlik Sense logs, but also your network components) to see where the connection is being terminated. Here is an article that walks through a few of the basics: Qlik Sense Enterprise Hub timeout.

Should you need more assistance, I'd recommend posting on our forums (Deployment and Management ) to get assistance from our larger community.

All the best,
Sonja

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

federicotedesco — Mon, 12 Jun 2023 16:30:54 GMT

Hello everyone,

thanks for the article becasue we have found the cause of the lost connection.

In our architecture there is a network appliance that block the web socket connection.

In proxy.config we have set the web ping interval to 50 second (may be necessary to set a value to 40/45).

You suggest:

A too small number (e.g. less than 30) will load the proxy and the network and IS NOT recommended. Suitable numbers could be 60 to 300

In this case, can we keep/decrease the value of web ping interval or is it prefer an increase the timeout side network appliance?

Regards

Federico

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

Sonja_Bauernfeind — Tue, 13 Jun 2023 06:48:04 GMT

Hello @federicotedesco

We would recommend increasing the timeout on your network appliance. If you are unable to do so, decreasing the interval of pings is of course a possibility, but we cannot advise it. If you choose to decrease the interval, make sure to monitor the performance of the systems.

All the best,
Sonja

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

twales — Fri, 29 Sep 2023 14:15:53 GMT

Hi,

Setting up 7th AMI Aug/2023 BYOL server Windows 2019 on AWS.

I have installed 6 previous qlik ami's(2020-2022) all the same on AWS networks. As client managed cloud servers.

Have never had a disconnection every 60 seconds.

Set the client TO-300 as usual. Even opened other ports 4747, etc. Tried both Chrome and FF. Still no change.

Set WS ping to 30s. Now working as expected, that is TO is 5 minutes.

Network appliances I use NAT and LB's are default to 350s by AWS, 6 mins.

This AMI also still had the incorrect postgres dir in the ps1's. Had to change all to 14.

This seems to be a Qlik problem as I've done this 6 servers all actively running on the same AWS networks and this never happened before. Also not sure what I would do when AWS is defaulted to 350s already.

Any ideas?

Thanks

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

willtech93 — Sat, 23 Dec 2023 01:29:04 GMT

Hi all,

We had the problem with these kind of disconnections with some users and had to apply this functionaly in order to sessions lasting longer than five minutes, even with the Virtual Proxy settings at a higher time, this continued to happen. Any ideas of why this could be happening. Never had happened before and its just for some users.

Thanks.

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

Sonja_Bauernfeind — Wed, 03 Jan 2024 10:25:17 GMT

Hello @willtech93

If only specific users are affected, we recommend reviewing the Qlik Sense log files for additional information and investigating the differences in the setup these users have (different browsers, different network devices, VPNs used and so on).

All the best,
Sonja

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

sanrout — Tue, 18 Jun 2024 11:31:01 GMT

Hi @Andre_Sostizzo @Sonja_Bauernfeind,

We did add the above entry in proxy config file and interval was initially set at 90 seconds (considering the recommendation 60 to 300) and still the issue did appear and hence we tested with different values i.e. 60, 30, 15, 10 and lastly with 5 seconds. For all the cases we noticed the issue did not get solved.

We have used Wireshark to understand if Qlik Sense server is sending any tcp keep alive. To our surprise, it did not show any such tcp keep alive. However if we run from client side (my machine) I did notice such tcp keep alive. We do not understand why server/instance

Client side: wireshark shows tcp keep alive messages almost for 45 seconds

Server side (AWS EC2 windows server 2016): we do not notice any tcp keep alive messages being sent

is not sending such tcp keep alives ?

Windows server registry editor has the below settings for the tcp keep alive.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\: KeepAliveTime: 30000 KeepAliveInterval: 1000 TcpMaxDataRetransmissions: 10 These settings use the DWORD data type

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

Sonja_Bauernfeind — Wed, 26 Jun 2024 06:52:55 GMT

Hello @sanrout

This question would require direct investigation. I either recommend posting about your challenges in the appropriate forum (Deployment and Management), or investigating the possibility of contacting support.

All the best,
Sonja

article Enabling TCP Keep Alive Functionality In Qlik Sense in Official Support Articles

Enabling TCP Keep Alive Functionality In Qlik Sense

Cause:

General Information

How to configure?

Related content:

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

Re: Enabling TCP Keep Alive Functionality In Qlik Sense

Re: Enabling TCP Keep Alive Functionality In Qlik Sense