SSL for single domain on shared ip

[AndrewJA]

After some reading on the above subject, I'm still left a little confused and would like some advice.

Plesk Panel 11.5.30, on Centos 5.10.
I have 2 'domains' running on the same ip; sub.mysite.com and mysite.com.
I need to add SSL to sub.mysite.com.

From the documentation, http://download1.parallels.com/Ples...inistrator-guide/index.htm?fileName=68308.htm, it appears that if the user is using a SNI compatible browser a single SSL certificate for sub.mysite.com should work (as I am using a linux server, SNI is enabled by default I believe).

However, the control panel for the domain (website & domains > hosting settings) states that "To employ SSL, move this site to a dedicated IP address, install an SSL certificate on the site, and then select it below."
In addition, other documentation makes reference to a "Secure your sites" link on the control panel to implement a purchased SSL certificate, which is not visible to me - I presume because the domain is not on a dedicated ip address.

Can someone confirm that;
a) a SSL certificate for sub.mysite.com on a shared ip will work.
b) that the SSL for sub.mysite.com would managed at the server level (Server Management > Tools & Settings > SSL Certificates) rather than the domain's control panel.

One alternative may be to purchase a wildcard SSL certificate (*.mysite.com). This post http://forum.parallels.com/showthre...-unique-Subscriptions&highlight=ssl+shared+ip suggests that this would work. However, this is a more costly option and does more that I need (i.e. delivers SSL for all domains).

I could also purchase a dedicated ip address for sub.mysite.com. I have no experience of moving domains within plesk from a shared ip to a dedicated ip.
Is this a straightforward process?

Thanks in advance
-Andrew

 

[AndrewJA]

In the absence of any replies, I decided to purchase an additional ip for my server and move the domain to this new dedicated ip.
All very straightforward to do using Plesk panel.

The only glitch was that the new ip wasn't listening on port 443, so I was getting "connection refused" messages.

To resolve, I edited /etc/httpd/conf.d/ssl.conf and added the explicit instruction for apache to listen on port 443 on my new ip - perhaps this should be documented somewhere as plesk panel gives the impression that all is taken care of (i.e. tick the box that ssl is required for the domain)?