Jason Paul McCartan wrote:
> Recently though the server was used to add other name-based virtual domains.
> Now the SSL through HTTPS is totally unavailable, and when we tried to view
> anything over HTTPS we get a blank "Page Not Found" page. We have no problem
> on port 80 for any of the sites. Initially we could hit the same site on
> HTTP and HTTPS and the SSL would activate. Now on HTTP it works fine, but we
> get that "Page Not Found" error on HTTPS.
One big trap that a lot of people fall into is that you *cannot* have
SSL name-based virtual hosts. This is basically because SSL negotiation
has to be complete before any HTTP traffic can be received - to
negotiate SSL you need the certificate, which is defined in the VH,
which is selected using the ServerName, which can only be found from
HTTP, which can't take place until SSL is established... see the
problem?
That aside, you don't actually say you are trying to run SSL VHs so you
may have a simpler solution - define the port numbers explicitly in the
NameVirtualHost and VirtualHost directives to avoid ambiguities, e.g:
NameVirtualHost 192.168.1.1:80
# HTTP host1
<VirtualHost 192.168.1.1:80>
Servername www.site1.com
</VirtualHost>
# HTTP host2
<VirtualHost 192.168.1.1:80>
Servername www.site2.com
</VirtualHost>
# SSL host
<VirtualHost 192.168.1.1:443>
Servername ssl.site1.com
</VirtualHost>
Did you get a warning message when starting the server? Check in the
common_error_log...
Rgds,
Owen Boyle.
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
