Installation & Upgrade
Articles about Plesk components updates and upgrades including OS.
- Installation of Plesk via Plesk Web Installer fails: Could not connect to the target server. Process exited with status 1
- Upgrade to Plesk Obsidian or update between Obsidian releases fails: TypeError: an integer is required
- Unable to install or update Plesk in CloudLinux: The Yum utility failed to install the required packages
- Unable to update Plesk: Failed to fetch URL. Some index files failed to download
- Unable to install packages on Digital Ocean Ubuntu 18 droplet: Could not find /boot/grub/menu.lst file
- Unable to install Plesk license: Key Update Status: No properly formed ip addresses
- [FIXED BUG] sasl2-bin update error on Plesk server: dpkg: error processing package sasl2-bin (--configure)
- Plesk update on Debian or Ubuntu fails: E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem
- Unable to update Plesk: Migration failed: 17.0.10/xxxxxxx_insert_row_admin_preferences_update_to_actions.php
- Unable to install Postfix on a Debian/Ubuntu-based distribution: The following packages have unmet dependencies: Conflicts: mail-transport-agent
- Installation of Plesk updates fails: ERROR: Failed to run the Yum utility. The Yum utility failed to install the required packages
- Does Plesk support Windows Server 2019?
- Plesk installer does not show upgrade option
- Plesk is not accessible after faulty upgrade: Unable check file existence: Unable to convert a string to SID: (1337) The security ID structure is invalid
- Unable to install MSSQL 2017 from Plesk Installer: Error: The installation of the package 'sql2017_express' failed
- Unable to install or update Plesk: Operation too slow. Less than 500 bytes/sec transferred the last 30 seconds
- Plesk Update fails: mssql-tools : Depends: msodbcsql17 (>= 17.2.0.0) but 17.1.0.1-1 is to be installed
- Unable to update Plesk: Unpacking of archive failed on file /etc/httpd/logs: cpio: rename failed - Is a directory
- Unable to open Plesk after upgrade: The executed process was terminated because of unhandled signal received from the system
- Plesk update fails: GPG error: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY
- Unable to update/upgrade Plesk: The installation of the package '<package_name>' failed with code 1603
- How to upgrade MS SQL Server on Plesk server?
- Plesk UI is stuck at Maintenance Mode Cloning 95% after deploying server on cloud service from marketplace image
- Plesk update or upgrade fails: perl(MIME::Lite) is needed by perl-SOAP-Lite-0.710.10-4.el6.noarch
- Plesk upgrade fails on Windows Server: The installation of the package 'urlrewrite' failed with code 1603
- Plesk upgrade started in Web UI stuck
- Unable to upgrade Plesk with Percona: mariadb-server >= 5.0.60 is needed by plesk-mysql-server
- Plesk upgrade or update failed: Failed to connect to autoinstall.plesk.com port 80: Connection refused
- ModSecurity update/installation on Ubuntu server with Plesk fails: dpkg: error processing archive
- Plesk upgrade fails: E: Unable to locate package pp17.8.11-bootstrapper