Why you need it
A while ago I wrote about the regular vhost.conf file and getting Plesk to recognize this file once created. Read more about that here. Recently I ran into a similar issue with vhost_ssl.conf. This file tells Plesk where to look instead of httpsdocs folder. In Plesk 11, the httpsdocs folder is no longer used and all files secure or not are stored in httpdocs. This really makes more sense and is what most users would do anyway by creating a symbolic link between the two.
What if you are using a subdirectory? The problem here is that Plesk will look in the root httpdocs folder for https:// and branch out from there. But for http:// Plesk will look where vhost.conf points to. The solution is a vhost_ssl.conf file to forward requests to the correct (or different) folder.
This doesn’t seem at all necessary, unless you’re using WordPress or another CMS and want to keep it in it’s own folder. Your config file should use the same structure as normal even though it’s for SSL.
The config File
DocumentRoot /var/www/vhosts/niagaraschool.com/httpdocs/wordpress <Directory /var/www/vhosts/niagaraschool.com/httpdocs/wordpress> Order allow,deny Allow from all AllowOverride all Options +Indexes Options +FollowSymLinks </Directory>
Save this file in the conf folder of your root directory alongside vhost.conf
Don’t forget to tell Plesk to add the new config file
This is the part I always forget. Initialize for one specific domain.
/usr/local/psa/admin/sbin/websrvmng -u --vhost_ssl-name=domain.com
Initialize all vhost.conf files for all domains.