• 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.

Plesk Migration manager bug

Tozz

Regular Pleskian
I noticed a bug in Plesk when migrating from Plesk to Plesk. The new machine is Plesk 8.6.

When a vhost.conf configuration file exists on the old server this file is copied by the Plesk migration manager. However, the vhost.conf file is not included in the httpd.include file. As a result any hand-made configuration change is not included in the Apache webserver.

As a workaround you can run /opt/psa/admin/bin/websrvmng -a

I did not find any suitable place for a bug report. Is there any?
 
Here is the info I have on the process

If possible defect found in Parallels software, please send an e-mail to [email protected] with detailed description of what and how happens with our software and what steps should be taken to reproduce this defect, to have it examined by our Development Team.
 
Back
Top