Summary: | Wildcard certificate with multiple name-based vhosts - not found | ||
---|---|---|---|
Product: | Apache httpd-2 | Reporter: | Jacek Chmielewski <jacek.chmielewski> |
Component: | mod_ssl | Assignee: | Apache HTTPD Bugs Mailing List <bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | 2.2.0 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | FreeBSD |
Description
Jacek Chmielewski
2006-04-04 01:01:44 UTC
The configuration should use "ServerName vhost8.mydomain.com:443" at least; not sure otherwise why this should actually fail. Can you attach the complete error_log produced at startup with "LogLevel debug" configured? No response from OP. I just saw this and happened upon this bug report. platform: debian etch i386 version: apache-2.2.3-4+etch10 In my case this appears to occur only when: * you add a new ssl'd vhost to the config * you run /etc/init.d/apache2 reload If you instead run: /etc/init.d/apache2 stop /etc/init.d/apache2 start You get the familiar warning: [warn] RSA server certificate CommonName (CN) `*.mydom.com' does NOT match server name but the server starts fine and works as expected. I noticed that the error message indicates apache thinks the vhost is listening on port 0, not port 80 or 443: Oops, no RSA or DSA server certificate found for 'site.mydom.com:0'?! Perhaps this will help tracking this down. I did not have to resort to adding the port number to the ServerName directive. |