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.
This is a valid request, so we’ll look into it. There is no ETA at the moment, but we would really appreciate you voting for this request so that we can accurately assess its popularity relative to other features. Thanks in advance!
Please give an public update to this topic.
For legal reasons i´m not allowed to post the information we got from our Plesk account manager.
@Mike: Ubuntu 20.04 is supported since Plesk Obsidian 18.0.29
"Ubuntu 20 is now supported. Plesk Migrator supports migration from Ubuntu 16 and 18 to Ubuntu 20."
Your reseller provider should be able to provide you with a new server based on Ubuntu 20.04 and Plesk - at least we provide this servers already to our customers.
Thomas Leavitt commented
He's what I suggest: we hire an independent contractor to write this script, each of us contributing a small portion of the total cost, then we offer it for sale to other users needing it, and tell Plesk they can buy the script and incorporate it themselves for what we spent on it (and refund anyone who pays us in the meantime).
I'm sure a competent coder could build a solid script in a couple of weeks, so (estimate) 100 hours @ $75 - $7500. Split it 50 ways, we're each paying $150 apiece.
Who's willing to contribute? Say so here. Once we have 10 commitments, I'll go start talking to the coders I know and see if I can find one to do it for $7500 or less.
At least make installing Ubuntu 20.04 possible, properly and with MySQL8 and available with your resellers, so I can buy a new server, migrate everyone there and dump the old one if the distribution upgrades are so hard for you.
If the update cannot be carried out soon, the only option is to switch to another provider.
We're talking about time, work and money here!
Nobody pays PLESK for fun ...
And I don't want to beg for an update to be taken for granted!
Konstantin Eppinger commented
> ETA to update Ubuntu 16.04 to 18.04 via dist-upgrade?
Very deeply disappointed!
ETA to update Ubuntu 16.04 to 18.04 via dist-upgrade?
Very deeply disappointed!
I think dist-update from 16.04 to 18.04 is really important for a lot of users.
I am afraid customers will move to competitors if this feature is not available in plesk soon
Yes please - Just do it for Debian 9 to Debian 10. Please
yes please - Just do it!
Ben work commented
Just do it!
You have been saying for ages that this will be done.
I'm waiting for over a year already...
Why is it taking this long?
Patrick Timms commented
Another thing just while I remember it: an 18-20 upgrade will remove all custom ModSecurity exception rules you had in place, so be sure to note those down beforehand too.
Vote Yes! Yes! yes!
Carlos Hdez commented
Sure, it will be amazing!!!! Vote for yes!!
Julius Lisauskas commented
I've also managed to upgrade from ubuntu 16 to ubuntu 18 with do-release-upgrade. If you know what you are doing, it's possible... Now i need to upgrade from 18 to 20 :D
yes please - 6 instances that could use this :)
Good to know thet someone has jumped the trench from 18 to 20. I still do insist on a plesk full support to do the 16 to 18 Upgrade without all that backup-here-and-restore-there-shishi.Sorry! As time is running up and more and more apps expect at least 18 to run properly, there is urgent need for support asn solution right now, as our action must be planned and be planable with customers and users as well and quite ahead intime. Last time I lost 2 Days of Email because of severe delay at the Provider side right in the middle of an Server Restore & Upgrade!. AND please do not send Upgrade presents just last minute before cristmas.
I have 20 on two other servers as well. I'm not to happy with it as still a lot of server solutions like nextcloud e.g. do not work really smoothly with it! So Help aud jump to 18 and then let move forward with a clear Layout and concept for the next lops in the everlasting slope of innovation
The IDEA to hope that a Backup an restore will do the job to me is just a Vision of a nightmare. I tried this from 14 to 16 had to Restore the complete server and then foud mystelf with a ruin of what I had acomplished before No Never agin will I Follow such reccomendations so I wait until I either am forced to leave it alone and leave. Plesk must provide a solution that does the job for the whole server with all its domains in one step , whithout me having to pay a fortune for a vital and essential customer service that is essential and a must be, following the Linux convetion rules, provided free of charge.
If plesk expects to win my sympathy and respect again in future again you should provide a fluent upgrade out of this mess. Since end 2019 Kernelcare also ist not working properly with 16.04 and I cannot remove it traceless so this already is as substantial mess Im not feeling responsible for. You Must Provide a fluent process please and please do not leave us alone with having to shovel hunderds of GB from and back on a Webserver that should have enough intelligence to do that upgrade on its own. Others can and have done so already. Thanks
Dirk Liesenfeld commented
@anonym can I hire you for that job and if so, how much do you charge? I need to upgrade from 16.04 to 20.04.
Contact me "D.Liesenfeld" at "gmail dot com".
Patrick Timms commented
I managed to complete a non-supported dist-upgrade from Ubuntu 18.04 to 20.04 with Plesk installed on 3 separate hosted VPS instances. There were 3 major issues:
1) DNS resolution broke completely for all hosted domains, rendering them inaccessible both internally and externally. Resolution: alter OPTIONS="-u bind" in /etc/default/named to OPTIONS="-f -t /var/named/run-root -c /etc/named.conf -u bind -n 2".
2) Firewall rules could no longer be managed in Plesk, because it said the iptables package was not installed, even though it was. Resolution: ln -s /usr/sbin/iptables /sbin/iptables.
3) (On just one older server) Users could not log into Roundcube owing to Dovecot errors. Resolution: openssh dhparam 2048 > /opt/psa/etc/dhparams2048.pem - then alter the line in /etc/dovecot/conf.d/11-plesk-security-ssl.conf from ssl_dh=</opt/psa/etc/dhparams1024.pem to ssl_dh=</opt/psa/etc/dhparams2048.pem - then delete the old /opt/psa/etc/dhparams1024.pem for tidiness.
One further minor issue (again on the same older server): rndc decided it didn't want to talk to bind anymore. Resolution - as described here: https://serverfault.com/questions/221250/fixing-bind9-rndc-error-connection-to-remote-host-closed
Oh, also: you might need to run mkdir /var/lib/php/sessions in order to avoid errors from one or two cron jobs.
So, in short... you can do it, guys. But you'll need to be on the ball fixing stuff afterwards. Once you ease into it, though, the fixes are routine across the board and pretty workable.