-
1. Re: Horizon HTML Landing Page - All White
epa80 Sep 27, 2019 4:38 AM (in response to epa80)Our 1st fix attempt didn't pan out. We discovered that 443 was opened between the UAGs in the DMZ and the Brokers in the secure network, but only via their load balancer, not the individual brokers. We had the firewall team open it to all the brokers, which they did, yet the issue remains. Looking now for a different solution.
One new update: we found that the behavior has a slight alteration. When we click "VMware Horizon HTML Access" and get to that blank page, it isn't PERMANENT. It actually eventually does get to the login page, it just takes minutes to do so (I've seen up to 10 as low as 6). I'm wondering if we could have a routing issue.
-
2. Re: Horizon HTML Landing Page - All White
ap_idb Sep 28, 2019 8:57 PM (in response to epa80)Do you have your static routes correct? This could be a dumb question, as you would need to have that to route to your Horizon Connection Servers. HTML Blast needs more ports though, try this:
-
3. Re: Horizon HTML Landing Page - All White
epa80 Sep 30, 2019 10:21 AM (in response to epa80)We think we found the issue. There's a faulty health check out on the F5s that we think needs to be resolved. We're looking to modify it Tuesday, tomorrow, and test it again. We're pointing load balancers at load balancers at load balancers and one is being marked down erroneously. Almost positive this will end up being it.
I'll update the thread with the results.
-
4. Re: Horizon HTML Landing Page - All White
krogerkiran Sep 30, 2019 10:30 AM (in response to epa80)I had the same landing page - all white issue and i was waiting for the quick update to resolve this issue very soon.
Thanks in advance.
Kroger Kiran - Krogerfeedback
-
5. Re: Horizon HTML Landing Page - All White
epa80 Oct 3, 2019 6:59 AM (in response to epa80)Unfortunately we were mistaken. We had our F5 guy change the health check to actually make it show as up, eliminating the possibility that F5 marking it down was causing the hang up, but, no luck. We still had the issue.
We're still looking into it.