Date: Wed, 26 Aug 2009 11:58:53 +0200 From: Frederique Rijsdijk <frederique@isafeelin.org> To: Peter Pentchev <roam@ringlet.net> Cc: FreeBSD-Ports <freebsd-ports@freebsd.org> Subject: Re: Apache SSL broken after upgrade to 2.2.13? Message-ID: <4A95075D.3070806@isafeelin.org> In-Reply-To: <20090826090517.GA982@straylight.m.ringlet.net> References: <4A94F976.5040203@isafeelin.org> <20090826090517.GA982@straylight.m.ringlet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Pentchev wrote: > On Wed, Aug 26, 2009 at 10:59:34AM +0200, Frederique Rijsdijk wrote: >> Following todays portaudit advisory, I upgraded Apache on several >> machines. On a machine that's running SSL, things broke after the >> ugprade with the following error: >> >> [Wed Aug 26 10:23:39 2009] [error] Server should be SSL-aware but has no >> certificate configured [Hint: SSLCertificateFile] >> >> The previous version was 2.2.11_5. Everything worked fine. The hint that >> apache gives is obviously configured in httpd.conf.. >> >> Rolled back to version 2.2.11_5, all is working again. >> >> Did I miss something? > > This was reported in Debian, too; it seems to be an upstream change > in Apache. I don't know what they intend to do about it, but it does > indeed "break" the setups of a lot of people who only put the SSL > certificate, key, and stuff in the virtual hosts that actually > require it. > > As a workaround, just put the SSL cert and key directives somewhere > on a global level, outside a vhost, and Apache will start. Stupid, > I know, but that's how it is for the present :/ > That doesn't work for me .. [Mon Apr 20 12:53:04 2009] [error] Illegal attempt to re-initialise SSL for server (theoretically shouldn't happen!) Weird stuff..
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A95075D.3070806>