You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2009/11/15 22:37:44 UTC
DO NOT REPLY [Bug 39192] Wildcard certificate with multiple
name-based vhosts - not found
https://issues.apache.org/bugzilla/show_bug.cgi?id=39192
--- Comment #3 from vincent.mcintyre@atnf.csiro.au 2009-11-15 13:37:41 UTC ---
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.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org