Comments on: Creating Apache SSL Certificated webserver http://sickofmusic.com/2006/07/04/creating-apache-ssl-certificated-webserver/ Lifestyle, Music, Technology Wed, 07 Jan 2009 06:58:10 +0000 http://wordpress.org/?v=2.0.2 by: http://www.arts.hobsons.com/thread.jsp?topicid=302 http://sickofmusic.com/2006/07/04/creating-apache-ssl-certificated-webserver/#comment-55446 Fri, 14 Sep 2007 19:20:36 +0000 http://sickofmusic.com/2006/07/04/creating-apache-ssl-certificated-webserver/#comment-55446 <strong>http://www.arts.hobsons.com/thread.jsp?topicid=302...</strong> how to get harder erections... http://www.arts.hobsons.com/thread.jsp?topicid=302…

how to get harder erections…

]]> by: Scott Gunsaullus http://sickofmusic.com/2006/07/04/creating-apache-ssl-certificated-webserver/#comment-48450 Tue, 28 Aug 2007 20:24:58 +0000 http://sickofmusic.com/2006/07/04/creating-apache-ssl-certificated-webserver/#comment-48450 After following your instructions to the letter, I get the following: <code> * Forcing reload of apache 2.0 web server... [Tue Aug 28 16:14:41 2007] [error] (EAI 2)Name or service not known: Cannot resolve host name *.443 --- ignoring! apache2: Could not determine the server's fully qualified domain name, using 127.0.1.1 for ServerName [Tue Aug 28 16:14:42 2007] [error] (EAI 2)Name or service not known: Cannot resolve host name *.443 --- ignoring! apache2: Could not determine the server's fully qualified domain name, using 127.0.1.1 for ServerName </code> From what I've read elsewhere, this has to do with the fact that Apache2 does not support virtual hosts in SSL. Rather, it's SSL that doesn't work with name based virtual hosts. You're supposed to use IP based virtual hosts, because Apache can't accept *.443, or so they say... After following your instructions to the letter, I get the following:

* Forcing reload of apache 2.0 web server...
[Tue Aug 28 16:14:41 2007] [error] (EAI 2)Name or service not known: Cannot resolve host name *.443
--- ignoring!
apache2: Could not determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
[Tue Aug 28 16:14:42 2007] [error] (EAI 2)Name or service not known: Cannot resolve host name *.443
--- ignoring!
apache2: Could not determine the server's fully qualified domain name, using 127.0.1.1 for ServerName

From what I’ve read elsewhere, this has to do with the fact that Apache2 does not support virtual hosts in SSL. Rather, it’s SSL that doesn’t work with name based virtual hosts.

You’re supposed to use IP based virtual hosts, because Apache can’t accept *.443, or so they say…

]]>