• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Correct way to uprade from plesk 9.5.x to 11.x

ProWebS

Regular Pleskian
Hello,

we have several servers still with Plesk 9.5.x

the reasond we haven't upgraded yet is because of the change of the addional domains in Plesk 10/11.

The biggest problem which I dont know how to solve is the above:

we have some packages in which the customer can user more than 1 domains, for example lets say "package5" which can have totally 5 domains.
In Plesk 9.5 there is 1 client and 5 domains under this client, and if the client has 1GB of disc space in total on the Resources,
then the Resources of each of the five domains are setup with 200MB.

If we do an upgrade on Plesk it will convert each 5 domains into 5 separate packages which ofcouse is wrong because they belong to 1 client.

The correct way would be to convert it in a way so taht there would be 1 client, with 1 main domain, and the rest 4 domains would be converted to addons.
The question is , how is this possible?
What is the workarround?
What can I do ?
 
Plesk 11 can be a bit confusing. Here is what i would do:

make every domain a subscription
create the client as customer
subscribe those 5 subscriptions to that customer

regards
Jan
 
Back
Top