Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
jchoucq
Partner - Creator III
Partner - Creator III

qlik sense user disconnections behind F5 Reverse Proxy

Dear all,
 
a customer of ours is trying to use Qlik Sense from outside the company with F5 reverse Proxy. Everything is ok, but there are many disconnections. The IT team look for timeout but without any success.
there is an interesting article : https://community.qlik.com/t5/Knowledge/Hub-access-times-out-with-Error-Connection-lost-Make-sure-th... but for the moment, the customer still have the problem.
 
Disconnections can occur even during reload task or working on design.
 
Does anybody already met the same architecture ?
Thanks and have a good day.
Joh
Labels (2)
3 Solutions

Accepted Solutions
Maria_Halley
Support
Support

@jchoucq 

Have you looked at this article? It addresses how to external load balancers for QlikSense

https://community.qlik.com/t5/Knowledge/Network-Load-Balancer-NLB-Requirements-for-Qlik-Sense-Enterp...

View solution in original post

rohitk1609
Master
Master

Ask your user what is the minimum time when connection stays alive. Use this article and set few seconds above that threshold. 

https://community.qlik.com/t5/Knowledge/Enabling-TCP-Keep-Alive-Functionality-In-Qlik-Sense/ta-p/171...

 

Thanks,

Rohit

View solution in original post

Qlik_Administrator_Dude
Partner - Creator
Partner - Creator

Hello, 
I have used Qlik Sense behind an F5 before. First, what sort of balancing rules on your F5 are you using? I am guessing something like RoundRobin with Sticky Sessions. 

Ensure your Virtual Proxies are working properly. They need to be set up in a way that work with the algorithm you are using on your F5. For instance, if you only have a virtual proxy set up on your Central node, and Users are sent to RIM Node 1, I would expect a disconnect.  https://help.qlik.com/en-US/sense-admin/May2021/Subsystems/DeployAdministerQSE/Content/Sense_DeployA... 

Last I would ensure that the Load Balancing Rules are set up correctly. Check this link out for details: 
https://help.qlik.com/en-US/sense-admin/May2021/Subsystems/DeployAdministerQSE/Content/Sense_DeployA... 

Now to put it all together: The Session is going to be set up on One Node. If you authenticate, and then the F5 changes the Node, the session is lost, and it will cause you to disconnect. You need the Session to be persistent to the the Worker Node (Or Scheduler) for the entire session.  https://help.qlik.com/en-US/sense-developer/May2021/Subsystems/Platform/Content/Sense_PlatformOvervi...

Additional Tip: It might be worth it to double check all of your timeout values as well. Check this link out for further details on that: https://community.qlik.com/t5/Knowledge/Increase-session-timeout-in-Qlik-Sense/ta-p/1713275 

Use Session Monitor, Reloads Monitor, Operation Monitor, Browser Web Developer Tools (or Fiddler), and the Native F5 Tools to try to solve this problem. Reach back out if you are stuck. You can reach out via Linked In for more detailed support too (in my profile). 

Ah, one last thing. The Central Node is the one that does all of the authentication. Be aware of this.

View solution in original post

7 Replies
Maria_Halley
Support
Support

@jchoucq 

Have you looked at this article? It addresses how to external load balancers for QlikSense

https://community.qlik.com/t5/Knowledge/Network-Load-Balancer-NLB-Requirements-for-Qlik-Sense-Enterp...

rohitk1609
Master
Master

Ask your user what is the minimum time when connection stays alive. Use this article and set few seconds above that threshold. 

https://community.qlik.com/t5/Knowledge/Enabling-TCP-Keep-Alive-Functionality-In-Qlik-Sense/ta-p/171...

 

Thanks,

Rohit

jchoucq
Partner - Creator III
Partner - Creator III
Author

Hi @rohitk1609 , thank you for this answer.

it seems that the disconnection occurs every 5 minutes, and the user has set the keep-alive timeout in the QMC to 30 seconds.

You mentioned to set few seconds above the threshold, does it mean, we should test with 305 sceonds as a keep-alive timeout ? maybe i don't undestand, sorry.

Joh

jchoucq
Partner - Creator III
Partner - Creator III
Author

thanks @Maria_Halley i will check this article !

rohitk1609
Master
Master

Do it as per article in config file.

Qlik_Administrator_Dude
Partner - Creator
Partner - Creator

Hello, 
I have used Qlik Sense behind an F5 before. First, what sort of balancing rules on your F5 are you using? I am guessing something like RoundRobin with Sticky Sessions. 

Ensure your Virtual Proxies are working properly. They need to be set up in a way that work with the algorithm you are using on your F5. For instance, if you only have a virtual proxy set up on your Central node, and Users are sent to RIM Node 1, I would expect a disconnect.  https://help.qlik.com/en-US/sense-admin/May2021/Subsystems/DeployAdministerQSE/Content/Sense_DeployA... 

Last I would ensure that the Load Balancing Rules are set up correctly. Check this link out for details: 
https://help.qlik.com/en-US/sense-admin/May2021/Subsystems/DeployAdministerQSE/Content/Sense_DeployA... 

Now to put it all together: The Session is going to be set up on One Node. If you authenticate, and then the F5 changes the Node, the session is lost, and it will cause you to disconnect. You need the Session to be persistent to the the Worker Node (Or Scheduler) for the entire session.  https://help.qlik.com/en-US/sense-developer/May2021/Subsystems/Platform/Content/Sense_PlatformOvervi...

Additional Tip: It might be worth it to double check all of your timeout values as well. Check this link out for further details on that: https://community.qlik.com/t5/Knowledge/Increase-session-timeout-in-Qlik-Sense/ta-p/1713275 

Use Session Monitor, Reloads Monitor, Operation Monitor, Browser Web Developer Tools (or Fiddler), and the Native F5 Tools to try to solve this problem. Reach back out if you are stuck. You can reach out via Linked In for more detailed support too (in my profile). 

Ah, one last thing. The Central Node is the one that does all of the authentication. Be aware of this.

rohitk1609
Master
Master

do it with 290 Seconds. so before session expire, it will recreate it