Article ID: 234, created on Oct 6, 2008, last review on Jun 17, 2016

  • Applies to:
  • Plesk 12.5 for Linux
  • Plesk 12.0 for Linux
  • Plesk 11.0 for Linux
  • Plesk 11.5 for Linux


Yes, it is safe, and moreover, we recommend using package managers (for example, "yum" on RedHat-based systems, or "apt-get" on Debian-based systems) to keep the system up-to-date.

However, some packages may conflict with Plesk or another software. These packages can be added to a skip list. The recommended settings are:

  • for up2date, add to /etc/sysconfig/rhn/up2date:

  • for yum, add to /etc/yum.conf:

     exclude=kernel* sendmail bind-chroot caching-nameserver
  • for apt-get, execute with:

    sudo apt-mark hold <package>

    or, using dpkg

    echo <package> hold | sudo dpkg --set-selections

    To find out which actions should be taken after an Apache upgrade on a Plesk system, see the following KB article:

    #762 Is it possible to upgrade Apache to the latest version from an OS update?

If Plesk is installed inside a container, the kernel updates are not necessary - the kernel should be upgraded from the Hardware Node.
If Plesk is installed on a hardware server, the kernel updates are recommended if there are only vendor's repositories configured. Otherwise, if the custom repositories provide new kernels, it is better to have the kernel manually updated from the vendor's repository. The reason is simple: major troubles are caused by kernels with GRSecurity patches applied. Plesk is not designed for working with such configurations.

Search Words

package manager

system package

packages updates

package update

yum update

keep the system up-to-date.


29d1e90fd304f01e6420fbe60f66f838 a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c 2a5151f57629129e26ff206d171fbb5f e335d9adf7edffca6a8af8039031a4c7 01bc4c8cf5b7f01f815a7ada004154a2 0a53c5a9ca65a74d37ef5c5eaeb55d7f aea4cd7bfd353ad7a1341a257ad4724a 742559b1631652fadd74764ae8be475e

Email subscription for changes to this article
Save as PDF