[Savannah-hackers] Re: URGENT: apache stuck in subversions

[Jaime E . Villate]

On Tue, Aug 06, 2002 at 05:01:06PM -0400, Paul Fisher wrote:
> I created a new cert and apache-ssl is running now.  I don't know if
> it was refusing to start because the old one had expired.

Thanks a lot Paul. Yes, the problem was that the olld one had expired. I
had also created a new one (apache.pem.new) and replaced the old one
(apache.pem) with it, but for some reason it didn't work for me.

> I also changed your bit of data in httpd.conf:
> 
> <VirtualHost 199.232.41.2>
> ServerName freesoftware.fsf.org
> SSLDisable
> </VirtualHost>
> 
> I added the SSLDisable.  Also note that freesoftware.fsf.org points to
> 199.232.41.3, so this VirtualHost will never get used.

OK, you've just answered what I was trying to figure out when apache got
stuck: since subversions listens both on 199.232.41.2, 199.232.41.3 I thought
the above directive might work.
About the SSLDisable, I did not put it because I want both
http://freesoftware.fsf.org and https://freesoftware.fsf.org to work
I was next going to put something such as

<VirtualHost 199.232.41.3:80>
ServerName freesoftware.fsf.org
SSLDisable
</VirtualHost>

Should we have two different certificates, one for savannah.gnu.org and
another one for freesoftware.fsf.org?

Cheers,
Jaime