Hi,
I just upgraded my Horizon View 6.2 environment to 7. The upgrades seemed to well of my Composer server and my two connection servers. However when I try and login to the Admin page it is just a blank blue screen and the watch keeps going round and round. Anyone seen this yet?
Thanks.
Use a different browser than chrome if that's what you used in the past. We are having this same issue too and the warning is blank except for a time stamp. Also, HTML Blast does not work through chrome anymore, it says it can't find the connection server, but all other browsers work.
TL;DR
Google Chrome no longer works with Horizon View 7 products.
That is a tough one to believe. How can Chrome not be supported in Horizon 7? What version of Chrome are you using?
While hard to believe we've testing on several OS's, and machines on prem and off. We've tested version
47.0.2526.106 m
and
49.0.2623.87 m
The specific pages/items that don't work any longer are:
Load Balanced https://view.site.com/admin
Hostname only https://hostname/admin
HTML Access via hostname only https://hostname
HTML Access via Load Balanced name Https://view.site.com
Things that still work:
PCoIP via Client
FQDN Admin Page directly to connection server (not load balance name) https://FQDN
Main horizon page of https://hostname OR https://FQDN
Right now it appears only directly to A connection server AND via FQDN (Yes I know this is best practice, BUT this wasn't broken before) is the only means working IN CHROME. IE and Edge are functioning correctly.
And confirmed it works in FireFox. It's a Chrome specific issue at the moment. I'm thinking our Load balancing isn't using FQDN in the back end and I bet something being handled in Chrome doesn't like what view is presenting anymore unless it's a FQDN
Did you find a permanent fix for your issue?
I have been just using Firefox for the time being until I hear of a fix.
I wish someone had an actual fix for Chrome working with anything in Horizon 7
You sir, are my hero. That fixes Chome for the admin page and HTML use!
I wonder why only Chrome was affected.
I just realized who replied... Damnit Carl! Why are you so awesome!
Literally, I've built my whole infrastructure from YOUR guides! Epic man...
I tried this workaround with Horizon 7 and Chrome on MAC - no luck...
FWIW, be sure to restart the browser as well.
Confirmed this works with Chrome 58.0.3029.96 (64-bit)