Issue Plesk Related Issues Arising After Upgrading Ubuntu Server OS (22.04 LTS to 24.04 LTS)

[learning_curve]

Server operating system version

Ubuntu 24.04 LTS

Plesk version and microupdate number

18.0.64

Where to start?

Initially, in this first post, we can deal with Plesk items that are (to be accurate) not directly related to the specific Dist-Upgrades mentioned in the thread title, but could (and really should) have been dealt with, in the latest 108.0.64 Plesk upgrade, but they still haven't been, hence they are still present...

1) These Plesk errors / warnings are still present, yet this was reported and acknowledged here, way back in June when running Ubuntu 24.04 LTS / Plesk Obsidian 18.0.61

Issue - Apt update warning weak algorithm (dsa1024)

Hi, when I run apt update on my Ubuntu 24.04 server I get the following warning: W: http://autoinstall.plesk.com/pool/PSA_18.0.61_14662/dists/noble/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024) W...

talk.plesk.com

2) These Plesk errors have been reported before (on previous Ubuntu OS releases / previous Plesk Obsidian releases / previous Roundcube releases) and it's always the same error, which appears to be caused by delays in "confguration" verification with later PHP releases. We're now 2 further releases forward on Roundcube, but still on PHP8.2...

Question - Roundcube 1.6.7 is on PHP 8.2 but, Obsidian 18.0.61 is on PHP 8.3 - Why the delay in moving Roundcube on to PHP 8.3?

As per the thread title. Anybody using Roundcube on Obsidian (like us) are currently unable to remove PHP 8.2, purely because of the Obsidian / Roundcube dependencies. Roundcube 1.67 supports PHP 8.3 and Obsidian is now on PHP 8.3, but currently, the Obsidian default setup, is that Roundcube...

talk.plesk.com

Neither of these two items are mission critical, obviously, but both of them are without doubt sub-optimal, so could and should have been rectified by now, by Plesk

In the next post, we can deal with all of the "surprises" that 'Plesk Related Issues Arising After Upgrading Ubuntu Server OS (22.04 LTS to 24.04 LTS)' have brought to us...
Note that there's been no issues with the Dist-Upgrade and / or the Plesk upgrade from 18.0.63 to 18.0.64. It's the collateral damage (artistic differences? ) afterwards

 

[learning_curve]

To continue from the previous post / some background etc. They are identical servers with identical configs, 2 live, one redundancy backup. A condensed version of the common operational config is shown in the forum sig. The Manual Procedure for the Dist-Upgrade for Ubuntu 22 > Ubuntu 24 from this page:
https://support.plesk.com/hc/en-us/...-upgrade-procedure-on-Linux-server-with-Plesk was followed on all of them, without any significant issues or errors. Some notes that we posted on our own procedure changes are shown on HERE which is part of another thread.

Other than the OS changes directly applied via the Dist-Upgrade itself, there were no changes to Plesk itself (the upgrades to 18.0.64 were completed after the Dist-Upgrades) & the MariaDB databases were not upgraded as part of the Dist-Upgrade because they were already on the 10.11.9 release. Plesk now support MariaDB 11.4 but we're not going to run those upgrades, until all of these current issues are resolved (even though they are not associated with MariaDB).

Currently, we have zero mission critical issues with Plesk post the Dist-Upgrades, but wedo have some collateral damage, none of which were present, when running the previous Plesk 18.0.63 release on Ubuntu 22.04. All of the servers' networking / DNS etc was unchanged by the Dist-Upgrade, but it's still unclear (at this stage) what the true sources of these errors/ warnings are Maybe Plesk, or somebody else, may have seen these or similar to these before, so can add some helpful corrective comments to this thread. They all appear to be related to Plesk (and or connectivity to it) yet they all appear at random, never consistently (in terms of time) and they weren't present previously, at all, ever. It's been NetPlan / IONOS DNS Servers / resolvectl not systemd-resolve pre and post Dist-Upgrade / Plesk Upgrade, yet all of the usual expected actions eg. full plesk repair procedures, all external tests etc don't reveal the true sources.

Extracts of example some of the current errors / warnings:

Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0: php_network_getaddresses: getaddrinfo for api.monitoring360.io failed: Temporary failure in name resolution

Autoinstaller exited with error: Failed to read product information from the file : Can't process products.inf3: Failed to download the file http://autoinstall.plesk.com/products.inf3 (unknown IP):
Could not resolve host: autoinstall.plesk.com

Can't process versions.inf3: Failed to download the file http://autoinstall.plesk.com/versions.inf3 (unknown IP):
Could not resolve host: autoinstall.plesk.com

One example of inconsistency:
Running # curl -Iv autoinstall.plesk.com will sometimes produce the full, expected result, then suddenly, it won't
(e.g. * Could not resolve host: autoinstall.plesk.com * Closing connection curl: (6) Could not resolve host: autoinstall.plesk.com)

Yet apt update which includes calls to autoinstall.plesk.com will run faultlessly, at the exact same time that ^ that curl command, won't.

Clearly, post Dist-Upgrade there's a new connectivity / network / plesk api issue, yet none of that config was changed as part of the Dist-Upgrade and all of the 'Temporary failure in name resolution' errors / warnings etc since ,are only related to Plesk controlled sources, nowhere else.

Having searched on here and re-tested where required, we've already covered all of the previous "quick fixes" (this thread is a good example FWIW)
This will probably, only be a small misconfig, as a result of the Dist-Upgrade, i.e. maybe a new OS / Plesk or Plesk / OS interface change, somewhere...

 

[learning_curve]

Another non-critical Plesk related issue that's now present, after the upgrade to Ubuntu 24.04 LTS is this item in the Change Log for 18.0.64:

"The CloudLinux team extended the Imunify360 extension with the improved ImunifyAV/AV+ and renamed the Imunify360 extension to Imunify. Existing users of the free and paid ImunifyAV extension (the revisium-antivirus ID) can upgrade to the new ImunifyAV/AV+ at no additional cost. Learn more about benefits of the revamped Imunify and how to upgrade to it"

The lack of support for Ubuntu 24.04 is omitted from the Change Log... (see image)
Yes it's a 3rd Party Package not a Plesk Package, but the omission detail should have been included in the Change Log notes

 

[Sebahat.hadzhi]

We understand that the resolution might be taking longer than expected and we would like to apologize for any possible inconvenience caused. It is on team's agenda. As you mentioned, these aren't that critical issues and there were more pressing and crucial matters prioritized for the latest release. Unfortunately, I cannot provide any ETA for the weak algorithm warning messages. As for updating the PHP version of Roundcube to 8.3, that should be introduced in the following Plesk release (unless something goes unpredictably wrong).

The error messages reported in #2 look like networking/connectivity-related issues. If you have the option, please get in touch with our support team so they can connect to the server(s) and perform thorough investigation and attempt to identify the culprit.

As far as I am aware, support for Ubuntu 24 was never introduced. Please correct me if I am wrong. Unfortunately, we cannot list an OS compatibility chart for a third-party software on our change log page as it will sort of clog it with non-vital information. I hope you understand my point.

 

[learning_curve]

We understand that the resolution might be taking longer than expected and we would like to apologize for any possible inconvenience caused. It is on team's agenda. As you mentioned, these aren't that critical issues and there were more pressing and crucial matters prioritized for the latest release. Unfortunately, I cannot provide any ETA for the weak algorithm warning messages. As for updating the PHP version of Roundcube to 8.3, that should be introduced in the following Plesk release (unless something goes unpredictably wrong).

Thank you. The weak algorithm issues are a simple fix (by comparison) but it's still good to see that the Roundcube to 8.3 is (finally) on it's way, soon.

The error messages reported in #2 look like networking/connectivity-related issues. If you have the option, please get in touch with our support team so they can connect to the server(s) and perform thorough investigation and attempt to identify the culprit.

After some intense comparisons and inspections (because it wasn't on all 3 servers), we finally fixed these problems ourselves, yesterday. Just catching up with an update now. Somewhere, at some point, in amongst the Dist-Upgrade, the content of /etc/systemd/resolved.conf.d/resolved.conf was changed. It's a 'drop-in' file, not a symlink and it shouldn't have been chnaged of course, but it was. It took some time to trace this subtle, but config compromising, change (mainly by comparison), because using systemd-resolved service for Network Name Resolution has many linked dependencies . Still don't fully understand why this only effected Plesk interactions and no others, but in fairness, it wasn't actually a Plesk issue in the end, even though the Dist-Upgrade was a Plesk procedure. The errors / warnings were all caused by just one file being compromised / corrupted as part of an OS Dist-Upgrade, which then caused the said 'collateral damage'.

As far as I am aware, support for Ubuntu 24 was never introduced. Please correct me if I am wrong. Unfortunately, we cannot list an OS compatibility chart for a third-party software on our change log page as it will sort of clog it with non-vital information. I hope you understand my point.

Yes, fully understood. Wasn't imagining any kind of OS compatibility chart etc. Just a very short, writtten exclusion suffix e.g. (NOT Ubuntu 24.04 or Debian 12) or similar, would be good enough. It's up to 3rd party suppliers to advise Plesk (we think) about any non-supported data, in advance, so this doesn't arrive as a surprise for any Plesk Users / Customers. Ubuntu 24.04 LTS was released way back in April, so this particluar example will no doubt be updated pretty soon.

 

[Sebahat.hadzhi]

After some intense comparisons and inspections (because it wasn't on all 3 servers), we finally fixed these problems ourselves, yesterday. Just catching up with an update now. Somewhere, at some point, in amongst the Dist-Upgrade, the content of /etc/systemd/resolved.conf.d/resolved.conf was changed. It's a 'drop-in' file, not a symlink and it shouldn't have been chnaged of course, but it was. It took some time to trace this subtle, but config compromising, change (mainly by comparison), because using systemd-resolved service for Network Name Resolution has many linked dependencies . Still don't fully understand why this only effected Plesk interactions and no others, but in fairness, it wasn't actually a Plesk issue in the end, even though the Dist-Upgrade was a Plesk procedure. The errors / warnings were all caused by just one file being compromised / corrupted as part of an OS Dist-Upgrade, which then caused the said 'collateral damage'.

Thank you for sharing how you resolved the issue. Hopefully, that will be useful for anyone who might come across it.

Yes, fully understood. Wasn't imagining any kind of OS compatibility chart etc. Just a very short, writtten exclusion suffix e.g. (NOT Ubuntu 24.04 or Debian 12) or similar, would be good enough. It's up to 3rd party suppliers to advise Plesk (we think) about any non-supported data, in advance, so this doesn't arrive as a surprise for any Plesk Users / Customers. Ubuntu 24.04 LTS was released way back in April, so this particluar example will no doubt be updated pretty soon.

I get your point. Thanks for the suggestion. I will discuss it with our team and we will see if we can integrate that in the Change log.

 

[learning_curve]

@Sebahat.hadzhi Happy Footnote: Having solved that previous 'challenge' and as mentioned previously in post #2, we moved on to the MariaDB upgrades, seeing as Plesk now supports MariaDB 11.4 from 18.0.64 onwards. At the date / time of this post, there was no prompt within the Plesk UI so we used existing the Manual Plesk Procedure (from here) selecting the 'Plesk on Ubuntu 20.04/Ubuntu 22.04' option (as 24.04 isn't shown in that article yet ) but then substiuted 11.4 where 10.4 is shown. They all upgraded fine and are all now running Plesk Obsidian 18.0.64 on MariaDB 11.4.3.