Kemp Support, how can we help?

The latest application delivery knowledge and expertise at your fingertips.

  1. Kemp Support
  2. Knowledge Base
  3. Applications

After Firmware update on Hozion Server getting Error 421 when going through KEMP.

Updated: 

 

Information

 

Summary:

After updating the connection server 2111.1 to 2306 and after that start getting errors causing error 421
Environment:

Product: Loadmaster

Version: Any

Platform: Any

Application: Hozion Connection Server
Question/Problem Description:

 
Steps to Reproduce:  
Error Message:
  • The UAG will send an HTTPS GET request to the Connection Server URL /favicon.ico containing the X-EUC-Health header.
  • If there is a load balancer between the UAG and Connection Servers, the health reports being sent by the UAG to the Connection Servers may fail if the X-EUC-Health headers being sent by the UAG are not being forwarded by the load balancer to the Connection Servers.
Defect Number:  
Enhancement Number:  
Cause:  
Resolution:

Previously had these settings in the locked.properties file located here:

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

Those settings were:

checkOrigin=false
enabledCORS=false

The update in the Horizon Connection server basically overrode those settings and ignored them as values. So had to add a new one to allow the UAGs to talk to the connection servers. So had to add the new config of:

allowUnexpectedHost=true

to the locked.properties file. These settings should not be required to work in environments but due to constraints in ours, so need that setting.
Workaround:  
Notes: UAG Gateway Error Messages in Horizon View Administrator Portal Dashboard (90749)
Make sure before making changes to discuss it with your Hozion Administrator once the change is approved take a snapshot of your config and then proceed with changes.

As it's not part of the Loadmaster config, so make changes after your commit to this setting. 
Was this article helpful?
2 out of 2 found this helpful

Comments

Avatar

Rico Roodenburg

Hi,

Great article, it has helped me a lot for solving the 421 problem.

Please don’t call it ‘Firmware update’. It’s just a update.

Another better solution will be:
Add the IP-address of the External Tunnel URL, which is given in the UAG configuration, as follows in the locked.properties;
portalHost.1=ip-address

0
In this document