Applicable to:
- Plesk
Note: We recommend trying out the Release Candidate using backed up production data, but do not recommend using it in live production environments.
Choosing an upgrade strategy
There are two ways to upgrade Plesk:
-
In-place upgrade is performed using Plesk Installer on the same server. Can be used if the OS installed on the server is supported by the target Plesk version and is not discontinued under the terms of the Plesk Lifecycle Policy.
-
Upgrade by transfer is the process of switching to the latest Plesk version by moving all of the hosting data and settings from the current Plesk server to a server with the latest version of Plesk installed. This strategy is preferred when upgrading servers with an OS that either not supported or is approaching the support termination date.
Before you start
Make sure the server has enough resources and meets all requirements:
-
OS version should be supported by its vendor and not approaching its termination date (check the Plesk Lifecycle Policy page).
-
In case of Upgrade by transfer strategy, the server should meet the target version's software requirements and that all software installed on the server is compatible with the target version. For example, if the server has hMailServer installed and set up as a mail server in Plesk, then upgrading to Plesk Obsidian may be unsuccessful, as this version does not support hMailServer. In such case, upgrade by transfer is recommended.
-
In case of In-place upgrade, the installed version of Plesk should support upgrading to Plesk Obsidian. The supported versions are:
- Plesk Onyx 17.0
- Plesk Onyx 17.5
- Plesk Onyx 17.8
If an earlier version is installed you can either upgrade to Plesk Onyx first or set a new server with Plesk Obsidian and then transfer the accounts and websites to the new server. Please see Plesk Migration and Transfer Guide for details.
-
At least 3GB of free disk space should be available for each of the following directories:
- On Windows:
C:\ParallelsInstallerand%plesk_dir%
(see #213903325 for the reference) - On Linux:
/root/parallelsand/usr/local/psa(or/opt/psaon Debian and Ubuntu) and/tmp(if it is mounted to a separate partition)
- On Windows:
- On Linux: it should be possible to execute files in the
/tmpdirectory. Check that directory is not mounted withnoexecoption:
# mount -l | grep noexecIf it is, remount the directory without the
noexecoption:# mount -o remount,exec /tmp - On Linux: verify that the system package manager is configured properly and can fetch and install packages from the OS vendor's repositories (see the article How to check system repositories configuration). Note that there is no need to disable third-party repositories before the upgrade. Also, the latest OS updates should be applied using
yumorapt, depending on the type of Linux distribution. - On Windows: MySQL should be used as a Plesk database provider. To determine which database provider is used to storing the Plesk configuration database, use the article #213922485. If the Plesk database provider is Jet or MS SQL, switch it to MySQL using the instructions provided in article #213921345. It will save time during the upgrade.
- Download and run the latest pre-upgrade checker. If a problem is found, it is reported as a warning in the final report. The log file will have a full description of the issue with a link to a helpful KB article. Apply the solutions, then re-run the pre-upgrade checker until no warnings are reported or only non-critical issues (such as business logic warnings) are left.
- "Known Problems and Limitations" section of Plesk Upgrade Notes should be read and the necessary actions are taken.
- The upgrade should be scheduled on the time when the server load is the lowest and the service downtime impact on hosting customers is minimal.
- All scheduled maintenance tasks should be temporarily disabled, as they may interfere with the upgrade process (especially, on Windows).
- It is a good idea to make a full server backup, which can be used to re-image the server if needed
How to start the upgrade
Detailed instruction can be found in How to upgrade Plesk to the next release
-
If there is no output from Plesk Installer for a long time, it does not mean that the upgrade has stuck. Some silent background operation might be taking a long time to run. Check what is happening on the server:
-
On Linux, run the
ps axufwwcommand and check the process tree that stems from the Plesk Installer process. See if any of these processes are running ("R" state). Run the command several times with an interval of 1-3 minutes and check if there is any change. -
On Windows, download Process Explorer, unpack and run it. Check the process tree and see if any child processes of
ai.exeare consuming CPU or opening/closing files.
-
-
If the upgrade fails, check for error messages in the output, as well as in the log files (
C:\ParallelsInstaller\autoinstaller3.logon Windows or/tmp/autoinstaller3.logand/var/log/plesk/install/plesk_17.0.17_installation.logon Linux). Check Plesk Knowledgebase for solutions using the found error messages. -
To continue the failed upgrade, re-run
plesk-installer.exeon Windows or ./plesk-installeron Linux, or use the following command:# plesk repair installation
Comments
15 comments
Hello, is there a way to upgrade a Plesk server offline?
Or to keep the server off-network and only allow Plesk to communicate with the internet and install the latest Plesk?
Hello @Jef,
> Hello, is there a way to upgrade a Plesk server offline?
By design, this is not possible, upgrades are done online if you are talking about In-place upgrades.
For upgrades by transfer only connectivity between old and new Plesk servers is required.
> Or to keep the server off-network and only allow Plesk to communicate with the internet and install the latest Plesk?
This is a possible scenario. You may disable Plesk automatic updates and connect the server to the internet only when required and install required updates/upgrades.
Current version: Verzió 17.8.11 #67
plesk installer upgrade PLESK_18_0_18
Exception: Failed to solve dependencies:
plesk-dovecot-imap-driver-18.0-2.centos.7+p18.0.18.0+t190822.1506.x86_64 requires plesk-dovecot >= 2.3.6
plesk-dovecot-imap-driver-18.0-2.centos.7+p18.0.18.0+t190822.1506.x86_64 requires plesk-dovecot-pigeonhole >= 0.5.6
ERROR: The Yum utility failed to install the required packages.
Attention! Your software might be inoperable.
Visit https://support.plesk.com/ to search for a solution.
exit status 1
installed dovecot version:
plesk-dovecot 2.3.7.2-centos7.19090321 (PLESK_17_8_11-extras)
plesk-dovecot-core 2.3.7.2-centos7.19090321 (PLESK_17_8_11-extras)
plesk-dovecot-imap-driver 17.8.11-cos7.build1708190903.21 (PLESK_17_8_11-extras)
plesk-dovecot-pigeonhole 0.5.7.2-centos7.19090312 (PLESK_17_8_11-extras)
Hello Jászay,
Please submit a ticket to Plesk Support https://support.plesk.com/hc/en-us/requests/new to investigate the issue further.
Hello,
I expected as part of the upgrade that curl and libcurl would also be updated, but this does not appear to be the case:
# rpm -q curl libcurl
curl-7.29.0-54.el7.x86_64
libcurl-7.29.0-54.el7.x86_64
According to the change log the version of libcurl on Obsidian is 7.63.0. How can I upgrade this? It is required in order to achieve full compatibility with a software package I am using.
Thanks
Hello @Charles,
Could you, please, provide the OS, where Plesk is installed?
I will need it to check on a test server.
Hi @Ivan,
The OS is CentOS 7.
Thank you.
Hello @Charles,
Thank you, I've reproduced this:
# rpm -q curl libcurl
curl-7.29.0-46.el7.x86_64
libcurl-7.29.0-46.el7.x86_64
plesk -v
Product version: Plesk Obsidian 18.0.19
Build date: 2019/10/02 12:00
OS version: CentOS 7.5.1804
I'll clarify the reason will add this information here.
@Charles, I've clarified this, Packages were updated for Plesk installer binary itself so that it uses more modern version.
The curl installed on the server is provided by OS vendor.
You may trying upgrading it using similar method as, for example, here: https://talk.plesk.com/threads/plesk-backup-manager-problem-with-ftps-and-curl.345484/#post-836892
The upgrade checker doesn't seem to have an Obsidian version on http://autoinstall.plesk.com Is there one elsewhere?
Hello @Tara,
Let me know what's the exact issue you have?
According to my tests, the installer takes Plesk Obsidian packages from http://autoinstall.plesk.com/pool/PSA_18.0.*.
In case Plesk 18 isn't displayed for you as an option for the upgrade, make sure you have Plesk 17.8 installed because this is a prerequisite for Plesk Obsidian.
Also, make sure your server satisfies Software requirements: https://docs.plesk.com/release-notes/obsidian/software-requirements/
The upgrade process itself is fine and I was able to upgrade without issue.
It's just in the instructions above, under Advanced requirements, it says:
5. Download and run the latest pre-upgrade checker. If a problem is found, it is reported as a warning in the final report. The log file will have a full description of the issue with a link to a helpful KB article. Apply the solutions, then re-run the pre-upgrade checker until no warnings are reported or only non-critical issues (such as business logic warnings) are left.
You get the pre-upgrade checker from http://autoinstall.plesk.com/<Plesk_version>/examiners/panel_preupgrade_checker.php where <Plesk_version> is the desired version of Plesk you are willing to upgrade to. Trouble is the most recent version there is PSA_17.8.11. So while the instructions suggest running the pre-ugrade checker prior to upgrading to Obsidian, there is no pre-upgrade checker for Obsidian.
The correct link to Pre-upgrade checker for Obsidian is http://autoinstall.plesk.com/pool/PSA_18.0.20_1312/examiners/panel_preupgrade_checker.php
How can I downgrade Plesk Obsidian to Plesk WebHost?
Hello @Khalequzzaman,
Probably, you've meant a downgrade to Plesk Onyx because WebHost is an edition of Plesk license: https://www.plesk.com/editions/
The scenario of Plesk downgrade is unsupported: https://support.plesk.com/hc/en-us/articles/213955885-Is-it-possible-to-downgrade-Plesk-or-roll-back-Plesk-updates-
Please sign in to leave a comment.