Plesk 10.4.4#10 - Location of vhost.conf and vhost_ssl.conf for subdomains?

[Angels]

Plesk 10.4.4#10
Debian

I just noticed that a (working) vhost.conf and vhost_ssl.conf are totally ignored by running httpdmng.

What is the current location for the vhost.conf and vhost_ssl.conf files for subdomains in Plesk 10.4.x, or are they gone, because of the new panel settings?

I tried both locations and none seems to be working:
/var/www/vhosts/DOMAIN.TLD/subdomains/SUBDOMAIN/conf/vhost.conf
/var/www/vhosts/SUBDOMAIN.TLD/conf/vhost.conf

After running httpdmg i checked the new generated /var/www/vhosts/SUBDOMAIN.TLD/conf/xxxxx.conf file if my settings fron the vhost.conf were inclued, without success.

 

[paulojsp]

a little late...

Check this topic:
http://download1.parallels.com/Plesk/PP10/10.4/release-notes/parallels-plesk-panel-10.4-for-linux-based-os.html

In topic #19
Web hosting management tools (that change php.ini, vhost.conf, etc) are now available for subdomains.
All domain-management features are available for subdomains.
System files of subdomains are located in /vhosts/<subdomain-name>.example.com/ now, just like for a regular domain.
All limitations on putting subdomains in the subdomains/ directory were eliminated.

hope that helps

 

[HostaHost]

Of course the migration tool still often leaves vhost_ssl.conf behind regardless of the source server version, so watch out for that. Some versions of 10.x also let users create a subdomain with the content served from /dev which was disallowed in 10.4 due to the use of /dev for chrooted shells; another problem you can run into during upgrades.

Not the worst problem though; my vote for that would be the fact that subdomains can't have their own cgi-bin directory outside the subdomain's documents directory anymore, i.e. a cgi-bin that's relative to the documents directory via ../httpdocs/ like you could in every version of Plesk going back six years. In 10.4, it can either be inside the subdomain's documents directory, or it will share the cgi-bin with the primary domain, making it pretty difficult to test new versions of a site when you can no longer mimic the main site's structure.