Hello, I recently updated mod_nss from mod_nss-1.0.3-8.el5.i386 to mod_nss-1.0.8-3.el5.i386. I initially had the issues related to permissions and the post install script. However, I changed the permissions and ensured that the group apache runs as could read the various dbs it needed to. However, now, I'm getting this on any vhosts that are configured to use NSS: [Thu Feb 24 21:05:47 2011] [error] SSL Proxy: I don't have the name of the host we're supposed to connect to so I can't verify that we are connecting to who w e think we should be. Giving up. [Thu Feb 24 21:05:47 2011] [error] (20014)Internal error: proxy: pass request body failed to <a href="http://10.68.176.1:443">10.68.176.1:443</a> (<a href="http://hostname.domain.net">hostname.domain.net</a>) [Thu Feb 24 21:05:47 2011] [error] proxy: pass request body failed to <a href="http://10.68.176.1:443">10.68.176.1:443</a> (<a href="http://hostname.domain.com">hostname.domain.com</a>) from 10.69.140.61 () [Thu Feb 24 21:06:00 2011] [error] SSL Proxy: I don't have the name of the host we're supposed to connect to so I can't verify that we are connecting to who w e think we should be. Giving up. [Thu Feb 24 21:06:00 2011] [error] (20014)Internal error: proxy: pass request body failed to <a href="http://10.68.176.1:443">10.68.176.1:443</a> (<a href="http://hostname.domain.net">hostname.domain.net</a>) [Thu Feb 24 21:06:00 2011] [error] proxy: pass request body failed to <a href="http://10.68.176.1:443">10.68.176.1:443</a> (<a href="http://hostname.domain.net">hostname.domain.net</a>) from 10.69.140.61 () (Please note that "<a href="http://hostname.domain.net">hostname.domain.net</a>" in there was the FQDN of the host related to the IP address before it...which was correct in where it is being proxy passed to. Here is a sample configuration for each vhost: <VirtualHost *:10480> DocumentRoot "/var/www/html" ServerName <a href="http://server.domain.com">server.domain.com</a> AllowConnect 10480 NSSProxyEngine on NSSEnforceValidCerts on NSSProxyCipherSuite -rsa_rc4_128_md5,-rsa_rc4_128_sha,+rsa_3des_sha,-rsa_des_sha,-rsa_rc4_40_md5,-rsa_rc2_40_md5,-rsa_null_md5,-rsa_null_sha,+fips_3des_sha,-f ips_des_sha,-fortezza,-fortezza_rc4_128_sha,-fortezza_null,-rsa_des_56_sha,-rsa_rc4_56_sha,+rsa_aes_128_sha,+rsa_aes_256_sha NSSFIPS on <Location /service/ > Order Deny,Allow Deny from all Allow from all ProxyPass <a href="https://hostname.domain.com:443/service/">https://hostname.domain.com:443/service/</a> ProxyPassReverse <a href="https://hostname.domain.com:443/service/">https://hostname.domain.com:443/service/</a> </Location> And the hostname in the ProxyPass/ProxyPassReverse does translate to the IP listed in the logs. Rolling back to the old version resolves the issue. I'm admittedly learning mod_nss as I go about this, but haven't been able to figure this issue out. LogLevel is debug, but I have no other errors or info to go on. From searches, I've seen suggested that there may be an issue with shared libraries if mod_ssl is loaded as well...so I've verified that mod_ssl is not being loaded. Any info that can be provided would be greatly appreciated. Thanks! Erica