Installation & Upgrade
Articles about Plesk components updates and upgrades including OS.
- How to update Plesk Obsidian to the latest build
- How to install Plesk for Linux
- How to upgrade Plesk to the next release
- How to install an SSL certificate for a domain in Plesk (Let's Encrypt / other certificate authorities)
- The error message appears after updating Plesk: Template domain/service/nginxSeoSafeRedirects.php doesn't exists
- [FIXED BUG] Plesk or "yum update" system update fails: requires libMagickCore.so.5
- [BUG] Unable to update Plesk Obsidian for Windows: The required version '3.27.0' was not found on the server
- How to exclude a system package from update in Plesk for Linux
- [BUG] Unable to install Plesk updates: The repository 'http://dl.google.com/linux/mod-pagespeed/deb stable Release' is not signed
- Plesk for Linux update or upgrade fails on server with Ubuntu OS: Fatal, conflicts violated plesk-control-panel:amd64
- [BUG] Plesk shows notification about failed Plesk Update: Task is not responding
- [FIXED BUG] Web Installer does not start Plesk installation on redeployed Linux server with same IP address: Installation to the host 203.0.113.2 has been already started
- [BUG] Pre-upgrade warning about database users ecrypted passwords: There are XX accounts with passwords that are encrypted using an outdated algorithm
- [BUG] Unable to upgrade Plesk to Obsidian on a Google Cloud instance: Unable to obtain the required version of Plesk Installer
- Unable to upgrade Plesk: The user specified as a definer ('root'@'localhost') does not exist
- Plesk Installer reports the warning: There are custom web server configuration templates
- [BUG] Upgrade to Obsidian fails: The installation of the package 'plesk-locale-base-en-US' failed with code -1
- The Plesk Installer page constantly refreshes with "Plesk Installer was updated" on Plesk for Windows Server
- [BUG] Pre-upgrade warning message: There are 2 mail accounts with passwords encrypted using a deprecated algorithm. These users will be able to log in to mail server with PLAIN authentication mechanism, but they will lose the ability to log in to Plesk
- [BUG] Unable to download Plesk Installer to the Windows Server Core or via CLI
- [BUG] Plesk is unavailable after upgrade from Onyx to Obsidian: mailmng-imap failed: Error: invalid command --features
- Plesk Obsidian RTM is not available for upgrade on the Updates and Upgrades page
- Upgrade Guide to Plesk Onyx
- [BUG] Unable to upgrade Plesk Onyx to Plesk Obsidian: ailed to solve dependencies: plesk-mail-pc-driver-18.0-2.centos.7+p18.0.18.1+t190909.1738.x86_64 requires postfix >= 2:3.4.5
- [BUG] Installation via Plesk Web Installer failed: It is impossible to detect the FQDN of the host
- Unable to update Plesk: RepoError: database is locked
- [BUG] Plesk Repair Kit is not installed after dist-upgrade from Ubuntu 14 to Ubuntu 16
- [BUG] Failed update from Onyx to Obsidian: plesk-mail-pc-driver-18.0-2.centos.7+p18.0.17.0+t190726.0917.x86_64 requires libmilter.so.1.0()(64bit)
- Plesk installation/update/upgrade fails: No such file or directory: '/var/cache/yum/x86_64/
- Unable to install Plesk: "version `OPENSSL_1.0.2' not found" or "version `OPENSSL_1_1_1' not found"