• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

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