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

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

HTTP Error 400. The request hostname is invalid

Product: LoadMaster

Version:7.2.48.3

Platform: VMware

Application: IIS

Why is the new service returning:

HTTP Error 400. The request hostname is invalid

• The new SubVS was returning "HTTP Error 400. The request hostname is invalid."
• The Reencryption 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.

• Disable the Require Server Name Indication option on the Real Server
• Disable re-encryption on the LoadMaster

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