• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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