Hi,
I upgraded our web server last week from Apache 1.2 to
mod_ssl-2.2.8 apache_1.3.6 openssl-0.9.2b HP-UX B.10.20
The old httpd.conf was quite large due to a lot of virtual ip hosts. Some
of which were SSL. I copied it across and cleaned it up to go with the new
layout from httpd.conf.default.
Now, on the real ip of the server we have have port 80 & 443 available.
And this works fine (80 & 443).
DocumentRoot /path/to/doc/root
Port 80
Listen 80
Listen 443
<VirtualHost real_ip:443>
SSLEngine on
</VirtualHost>
However _any_ another virtual host that lies on port 443 causes the
browser to hang when it connects, eventually my netscape replies with...
'There was no response. Ther server could be down or is not responding'
Any ideas?
Yes I....
1) run with -DSSL
2) Have Listen 443
3) Have SSLEngine on
I know that 1 & 2 work because SSL works on the real_ip address. The real
ip is using the default ip from section 1 of the httpd.conf adn the
default certs too. Could there be something there that is messing up the
others? I used s_client to test the others but it timed out with
$ s_client -connect not_working_ip:443 -state -debug
connect: Connection timed out
connect:errno=238
I looked over the mailing list archive at www.progressive-comp.com but
couldn't find anything that pin pointed this problem exactly.
---------------------------------------------------------------------------
the idea here being eventually have my own ship/boat, an old minesweeper
would be great, and do trips etc,...then stock up on weaponry and do a
sly job on the south sea pirates. I can see it now, innocent looking
older ship takes on pirates and reveals a hidden agenda.
---------------------------------------------------------------------------
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
