Handling HTTPS to all domains sensibly

[JasonJ]

When I attempt to access any domain through HTTPS, I just get the contents of the main domain for the server. I would like to be able to access any domain (and sub-domain or alias) through HTTPS.

I realise the certificate will be wrong for any domain except the main domain, but at the moment it is not just the certificate, but the whole website delivered that is not consistent with the domains being accessed.

All my domains are configured with SSL and to use the same location for SSL and non-SSL. However, those settings are being completely ignored. I can see the port-443 entries being created in the domain apache configuration files though, and those entries look correct, so I am guessing there is an overriding http config file that gets in early with port 443 requests.

Any idea what I need to change for this to work in a more sensible way, i.e. to deliver the correct website for a domain across all ports?

-- Jason

Plesk 8.6

 

[JasonJ]

I have discovered the "httpd -S" option that shows how all the ports and IP addresses are handled. So far as I can see, the default port 443 is handled by the main domains for each IP, but then each additional domain that has the "use SSL" boxed ticked in Plesk is also set up to handle port 443. The trouble is, those domains never get to handle that port. I really cannot see why.