Upgrade Ubuntu 16.04 to 18.04 and / or 20.04
I want to upgrade Plesk 18 from Ubuntu 16.04 to Ubuntu 18.04 or 20.04.
I’m glad to inform you that today we finally published dist-upgrade instructions for Plesk Obsidian.
Using this instruction server administrator can perform Operation System upgrade together with Plesk Obsidian.
Supported dist-upgrade paths:
Debian 9 to Debian 10
Ubuntu 16 to Ubuntu 18
Ubuntu 18 to Ubuntu 20
Note: Debian 8 → Debian 9 dist-upgrade path is not in the supported list.
Dist-upgrade chapter in Plesk Obsidian documentation: https://docs.plesk.com/en-US/obsidian/administrator-guide/server-administration/distupgrade-support.74627/
KB article with the particular instructions: https://support.plesk.com/hc/en-us/articles/213410369
Joe Blow commented
I did the update from 16.04 LTS to 18.04 LTS on two machines and after some trial and error and backups/restores it worked finally on both machines.
Some best-practices here, which deviated from aboce installation guide in my case
# Grafana Keys were missing for the sources, following command fixed it
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 8C8C34C524098CB6
# some access rights were wrongly set. Installation aborted, following command fixed it
sudo chmod -x /usr/share/initramfs-tools/hooks/fixrtc
# root file system rights were wrongly set, installatio aborted, following command fixed it
chown root /
The part with #Get the Plesk packages that need to be upgraded. i completely left out. And it worked as well.
Upgrade from Ubuntu 16.04 to 18.04 worked for me (described here: https://support.plesk.com/hc/en-us/articles/213410369 )
The upgrade from Ubuntu 18.04 to 20.04 requires Plesk version 18.0.33. This version is not released yet.
Also it is stated, that we have to uninstall docker manually.
Is docker not supported in Ubuntu 20.04?
The procedure described here for Ubuntu 16.04 -> 18.04 worked for me.
However, steps 7 and 8 are not very clear. Therefore, I performed an apt-get update and upgrade instead, and then fixed Apache as described in step 8.
Not sure why it took so long for Plesk support to produce such guide, but in the end migration was possible. Thank you. I hope a migration guide to Ubuntu 20 can be published soon.
[Deleted User] commented
I canceled my subscription for the end of January after using Plesk for many years.
Thank you for nothing ...
No support, no communication, no ETA, just nothing.
A really incredible neglect of your business customers!
Anything new? ETA? Please... it's really so hard to put an update on this matter? There is almost NO communication from your side and we are eager to see if the solution will come soon or never.
So we ask again: How far are you on this matter?
dist-upgrade from debian9 to debian10 please ...
Matteo Sgalaberni commented
dist-upgrade from debian9 to debian10 please
This voting system is a joke, voting for what are in essence essential parts of any control panel is stupid and wastes peoples time. Lovely way to fob off your clients.
Its almost december 2020. Come on guys. When will it be possible to upgrade from 16.04 to 18.04/20.04 without a second (paid) server and without breaking the configuration?
Karl-W. v. R commented
I just recently managed to get things packed. somehow and then migrate to another server that runs on 18.04. It took me alll about 5 retrys to have all in place to make it smoothly running. Still a cactus would have been more easy and less painful to be carried. The plesk migraton tool does not migrate if something or some extension is not installed on the new server and it does not transfer licenses nor extensions
The transfer of additional Licenses had to be done by plesk manually and the quality of what was then useable was wayout of any positive range for any type of migration.
You always have to be aware of from where and how you connect to an between these servers remove almost all IP protections and disable firewalls to make ist work fast and have. You must have a working recovery access to both systems, oherwise there is a high chanche to be blocked or even locked out of one of your servers in an instance. Plesks DNS and *X Record Transfer does not work when you transfer between Strato VPS Systems. You must use the tools provided by Strato and that also is not just a smooth running thing. More than all painful is that this transfer is not for free as Strato on top of all lets you pay 20 to 60€ for the domain transfer.
Not to be too unfair, a Reset or upgrade of a windows System is also quite painful.
But compared with the smoothness of the Ubuntu sytsem upgrade as it happend when I upgraded Plesk + Ubuntu server from 14.04 to 16.04 this was bu.sh..
I very much hope that the next Upgrade 18.04 to 20.04 oder better to 22.04 will be prepared much much better better than this one by plesk.
You'd better be orking on this by now dear Plesk'ians!
Btw. on Strato VPS servers "kernelcare" ista waste of time and money. It simply is not compatible with the Unbuntu releases of Ubuntu 16.04.xx and 18.04 Strato provides right now.
The domains are up an running stale now after almost 15 days, but I'll be leaving Business and start growing trees somwhere before I do this again. as those roots are more solid, I believe. :-(
An absolutely MUST-HAVE, my Plesk-friends. Support is always amazing since years. So, this little, but important, feature should be implemented as soon as possible.
Lots of greets
Urgent !!!, dist-update from 16.04 to 18.04
any update regarding the upgrade guide?
Does the guide require a second server?
Thomas Leavitt commented
Re: Anton Maslov
Here's the official word via a support request made on my behalf by our vendor (paraphrased to protect the innocent) about upgrading from 16.04 to 18.04, and 18.04 to 20.04:
It will be a guide (tested to the best of their ability), not a script.
It will NOT be officially supported. If the process blows up in your face, they won't help.
So, if you can't use their migration tool, you're SOL. The response was very, very definitive about this. Plan accordingly. I'm going to vehemently express my dissatisfaction with this approach to our vendor.
Second server would NOT be acceptable.
I hope the guide does not involve a second server we have to pay for. Fingers crossed.
Wow, something seems to be happening. They changed the status from planned to started. But - alas - there will be no real solution, only a GUIDE. Let's hope it will be a really good one... 😕
Today at 20:05
We do plan to publish a guide for Ubuntu dist-upgrade16>18 and 18>20 on Plesk Obsidian 18.0.31 version approximately till end of October.
Mark Barnes commented
Please we need Debian 9 to 10, it is ridiculous that this has not been implemented already!