• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Package Update Manager notification says "Failed to fetch http://updates.atomicorp.com/..."

King555

Regular Pleskian
Since about a week I get a daily e-mail with a Package Update Manager notification saying:

Code:
2019-11-18 06:30:51 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2019-11-18 06:30:55 ERROR: W:Failed to fetch http://updates.atomicorp.com/channels/tortix-common/debian/dists/jessie/main/binary-amd64/Packages  404  Not Found [IP: 46.105.121.84 80]
, W:Failed to fetch http://updates.atomicorp.com/channels/tortix-common/debian/dists/jessie/main/binary-i386/Packages  404  Not Found [IP: 46.105.121.84 80]
, E:Some index files failed to download. They have been ignored, or old ones used instead.
2019-11-18 06:30:55 ERROR: Exited with returncode 1.

I guess this is the update for ModSecurity, which is activated in Plesk. Do I have to change the URL manually or is this a bug in Plesk?
 
The Atomicorp server seems to only work over https, while the repository configuration calls for a plain http connection.

As a first step I suggest manually altering the repository configuration on your side, this will fix the error. When the updates start flowing again, see if this was perhaps fixed in a later repository update, if not, research further...
 
Thanks.

Yesterday and today I did not get the mail, but I did not change anything.

Do you know how to check whether the ModSecurity rules are up to date?
 
Apparently they altered their server configuration to also work with plain http again.

As for the ModSecurity rules, e.g. check the timestamps of the /etc/httpd/conf/modsecurity.d/rules/tortix/modsec contents or look into /var/asl/data/updates-data ...

A daily update can be manually triggered with:
Code:
plesk daily UpdateModSecurityRuleSet
 
I did not find the directories you mentioned, but I found this one: /etc/apache2/modsecurity.d/rules/tortix/modsec

There are several files with today's date, incl. 50_plesk_basic_asl_rules.conf. I guess this is the updated file and so everything is fine.
 
Back
Top