Installation & Upgrade

Articles about Plesk components updates and upgrades including OS.

Unable to install or update Plesk on CloudLinux OS: The Yum utility failed to install the required packages
Upgrade to Plesk Obsidian or update between Obsidian releases fails: TypeError: an integer is required
Installation of Plesk via Plesk Web Installer fails: Could not connect to the target server. Process exited with status 1
How to install Plesk on Linux with specific pre-installed MySQL/MariaDB version
Unable to install Plesk via Try For Free Web Installer: Could not connect to the target server: no such host
Discontinued support of features and components in Plesk Obsidian 18
Plesk and CLI utilities are not working: HTTP 500 error
Debian 10 support in Plesk
Unable to update Plesk: The required version '3.20.19' was not found on the server.
Plesk installation/update/upgrade fails: No such file or directory: '/var/cache/yum/x86_64/
Plesk Installer fails: The installation of the package 'aspnetcoremodule' failed with code 1603
Unable to remove a broken PHP handler in Plesk
Unable to upgrade Plesk: backup is created with insecure permissions
Unable to use Plesk login command or install/update extensions after interrupted Plesk upgrade: error while loading shared libraries
Unable to install Plesk via Web Installer: unable to parse private key: ssh: no key found
Unable to install system updates or update Plesk: Another app is currently holding the yum lock
How to exclude a system package from update in Plesk for Linux
Plesk Upgrade fails: Sub-action 'InstallMsiPackage' failed with error code: 1603(0x00000643) Could not open input file: C:\Program Files (x86)\Plesk/admin/plib/scripts/update-failure-notification.php
Unable to update Plesk: The installation of the package 'git' failed
Plesk update/installation fails: The MD5 checksum of the plesk-nssm.zip.tmp file does not match the value specified in the configuration file
Unable to update Plesk Obsidian for Windows: The required version '3.27.0' was not found on the server
Unable to update Plesk: The installation of the package 'aspnetcore-3.1' failed with code 1603
Plesk interface is not working after Plesk upgrade: "TypeError: Cannot read property" or "404 Page Not Found"
Unable to install Plesk via Web Installer: handshake failed: ssh: unable to authenticate, attempted methods [none password], no supported methods remain
Why "plesk login" command generates links like "192-0-2-2.plesk.page"?
Is it possible to update "curl" on Centos 7 or Ubuntu 18.04 server with Plesk?
System update warning: Target Packages (...) is configured multiple times in /etc/apt/sources.list.d/plesk-ext-panel-migrator.list
Can't install or update Plesk: there is no product with the ID 'plesk' at the installation source
Plesk upgrade failed: The installation of the package 'aspnetcore-3.1' failed
How to manage Plesk autoupdates date and time