Installation & Upgrade
Articles about Plesk components updates and upgrades including OS.
- Error during Plesk upgrade to Obsidian 18.0.37: PHP Fatal error: Uncaught JMS\Serializer\Exception\RuntimeException: Could not decode JSON, syntax error - malformed JSON.
- Issues upgrading or after converting CentOS 8 to AlmaLinux: none of the providers can be installed
- Unable to update Plesk on CentOS 7 in Google Cloud platform: repomd.xml signature could not be verified for google-cloud-sdk
- Unable to update Plesk Obsidian 18.0.34 to the latest available build on Ubuntu 16.04: There is no release with ID 'PLESK_18_0_35' of product 'plesk' at the installation source
- sa-compile update fails on Plesk server with Plesk Email Security: dpkg: error processing package sa-compile (--configure)
- Plesk update to version 18.0.34 fails with message: Plesk database scheme was not upgraded completely
- Daily Maintanace scripts, Plesk update are stuck due to hanged /usr/libexec/urlgrabber-ext-down processes
- Unable the access Plesk after dist-upgrade: blank page is shown
- Plesk upgrade failed: /usr/bin/mysql: unknown variable
- SpamAssassin fails to update on a Plesk server: no 'mirrors.sought.rules.yerp.org' record found, channel failed
- Plesk repair installation launched from Plesk GUI failed: Another instance of bootstrapper is already running. Please\nwait until it finishes
- Plesk installation on CentOS 8 fails: nothing provides
- Plesk Obsidian upgrade on Windows get's stuck or fails: this operation returned because the timeout period expired
- After November 30th, 2020, updating system packages on Plesk server with CentOS 6 fails: Cannot find a valid baseurl for repo: base
- How to manage date and time for Plesk autoupdates?
- 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
- Warning after upgrade to Plesk Obsidian: Upgrade failed. To remove this notice, remove the file C:\Program Files (x86)\Parallels\Plesk/var\upgrade\plesk-upgrade-failure.flag from the server
- 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 or update Plesk: there is no product with the ID 'plesk' at the installation source
- 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 upgrade fails: Unable to find "main" IP address
- 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
- 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 update Plesk Obsidian to the latest build