What distro are you running? On Red Hat et al, the SSL configuration is
usually found in /etc/httpd/conf.d/ typically as ssl.conf.
Curt
On Fri, Feb 26, 2010 at 9:17 AM, Bruce W. Martin marti...@gmail.com wrote:
I have a server with two NICs on different IP addresses hosting two Virtual
hosts
We ran into a problem with our SuSE server a while back, when we installed
an SSL certficate. The server had two NICs and we had to configure one of
the SSL lines to *:443 so it would listen on all interfaces.
Perhaps you're having a similar issue?
Chris
On Fri, Feb 26, 2010 at 9:17 AM, Bruce
On Feb 26, 2010, at 9:20 AM, Curt Lundgren wrote:
What distro are you running? On Red Hat et al, the SSL configuration is
usually found in /etc/httpd/conf.d/ typically as ssl.conf.
Curt
RHEL 4. Yes, there is a /etc/httpd/conf.d/ssl.conf file but I don't think it is
being used as I changed
On Feb 26, 2010, at 9:24 AM, Chris McQuistion wrote:
We ran into a problem with our SuSE server a while back, when we installed
an SSL certficate. The server had two NICs and we had to configure one of
the SSL lines to *:443 so it would listen on all interfaces.
Perhaps you're having a
Does it play right if you disable SELinux?
What version of Apache?
Was everything working correctly before the second cert?
Any other changes between working correctly and busted?
Bill
On Fri, Feb 26, 2010 at 10:35 AM, Bruce W. Martin marti...@gmail.comwrote:
On Feb 26, 2010, at 9:24 AM,
On Feb 26, 2010, at 9:55 AM, Bill Woody wrote:
Does it play right if you disable SELinux?
Don't know as I am not inclined to do this on this production system.
What version of Apache?
2.2.14
Was everything working correctly before the second cert?
Yes
Any other changes between working
I believe the default behavior of Apache is to load anything in the
/etc/httpd/conf.d/ directory that has a .conf extension. You might try
moving the ssl.conf file somewhere else.
Curt
On Fri, Feb 26, 2010 at 9:28 AM, Bruce W. Martin marti...@gmail.com wrote:
On Feb 26, 2010, at 9:20 AM, Curt
On Fri, Feb 26, 2010 at 10:35 AM, Curt Lundgren verif...@gmail.com wrote:
I believe the default behavior of Apache is to load anything in the
/etc/httpd/conf.d/ directory that has a .conf extension. You might try
moving the ssl.conf file somewhere else.
I wouldn't assume that it's the default
Thank-you for everyone who pitched in on this. Curt was pretty much right on
this. I had changed the filename for /etc/httpd/conf.d/ssl.conf to
notthis.ssl.conf and apache was still picking up on it. when I changed it to
ssl.conf.notthis apache failed to start which told me it actually was