• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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