• 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 Version Problem and restore

C

Cindy L

Guest
My company has bought the Plesk 8.1 product about 3 years ago,
and didn't do any upgrade since then.

As the domains has nearly reach the maxiumum number,
we would like to carry out on the Plesk restore progress test
on other servers, in order to have a quick response to our cusomters
for any unpredictable accident.

There are several doubts i would like to seek for your team's answer
1) Would Plesk 8.1 support with Fedora 11 or higher version above?
since all our new company server has been upgraded to Fedora 11.
2) If Plesk 8.1 does not support Fedora 11, which is the highest Version
of Fedora would be support?
3) Is Plesk 8.1 License can be used in Plesk 9.5?
as i understand Plesk 9.5 does support Fedora 11.
4) If I would do an upgrade on Plesk, e.g. upgrading Plesk 8.1 to Plesk 9.5,
would there any attention or risk should be raised when i doing the restore progress?
Is there any document i could follow on such restore progress?

Thanks
 
Back
Top