Resolved Plesk 18.0.52 System Updates / Extensions / Cron - Multiple Failures

[learning_curve]

Server operating system version

Ubuntu 22.04.02 LTS

Plesk version and microupdate number

18.0.52 Update #3

This started earlier with an e-mail notification:

Reason: 2023-06-01 06:26:53 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2023-06-01 06:27:01 ERROR: E:The repository 'mirror://repo.danami.com/channels/danami-juggernaut/ubuntu/mirrors.txt jammy Release' no longer has a Release file.
2023-06-01 06:27:01 ERROR: Exited with returncode 1

Followed by additional e-mail notifications:

run-parts: /etc/cron.daily/60sa-update exited with return code 4

Oops: Unable to download: Can't connect to download.configserver.com:443 (Temporary failure in name resolution)

Whilst in the Plesk WebUI Interfaces, we have:
Action log:

i@https://**My-Server**:8443/cp/javascript/main.js:8:59922
@https://**My-Server**:8443/cp/javascript/main.js:394:105066
map@[native code]
@https://**My-Server**:8443/cp/javascript/externals/prototype.js:1:15936
m@https://**My-Server**:8443/cp/javascript/main.js:394:104973
ks@https://**My-Server**:8443/ui-library/plesk-ui-library.min.js:26:62824
_i@https://**My-Server**:8443/ui-library/plesk-ui-library.min.js:26:119680
Ec@https://**My-Server**:8443/ui-library/plesk-ui-library.min.js:26:108832
vc@https://**My-Server**:8443/ui-library/plesk-ui-library.min.js:26:108760
bc@https://**My-Server**:8443/ui-library/plesk-ui-library.min.js:26:108623
cc@https://**My-Server**:8443/ui-library/plesk-ui-library.min.js:26:105764
cc@[native code]
Ha@https://**My-Server**:8443/ui-library/plesk-ui-library.min.js:26:46665
dc@https://**My-Server**:8443/ui-library/plesk-ui-library.min.js:26:106268
@https://**My-Server**:8443/ui-library/plesk-ui-library.min.js:26:124291
eu@https://**My-Server**:8443/ui-library/plesk-ui-library.min.js:26:124321
g@https://**My-Server**:8443/cp/javascript/main.js:8:143826
global code@https://**My-Server**:8443/modules/action-log/index.php/index/log:108:14

This was relating to a 'null' value

The "Updates source and installation settings" section (within Plesk / Update Settings) is unmodified and correct, however the "summary" section of same, is not:

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

**My-Server**:8443/admin/pum/updates-list gives the expected error response:

The System Updates tool is already installing updates in automatic mode. Please try later.

**My-Server**:8443/modules/catalog/index.php/catalog/featured gives this error:

Internal server error Retry

Updating via Command Line is essentially repeat of the above with some additional text, including:

N: Updating from such a repository can't be done securely, and is therefore disabled by default.

Within **My-Server**/root only the Parallels directory content has been modified today (1/6/23) with two additional files: products.inf3.tmp and versions.inf3.tmp

So... Is this a Plesk connections issue? Is this the result of an earlier corrupt update? Or is it A.N.Other?
All sites and services are fine, just all Plesk connections are currently having these issues.

 

[Peter Debik]

Could not resolve host: autoinstall.plesk.com

Could you please check your /etc/resolv.conf entries, maybe modify them to something reliable like 8.8.8.8 and then ping autoinstall.plesk.com to verify that your host can connect to that URL?

 

[learning_curve]

Your post was a catalyst for us to re-examine things @Peter Debik Thanks!

We could already ping lots of places (apart from certain Plesk locations) without any issue. Our existing resolv setup uses IONOS DNS servers but, has 9.9.9.9 & 8.8.8.8 as fallback DNS servers too. Those Plesk ping oddities, made us think of Juggernaut / our detection criteria for prevention of DDOS attacks etc and Plesk's longstanding reluctance to actually provide any kind of definitive list of IP adddresses for Plesk / Plesk Autoinstall / Plesk Monitoring etc.

Sure enough, it was a quick process to find a few of the IP addresses (there are lots!) relative to autoinstall.plesk.com (via command line ping tests) and other IP addresses relative to Plesk, that we had previously banned, via a large number of IPv4 and IPv6 CIDR bans. By removing all of those CIDR bans and some server re-boots, we resolved all of those errors and problems, so all of those previous errors posted above, have been removed.

The only unknown.... that still remains, is: Why was this never an issue previously (as all of these CIDR bans were at least 4 months -minimum- old) because these issues only commenced, today? Is this a case of Plesk providing a Ninja style, periodic CDN switch, for their content or something similar to that?

 

[Peter Debik]

I do not have an idea why in the past it worked and now it did not. But I am glad to hear that the issue was solved and you can now connect to the installation repository again. So the issue has been resolved?

 

[learning_curve]

I do not have an idea why in the past it worked and now it did not. But I am glad to hear that the issue was solved and you can now connect to the installation repository again. So the issue has been resolved?

Yes. Fully resolved now thank you @Peter Debik
Still a mystery around those Plesk IP addresses, but it's best for that to be raised as totally separate issue, which we'll do shortly.

 

[floh]

Hi, I have several issues that curl cannot resolve hostnames but our dns is working well.

Sure enough, it was a quick process to find a few of the IP addresses (there are lots!) relative to autoinstall.plesk.com (via command line ping tests) and other IP addresses relative to Plesk, that we had previously banned, via a large number of IPv4 and IPv6 CIDR bans. By removing all of those CIDR bans and some server re-boots, we resolved all of those errors and problems, so all of those previous errors posted above, have been removed.

Where can I find these CIDR bans in Plesk? Fail2Ban? If it's on your external firewall, do you know the reason for that?

Best regards
Floh

 

[learning_curve]

Hi, I have several issues that curl cannot resolve hostnames but our dns is working well.
Where can I find these CIDR bans in Plesk? Fail2Ban? If it's on your external firewall, do you know the reason for that?
Best regards
Floh

We don't use Plesk Firewall or Fail2Ban because; a) That would be multiple repeats of what we already have and b) By default, they are incompatible with our own alternative choice, which is; Damani Juggernaut >> Plesk Firewall Extension - Features | Danami We select / auto block them in there. What might assist you further, is all of the Plesk IP addresses, which you'll need not to block / grey list / safe list etc whatever your setup uses. You can find them all here (including IPv6 addresses too if you, you use them, like we do) Resolved - Plesk - The Mysterious Location Of Plesk's Official IP Addresses / CIDR Addresses

 

[floh]

Hi, thank you for providing useful informations.