Kemp Support, how can we help?

The latest application delivery knowledge and expertise at your fingertips.

Virtual service returning "HTTP Error. The request hostname is invalid."

 

Information

 

Summary:

A new SubVS was created, when the user accesses the site it returns:

HTTP Error. The request hostname is invalid

Environment:

Product: Loadmaster

Version: Any

Platform: Any

Application: IIS

Question/Problem Description:

 

Steps to Reproduce:  
Error Message: HTTP Error. The request hostname is invalid
Defect Number: PD number
Enhancement Number: Kemp ideas number, if one exists.
Cause:  
Resolution:
  • The new SubVSwas returning "HTTP Error 400. The request hostname is invalid."
  • TheReencryption SNI Hostname was set to match on the hostname of the first SubVS. Once this was changed to the hostname of the new SubVS, the new SubVS began working as expected.
  • This would indicate that the Real Server is requiring the SNI Hostname which can be disabled on the server itself.
  • If you rather not disable this on the server, you can upgrade the firmware to 7.2.52 and above.  Older firmware versions do not have the ability specify more than one SNI Hostname.  The newer versions would allow you to either passthrough the SNI Hostname or this can be specified per SubVS.
Workaround:  
Notes:

https://support.kemptechnologies.com/hc/en-us/articles/201814885-Server-Name-Indication-SNI-

https://support.kemptechnologies.com/hc/en-us/articles/115001659626-How-To-Re-Encrypt-Multiple-SNIs


Was this article helpful?
0 out of 0 found this helpful

Comments