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

Best practice for Plesk on RHEL

H

HopChop

Guest
Hello!

I have plesk 7.5.3 running on RHEL3 since a couple of weeks and it works like a charm during my testings. I'm a complete newbie to plesk and haven't used RHEL before (but other distributions of linux/unix) and have some questions. I've been browsing this forum trying to get the answers but with no luck.

1. Should I use up2date or some kind of update service for RHEL or do I break configurations made by plesk then (if I for example update apache)? I of course don't want to run a server with possible exploits, but at the same time I don't want to destoy some of the magic glue made by plesk.

2. I've read in the forum that the components in the application vault doesn't get frequent updates. Do people update the components manually, let the components be old versions or is the application vault seldom used?
 
Back
Top