Date: Tue, 5 Jun 2007 12:00:46 -0500 From: "Hugh Messenger" <hugh (at mark) alaweb.com> Subject: [coba-e:10007] SSL VirtualHost To: <coba-e (at mark) bluequartz.org> Message-Id: <013401c7a793$10b9c670$010210ac@DELLBOY> X-Mail-Count: 10007I hate to bump my own questions like this, but I've hit a brick wall here. To summarize . for some reason (probably to do with the recent Centos updates) my BQ server has quit building the VirtualHost directives for sites using certificates. It will create a self-signed cert or import a CA cert, and correctly place them in the site homedir. But it doesn't build the httpd.conf magic to actually start listening on port 443 for that site. On an older 550 machine, I can see where that stuff is done using some <perl> which builds it on the fly in the httpd.conf. But that's all Apache1-centric, and the BQ box is obviously Apache2. Unfortunately, I only have the one BQ server, so I don't have a "known good" baseline to look at. I've worked round the problem, by manually entering the necessary config lines into httpd.conf. Which works fine,, but I really would like to bring the automated process back to life. Does anyone have any idea where BQ is supposed to build the <VirtualHost x.x.x.x:443> directives for SSL enabled sites? -- hugh10007_2.html (attatchment)(tag is disabled)