[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
Hi Kevin,I think the point being missed is each HTTPS site needs a separate IP address (or IP address, port, combination, but it is easier to use IP address).
We have servers at work with multiple HTTPS sites, and multiple virtual hosts, and it can get quite confusing as to how Apache is configured.
Listen 80 Listen 443 NameVirtualHost a.b.c.d:80Then the "virtualhost" statement in each site should explicitly state the IP address and port being used by each site.
I'm guessing you've enabled "NameVirtualHost" on the IP address you have the HTTPS site on, which will just confuse things.
You can just alias an extra IP on the webserver, stick all the HTTPS stuff on that, and keep it separate. Probably have to do some port forwarding on the firewall if you only have one public IP address to play with.
-- The Mailing List for the Devon & Cornwall LUG Mail majordomo@xxxxxxxxxxxxx with "unsubscribe list" in the message body to unsubscribe. FAQ: www.dcglug.org.uk/linux_adm/list-faq.html