• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved Rollback Plesk 7.4.29 To Plesk 7.4.28 (Previous Version) on Ubuntu 20.04.4 LTS

learning_curve

Silver Pleskian
Server operating system version
Ubuntu 20.04.4 LTS
Plesk version and microupdate number
Plesk Obsidian 18.0.43 MU #1
We have one domain, that uses third party apps that have an issue with PHP 7.4.29. The issue was not present in PHP 7.4.28 and will (in theory) be fixed in time to use with PHP 7.4.30 as/when that's released. There have been previous posts where it was possible to do this (this one is an exmple) but a) That was a long time ago and b) It was not done on Ubuntu OS. This file: /var/log/apt/history.log does contains all of the update details (it was part of this Plesk PHP update that became available after the 18/4/22)

There are articles on using this file's content, as part of Ubuntu OS Rollbacks, but PHP is provided by Plesk, so more than likely, it will be a more specifc process, IF it's possible

Has anybody done this yet / know if it is possible / what the correct Plesk related syntax would be?
 
Perhaps you could remove all plesk-php74 packages with .29 version with OS package manager and then download .28 packages from Index of /PHP74_17/ for your OS and install them with OS package manager.
 
Perhaps you could remove all plesk-php74 packages with .29 version with OS package manager and then download .28 packages from Index of /PHP74_17/ for your OS and install them with OS package manager.
Will that be okay? I'm meaning that isn't (wasn't..) the Plesk PHP 7.4.28 release different from the content of: php74-ubt20.04-x86_64.inf3 from that ^^ url
 
I'm not sure, it's just an idea.
Another idea is correcting URL for PHP74 in /etc/apt/sources.list.d/plesk.list after removing PHP7.4 component and then installing it with the new URL.
That ^ does sound easier, but the url is identical now to the archived url that we took when Plesk PHP 7.4.28 was issued;
deb Index of /PHP74_17 focal all

Just a guess, but that might end up just being: remove plesk PHP 7.4.29 and then re-install it as it would surely default to the current release?

Bizzarely, there is no official PHP release (yet) of PHP 7.4.29 on their own release page: PHP: Releases
That might be why the third party suppliers, are not ready / have the issue.
 
but the url is identical now to the archived url that we took when Plesk PHP 7.4.28 was issued
No. The default URL is

Code:
deb http://autoinstall.plesk.com/PHP74_17/  focal all

and .29 will be installed with it.

Modified URL for .28 is

Code:
deb https://autoinstall-archives.plesk.com/PHP74_17/ focal all
 
Thank you. That url ^^ should be the answer for the invoking the rollback to Plesk's PHP 7.4.28, but the syntax of the install I wanted to treble-check :)

Pretty sure that removing the existing Plesk PHP 7.4.29 components, should just be:

# plesk installer remove --components php7.4

To the replace this ^ with the archive Plesk PHP 7.4.28 components (& with the modifed /etc/apt/sources.list.d/plesk.list file, already in place) still not quite sure of the correct syntax with it being a Plesk package?

# apt upgrade - surley won't be sufficient, because there's no Plesk PHP 7.4.28 at this point

# apt ./<the correct reference to the current working directory, where the deb has been temporarily located> Shoud work - If - the deb is already there.

But, pretty sure that the url in the /etc/apt/sources.list.d/plesk.list file: deb Index of /PHP74_17/ focal all isn't the correct syntax to bring that via curl or wget, into the current working directory. What syntax should be used @IgorG to complete this part do you think?
 
It's not possible to edit posts anymore once they are x minutes old... This was going to be an edit to the install section above but, new post it is then.

It seems easy enough @IgorG to install via the GUI **:8447/add_components.html page provided by Plesk, after having selected the Local media option and added the full file path to the php74-ubt20.04-aarch64.inf3 file (in this case) within the Updates source and installation settings section on that page. That would also uggest there is a CLI option (with the correct syntax) so we'll wait to see if that is the case and if not, it will be a GUI process instead.
 
Long story short... It's done. In the end, all via the GUI route (breifly mentioned above). We'll re-config this, once the third-party developers advise us further (yesterday they helpfully updated us & advised that they do intend to fully support PHP 7.4.29, so it should only be a short wait now). Thanks again @IgorG
 
Back
Top