Notes from the field: Horizon and the locked.properties debacle

On a recent Horizon deployment version 2212.1 we just couldn’t get the workings correctly with the portalhost/balancedhost entries, the “workaround” for that matter until we get it sorted out is to turn back on the unexpected host feature like below:

allowUnexpectedHost=true
checkOrigin=false
enableCORS=false

Well this worked only for the original installed URL of the connection servers and load-balancer for that matter, all other SAN entries which were valid and should be used we’re providing the error: Error Pager failed to load

Log entries did not mention any portal/cors or any other issue (with or without the locked.properties allowing the all hosts again)

I stumbled around this article: Unable to login to Horizon Admin Console. Error: “Page failed to load. Please refresh the browser to reload again” (94217) (vmware.com)

This entry was not there as this was a new deployment, added the entry and rebooted the whole cluster and afterwards everything started working as it should. Very strange behavior and did not encounter this before, we’re keeping this one like it is and are going to log a case for further troubleshooting to see if this is a bug or not.

Hope it helps!


Posted

in

,

by