• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Subdomains with custom Apache configuration broken after upgrade to Plesk 10

breun

Golden Pleskian
After upgrading from Plesk 9.5.4 to 10.4.4 the vhost.conf and vhost_ssl.conf files for subdomains were not moved to the correct locations, which caused these domains to no longer work.

Example:

On Plesk 9.5.4 there was a subdomain 'sub' of example.com in /var/www/vhosts/example.com/subdomains/sub. This subdomain had a vhost.conf and vhost_ssl.conf in the /var/www/vhosts/example.com/subdomains/sub/conf directory and all was fine.

After upgrading to Plesk 10.4.4 a new directory /var/www/vhosts/sub.example.com was created and configuration should now be in /var/www/vhosts/sub.example.com/conf instead of /var/www/vhosts/example.com/subdomains/conf (although the subdomain's document root is still /var/www/vhosts/example.com/subdomains/sub/httpdocs).

It seems that the Plesk upgrade process does not correctly handle moving these configuration files for subdomains when upgrading from Plesk 9 to Plesk 10.
 
Last edited:
Back
Top