-1

We are using NSS as SSL engine in Apache server. Recently we applied latest SUSE Linux Enterprise server patches on Apache server which is hosting two IP based virtual hosts. After upgrade the first virtual host is working fine but the second one is not working.

Error log shows "Hostname vhost1.xxyyzz.com provided via SNI and hostname vhost2.xxyyzz.com provided via HTTP are different" when accessing vhost2.xxyyzz.com.

If we switch back to use mod_ssl the issue was gone. Obviously the issue is related to the following patches. Any help would be appreciated.

mozilla-nss 3.16.4-0.8.1 mozilla-nss-tools 3.16.4-0.8.1 apache2-mod_nss 1.0.8-0.4.9.1

user3195271
  • 29
  • 3

2 Answers2

0

Check your /etc/hosts file to see if you might be assigning the domain name to a local internal IP address or interface. This caused the same error message for me and many 400 errors. After changing /etc/hosts don't forget to restart the name service cache daemon ( service nscd restart ).

Jim DeOtter
  • 1
0

SNI isn't technically fully supported in that version of mod_nss but it has since been added: https://www.suse.com/support/update/announcement/2015/suse-ru-20150591-1.html

Saw the same error and saw it go away after applying the referenced patch.

Dan Miller
  • 1
  • 1