httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik Andersson" <>
Subject [users@httpd] RE: [SPAM: ] - RE: [users@httpd] Generating self-signed key doesn't work? - Email found in subject
Date Wed, 31 Mar 2004 09:07:29 GMT
Thanks for your help. I have a few questions regarding this though.

When I added the SSLLog parameters to the ssl.conf I got a error telling
me to use error log instead since SSLLog no longer was supported. I am
using apache 2.0.43. I did set the LogLevel to debug though.

I don't understand what you mean with me being wrong using
and If I want to access my servers using aren't that the way to do it??

I replaced NameVirtualHost with NameVirtualHost * and
got a lot of errors:
[Wed Mar 31 10:36:12 2004] [warn] VirtualHost overlaps with
VirtualHost, the first has precedence, perhaps you
need a NameVirtualHost directive
[Wed Mar 31 10:36:12 2004] [warn] NameVirtualHost *:0 has no

*sigh* This is taking all of my time and I seem to be stuck.. 

Regards / Erik

-----Original Message-----
From: Boyle Owen [] 
Sent: den 30 mars 2004 16:55
Subject: [SPAM: ] - RE: [users@httpd] Generating self-signed key doesn't
work? - Email found in subject

> -----Original Message-----
> From: Erik Andersson []
> Yes. I restarted the server after applying the changes. The
> server responds with http on both port 80 and 443.

I don't think your SSL VH is starting up. I think your requests on port
443 are being answered by one of your name-based VHs. Please try the
following to tidy things up:

- remove <IfDefine SSL> and </IfDefine SSL> from ssl.conf so SSL
directives are always loaded.
- remove <IfModule ssl_module> and </IfModule> from httpd.conf so is always loaded.
- in ssl.conf, in the SSL VH, add

	SSLLog logs/ssl_log
	SSLLogLevel debug

	to activate verbose SSL logging

- in httpd.conf, replace 



	NameVirtualHost *

- in httpd.conf, replace



	<VirtualHost *:80>

	(this was wrong anyway - you're not supposed to use FQDNS with
VH. Use only IPs or wildcards.) 
- restart the server and look in logs/ssl_log to see what is generated.
Also look in the error log after start up or if startup fails. 

- try a HEAD request to see what is loaded in the running server:

	telnet localhost 80
	HEAD / HTTP/1.0 <rtn><rtn>

Owen Boyle
Disclaimer: Any disclaimer attached to this message may be ignored. 

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message