----- Original Message ---- > Thank you for taking the time to write Stroller. This has really got > my head spinning. First of all, you're right about the netmask. It > is 255.255.255.248. I didn't have a good understanding of what a > netmask is so I thought it would be smart to change it for a public > message. > > The server is remote and hosted so I don't have any control over the > router or network. I've gone back and forth with the host but they > insist that everything is fine on their end. > > I'm confused because I have in apache2 config: > > <VirtualHost 1.2.3.1:443> > ... > SSLCertificateFile /etc/apache2/ssl/www.example1.com.crt > SSLCertificateKeyFile /etc/apache2/ssl/www.example1.com.key > ... > </VirtualHost> > <VirtualHost 1.2.3.2:443> > ... > SSLCertificateFile /etc/apache2/ssl/www.example2.com.crt > SSLCertificateKeyFile /etc/apache2/ssl/www.example2.com.key > ... > </VirtualHost> > > But if I request https://1.2.3.2 or https://1.2.3.2:443, I'm presented > with an SSL cert that has www.example1.com for the Common Name. I > used openssl to verify that the Common Name for www.example2.com.crt > is www.example2.com. >
I would suggest setting up separate access and error logs for each virtual host so you can see who is actually getting the connection, and then going from there. That will probably point out your real problem. Ben
