Applicable to:
- Plesk
Note: Currently Plesk Obsidian is in Release Candidate state
There are two ways to upgrade Plesk Obsidian:
In-place upgrade
In-place upgrade is performed within one server environment. To perform in-place upgrade:
-
OS should be supported by its vendor and Plesk;
-
Installed Plesk version should support upgrade to Plesk Obsidian.
The supported versions are:- Plesk Onyx 17.0
- Plesk Onyx 17.5
- Plesk Onyx 17.8
If requirements are met, proceed with the upgrade using method from this article.
If an earlier version is installed you can either upgrade to Plesk Onyx first or Upgrade by transfer.
Upgrade by transfer
Upgrade by transfer it is the process of upgrade by moving current environment to the server with Plesk Obsidian installed. To do so:
- OS should be supported by its vendor and Plesk;
- Currently installed Plesk version should support migration to Plesk Obsidian. Currently Plesk for Linux and Windows 8.6 and later are supported.
Proceed with the steps from this article to migrate your server to Plesk Obsidian.
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.