In article <[EMAIL PROTECTED]> you wrote:
> I have enabled the entire apache webserver
> I am trying to run with mod-ssl, using the SSLEnable keyword, however
> it generates this error in the error_log:
> [Wed Sep 16 10:40:56 1998] [error] mod_ssl: No SSL Certificate set
> for server www.moment.net:8080 [hint: SSLCertificateFile]
> However I do have the certificate in the proper place:
> SSLCertificateFile /www/web/secure/etc/apache/ssl.crt/server.crt
> I generated the .crt file based on the mod-ssl instructions and signed
> it using my own CA.
> I am using mod_ssl-2.0.9-1.3.1 and Apache 1.3.1
You say you have SSL enabled for the entire server? I assume you mean you
have an SSLEnable inside the main server context (i.e. outside the
<VirtualHost> sections). This is only ok when you don't use "Port 80" at the
same time. And you have to move the SSLCertificateFile directive to the same
context, i.e. outside any <VirtualHost> sections. OTOH there is usually no
reason why one enables SSL in the main server. Using a <VirtualHost> is
always ok, even when you run only one server. For instance my webservers run
even the "main" (i.e. my standard) server inside a <VirtualHost>. Because
this way your main server config isn't inherited by the <VirtualHost>, etc.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
