Installation & Upgrade
Articles about Plesk components updates and upgrades including OS.
- How to update Plesk Obsidian to the latest build
- How to perform dist-upgrade procedure on Linux server with Plesk?
- 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)
- How to change or get the server hostname on the Plesk server
- Which ports should be opened in the firewall on a Plesk server
- After upgrading Plesk Obsidian to 18.0.30, scheduled Plesk backups show the message: The following files were not found or were corrupted: backup_privatekey_2009210501.tgz
- [FIXED BUG] 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
- Cannot install Plesk update on CentOS 7: Failed to solve dependencies: plesk-core requires ca-certificates >= 2020.2.41
- CVE-2020-1350 in Microsoft DNS Server: SIGRed : A remote unauthenticated attacker can run arbitrary code on behalf of SYSTEM on Windows servers
- Unable to install Plesk: there is no product with the ID 'plesk' at the installation source
- [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
- System update shows warning on Plesk server: Target Packages (...) is configured multiple times in /etc/apt/sources.list.d/plesk-ext-panel-migrator.list
- 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
- Unable to install Plesk via Web Installer: handshake failed: ssh: unable to authenticate, attempted methods [none password], no supported methods remain
- Plesk is broken: TypeError: Cannot read property 'map' of undefined
- 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
- Plesk Installer or Repair Kit report the warning: There are custom web server configuration templates