“External” HTML Clients (browser clients) get disconnected or cannot re-connect.
I know about the following article which i have tested, It worked for some but not for others.
(https://kb.vmtestdrive.com/hc/en-us/articles/360000914833-Horizon-Cloud-Known-Issues)
When using External software (Horizon Client), these connections do not drop, but only external HTML Client connections.
Any advice would be appreciated.
Regards
Hi RLillicrap_SA,
Did you get an answer on this, or were you able to resolved it? Can you please share how you fix it?
I'm getting the same issues.
Thanks,
hello
any update, i have the same prob with internal and external user only with web client.
horizon view client "Your session has expired. Please re-connect the server"
i change global session settings in horiozon console but no change.
We are experiencing the same problem, seems to only happen when trying to authenticate to the loadbalancer VIP url of Horizon web console.
This issue can be seen mostly if the initial connection is going through Load Balancer to VIP.
If the connection is made directly to the Connection server IP / FQDN or UAG IP, it work fine.
Lets understand:
Please give kudos if it help
https://www.surajroy.com/
Here's how we addressed it.
Accessing connection server using HTML access results in the error message: Your session has expired...
We had this issue on our html websessions. This impacted both internal and external users. The fix for us was setting a Persistence Timeout of 8-12 hours, and additionally using the Horizon GPO bundle and setting the session timeout for 8-12 hours to match. Hope this helps someone. We also researched using XFF headers to keep the communication to the host Horizon server clean so the traffic didn't go to the wrong server. See the yellow note at the top of this article- Dashboard alerts for unrecognized requests for XML Api protocol connection in Horizon 2209 (8.7) (90...
That issue happens with load balancers on ANY version of Horizon, not just 2209-2212.
For later versions of Horizon be sure to set the Locked.Properties file to your load balancer and server name using portalHost entry.
Hi @garfield51, would you mind clarifying which settings you mean please?
"The fix for us was setting a Persistence Timeout of 8-12 hours"
Is that Horizon Admin Console -> Settings -> Global Settings -> Forcibly Disconnect Users setting?
"and additionally using the Horizon GPO bundle and setting the session timeout for 8-12 hours to match"
Is this a GPO set on the VM and the setting: Computer Configuration -> Administrative Templates -> VMware View Agent Configuration/Agent Configuration -> Idle Time Until Disconnect (VDI) or something else?
Much appreciated!