An increasing number of Internet applications use WebSockets (wss://), such as VirtualBrowser and some video-conferencing apps.
WebSockets maintain long-lived connections to target servers.
Configure the load balancer to support these use cases.The TCP Keepalives option is available with Artica v4.50 Service Pack 6 or Artica v4.50 Service Pack 5 Hotfix 20250910-20
If your users are seeing disconnect/reconnect issues in their video-conferencing app, the load balancer is likely terminating TCP connections to avoid long-lived sessions.
While this can improve distribution to backends, it forces WebSockets to re-establish their sessions, which can make the web application unstable.
To do this, increase the timeout values substantially so the load balancer only closes the connection after a very long period.
- On the left menu got to
HaCluster > Status > Parameters - Click on the TimeOuts link
- Set the Server timeout (default 300 seconds) and Client timeout (default 10 seconds) to match the average video-conference session length; in our example, set both to 7200 seconds (2 hours).
- The TCP Keepalives (client & server) should help too:
When enabled, the load-balancer sets TCP keepalives on client to proxy and proxy to Web server sockets.
This helps keep long-lived idle tunnels (e.g., WebSocket/CONNECT) from being dropped by NATs/firewalls and detects half-open connections.
Note: Keepalives don’t override Load-balancer timeouts