Horizon Web portal hangs but client works

[glacius2585]

Whomever takes the time to read this, thank you.

We are testing the VDI capabilities as a Proof-of-concept thing, so our setup is not to the Enterprise level.

We are running into an issue.

We have a UAG and it works for the Client, but it does not work for the web portal.

We are using:

Unified Access Gateway Appliance v23.03 (FIPS)

VMware Horizon 8.9.0 build - 21507980 Version 2303

vSphere Client version 7.0.3.01100

VMware ESXi, 7.0.3, 21424296

Attached are screen shots.

Architecture:

Firewall -> UAG -> Connection Server

Ports in firewall:

443, 4172, 8443

UAG and Connection Server are in the same subnet\VLAN so there are no firewall rules to interrupt the connection.

Scenario:

When using the client, users can log into the Pool\VMs with no issue, but when trying to connect using the web portal, it won’t go any further than the first landing page.

There is nothing to say 404 or cannot find resource, it just stays at the Waiting screen, no time out either.

I am not sure what I am missing, and I am not sure where to start looking.

Please, if anyone could give me a little insight or point to something I can start looking at, I would be most grateful.

P.S. I do see this error in event logs, but it does not seem to be triggered at the same time of testing the web portal

Failed to read registry value AppParameters: The system cannot find the file specified.

Registry key AppParameters is unset for service VMBlastSG. No flags will be passed to C:\Program Files\VMware\VMware View\Server\appblastgateway\run-absg.cmd when it starts.

[vDruid]

Hi,
This is most of the time a missing configuration in locked.properties file in the Connection server:
https://docs.vmware.com/en/VMware-Horizon/2212/horizon-installation/GUID-FE26A9DE-E344-42EC-A1EE-E13...

This depends also in the fact that you have or not a LB in front of the CS or UAG

[glacius2585]

Thank you for taking the time to help me.

We went ahead and made the changes as the article suggested:

C:\Program Files\VMware\VMware View\Server\sslgateway\conf

Created a file called: locked.properties

portalHost.1=FQDN of UAG (internal Domain DNS Name)

rebooted the server.

tried again, and same issue...

There is no LB at all.

Is there any other suggestion. 

I ran the developer setting in the browser and found an error (see Dev-setting.txt)

the first thing it says "/broker/xml 404 (Not Found)"

So it has to be a connection from the UAG to the Connector server (I think)

[vDruid · Accepted solution]

Hi glacius,

you say: portalHost.1=FQDN of UAG (internal Domain DNS Name)

First, il you have only one UAG, it should be portalHost only, without the .1

Second, you mention INTERNAL FQDN of UAG. il must be the external FQDN of UAG, meaning the one you enter in the URL or the Horizon heavy client as an end-user. 

Question: which type of UAG nic mode you are using ? Single ? double ? triple ?

Finally, if the heavy client works fine and the UAG horizon edge service is green, that means you UAG->CS connection is fine.

[glacius2585]

Oh boy!

You are a genius....

It works flawlessly now.

This extra settings that you have mentioned with the lock.properties, is this a bug, or did we forget to add this setting during installation?

[vDruid]

With pleasure !
That is not a bug, it is part of the standard configuration for HTML access. Ran into this many times for several customers.
Keep in mind that if you go into production and add some LBs, you will also have to update this file accordingly.