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)
- Cannot update to Plesk Obsidian 18.0.29 on Plesk for Windows: Error occured while performing sub-action 'UpgradeZip'
- Ubuntu 20.04 support in Plesk
- CVE-2020-1350 in Microsoft DNS Server: SIGRed : A remote unauthenticated attacker can run arbitrary code on behalf of SYSTEM on Windows servers
- [FIXED BUG] Plesk upgrade fails: Query failed: ALTER TABLE `pd_users` MODIFY COLUMN `login` varchar(32) NOT NULL
- [FIXED BUG] The error message appears after updating Plesk: Template domain/service/nginxSeoSafeRedirects.php doesn't exists
- Plesk is not accessible after upgrade from Plesk Onyx to Plesk Obsidian: Unable to create file: C:/Program Files (x86)/Plesk/var/locks/authorizer.lock: Permission denied
- Does Plesk support Ubuntu 20?
- Unable to update Plesk: The installation of the package 'aspnetcore-3.1' failed with code 1603
- [FIXED BUG] Plesk or "yum update" system update fails: requires libMagickCore.so.5
- Unable to update Plesk Obsidian for Windows: The required version '3.27.0' was not found on the server
- Does Plesk support CloudLinux 8?
- How to exclude a system package from update in Plesk for Linux
- 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
- 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
- Pre-upgrade warning about database users ecrypted passwords: There are XX accounts with passwords that are encrypted using an outdated algorithm
- 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
- 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
- Pre-upgrade warning message: There are 2 mail accounts with passwords encrypted using a deprecated algorithm
- Unable to download Plesk Installer to the Windows Server Core or via CLI
- 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