Applicable to:
- Plesk Onyx 17.8 for Linux
Symptoms
-
Debian 9 (Stretch) or Ubuntu 18.04 is installed on a server and Atomic repository is enabled in
/etc/apt/sources.list: -
ModSecurity Rules by Atomicorp are missing in Plesk at Tools & Settings > Web Application Firewall (ModSecurity) even if the Atomicorp license key is installed.
-
It is not possible to use ModSecurity Rules by Atomicorp at Tools & Settings > Web Application Firewall (ModSecurity) with the error message:
PLESK_ERROR: Failed to install the ModSecurity rule set: modsecurity_ctl failed: gpg: key FFBD5D0A4520AFA9: "Atomicorp (Atomicorp Official Signing Key) support@atomicorp.com" not changed gpg: Total number processed: 1 gpg: unchanged: 1
<...>
E: Some index files failed to download. They have been ignored, or old ones used instead. sed: can't read /etc/asl/config: No such file or directory Command '['sed', '-i', '-e', 's#^MODSEC_RULES_PATH\\s*=.*#MODSEC_RULES_PATH="/etc/apache2/modsecurity.d/rules/tortix/modsec"#g', '-e', 's#^RESTART_APACHE\\s*=.*#RESTART_APACHE="no"#g', '-e', 's#^AUTOMATIC_UPDATES\\s*=.*#AUTOMATIC_UPDATES="no"#g', '/etc/asl/config']' returned non-zero exit status 2 Unable to download tortix rule set -
When installing system updates, the operation fails with:
CONFIG_TEXT: Failed to fetch W: The repository 'http://updates.atomicorp.com/channels/tortix-common/debian stretch Release' does not have a Release file.
<...>
E: Failed to fetch http://updates.atomicorp.com/channels/tortix-common/debian/dists/stretch/main/binary-amd64/Packages 404 Not Found pdates.atomicorp.com/channels/tortix-common/debian/dists/stretch/main/binary-amd64/Packages 404
Cause
Plesk Onyx does not support Atomicorp rule-sets for Debian 9 (Stretch) and Ubuntu 18.04. Support for Atomicorp rule-sets on these OSes has been introduced in Plesk Obsidian 18.0.21.0.
A corresponding error message will be added in scope of the bug IDs PPPM-9037 (for Ubuntu 18.04) and PPP-31722 (for Debian 9).
Resolution
Alternatively, disable Atomicorp repository on the Plesk server:
-
Connect to the Plesk server via SSH.
-
Run the command:
# sed -i.backup 's@deb http://updates.atomicorp.com@#deb http://updates.atomicorp.com@g' /etc/apt/sources.list
-
Update system packages:
# apt-get update
Comments
19 comments
I followed these instructions exactly. Now I cannot access my server via Plesk Administrator, nor via SSH, plus all of my sites refuse to connect. In other words, this has completely destroyed everything...!
@Graham Jones
I would recommend you submit a support ticket so we could check the issue in more details:
How to submit a request to Plesk support?
Hi!
I have opened a ticket at Atomicorp - and at the end i got the message that support for debian 9 and ubuntu 18 is available...
Hello @Matthias Gaede,
Thank you for your update!
This information was passed to the Development Team.
We will update you as soon as we get any new information.
Also, the article was updated to display the new information about support of Debian 9 and Ubuntu 18 by Atomicorp.
Hi Artyom,
thank you for your quick reply... Looking forward to hearing from you again soon
Best regards
Matthias
Regarding my today´s ticket with Atomicorp support for Ubuntu 18 will be available in summer 2019.
@rwl
Thank you for sharing this information!
Same Problem on CentOS Linux release 7.6.1810 (Core)
@Roman Gräbner
I suppose that you have encountered a similar error, since these bugs appear only on Debian/Ubuntu. Try to search for other articles that are applicable for CentOS 7 using the exact error messages.
@Alisa Kasyanova
I think my error looks really similar
"Der ModSecurity-Regelsatz konnte nicht installiert werden: modsecurity_ctl failed: gpg: key 4520AFA9: "Atomicorp (Atomicorp Official Signing Key) <support@atomicorp.com>" not changed gpg: Total number processed: 1 gpg: unchanged: 1 gpg: Signature made Tue Jul 2 01:09:11 2019 UTC using RSA key ID 4520AFA9 gpg: Good signature from "Atomicorp (Atomicorp Official Signing Key) <support@atomicorp.com>" gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 1818 66DF 9DAC A40E 5B42 9B08 FFBD 5D0A 4520 AFA9 TERM environment variable not set"
Hello @Roman Gräbner,
This error is too generic, could you please share details?
Is this the full message?
Are you able to log in https://www.atomicorp.com/amember/login/index using login/password from /etc/asl/config file?
What is the output of the following command:
-----
plesk -v
-----
https://www.atomicorp.com/RPM-GPG-KEY.atomicorp.txt
wget -q https://www.atomicorp.com/RPM-GPG-KEY.atomicorp.txt -O- | apt-key add -
Mariusz Lisowski could you provide more information on what you are trying to achieve.
Same time in the end of year, same procedere again. Since two weeks the following errors on Ubuntu 18.04.5 and Plesk Obsidian (latest updated version), (running fine since Obsidian upgrade-release). Today I uninstalled ModSecurity, because I didn't use it for performance reasons.
Get: 1 https://updates.atomicorp.com/channels/tortix-common/debian bionic InRelease [1,799 B]
Err https://updates.atomicorp.com/channels/tortix-common/debian bionic/main amd64 Packages
404 Not Found [IP: 51.161.13.101 443]
Fetched 1,799 B in 2s (1,039 B/s)
W: Failed to fetch https://updates.atomicorp.com/channels/tortix-common/debian/dists/bionic/main/binary-amd64/Packages: 404 Not Found [IP: 51.161.13.101 443]
E: Some index files failed to download. They have been ignored, or old ones used instead.
But after uninstalling and "aptitude clean", "aptitude upgrade" the problem still exists. The update server entries were not removed. Shall I do it by myself?
Here Plesk update panel uninstall routine:
Reading state information...
The following packages will be REMOVED:
aum* libapache2-modsecurity-plesk* plesk-modsecurity-configurator*
plesk-modsecurity-crs*
0 upgraded, 0 newly installed, 4 to remove and 3 not upgraded.
After this operation, 14.2 MB disk space will be freed.
(Reading database ... (Reading database ... 5%(Reading database ... 10%(Reading database ... 15%(Reading database ... 20%(Reading database ... 25%(Reading database ... 30%(Reading database ... 35%(Reading database ... 40%(Reading database ... 45%(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%(Reading database ... 208451 files and directories currently installed.)
Removing aum (5.0-0.11) ...
Removing plesk-modsecurity-crs (18.0-v.ubuntu.18.04+p18.0.31.0+t200930.1833) ...
Removing libapache2-modsecurity-plesk (2.9.3-v.ubuntu.18.04+p18.0.31.1+t201106.1356) ...
Module security2 already disabled
Removing plesk-modsecurity-configurator (18.0-v.ubuntu.18.04+p18.0.31.1+t201105.1415) ...
Module security2 already disabled
dpkg: warning: while removing plesk-modsecurity-configurator, directory '/var/lib/plesk/modsec' not empty so not removed
(Reading database ... (Reading database ... 5%(Reading database ... 10%(Reading database ... 15%(Reading database ... 20%(Reading database ... 25%(Reading database ... 30%(Reading database ... 35%(Reading database ... 40%(Reading database ... 45%(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%(Reading database ... 208353 files and directories currently installed.)
Purging configuration files for plesk-modsecurity-crs (18.0-v.ubuntu.18.04+p18.0.31.0+t200930.1833) ...
dpkg: warning: while removing plesk-modsecurity-crs, directory '/etc/apache2/modsecurity.d/rules' not empty so not removed
Purging configuration files for libapache2-modsecurity-plesk (2.9.3-v.ubuntu.18.04+p18.0.31.1+t201106.1356) ...
dpkg: warning: while removing libapache2-modsecurity-plesk, directory '/var/cache/modsecurity' not empty so not removed
Purging configuration files for aum (5.0-0.11) ...
dpkg: warning: while removing aum, directory '/etc/asl' not empty so not removed
dpkg: warning: while removing aum, directory '/var/asl/tmp' not empty so not removed
dpkg: warning: while removing aum, directory '/var/asl/rules' not empty so not removed
dpkg: warning: while removing aum, directory '/var/asl/data' not empty so not removed
Überprüfung der Komponenten und Produkte wird gestartet...
Datei wird heruntergeladen report-update: 0%
Datei wird heruntergeladen report-update: 100% fertig.
Datei wird heruntergeladen pool/PSA_18.0.31_4506/examiners/py_launcher.sh: 0%
Datei wird heruntergeladen pool/PSA_18.0.31_4506/examiners/py_launcher.sh: 100% fertig.
Die Änderungen wurden erfolgreich übernommen.
No answer to my problem? No solution to remove/uninstall atomic repository?
The solution on https://support.plesk.com/hc/en-us/articles/360002245513-Atomicorp-rule-set-does-not-work-on-Debian-9-Ubuntu-18-04-with-Plesk-Onyx-E-Failed-to-fetch-http-updates-atomicorp-com-404-Not-Found- doesn't work.
Every day I get:
Err https://updates.atomicorp.com/channels/tortix-common/debian bionic/main amd64 Packages
404 Not Found [IP: 51.161.13.101 443]
Fetched 1,799 B in 1s (1,461 B/s)
W: Failed to fetch https://updates.atomicorp.com/channels/tortix-common/debian/dists/bionic/main/binary-amd64/Packages: 404 Not Found [IP: 51.161.13.101 443]
E: Some index files failed to download. They have been ignored, or old ones used instead.
I am having the same issue on the latest Ubuntu 18.04.5 and Plesk Obsidian 18.0.32 version. Markus did you find any solution?
Hi Enrique,
sure. I manually removed the entries by hand. Since I uninstalled ModSecurity via Plesk updates/upgrades it is the oldest and easiest way to remove the unnecessary repository entries.
Greets
Hello Markus,
thank you very much for the quick response. I will try that out.
Cheers.
extract from atomic support ticket:
Request:
apt-get update fails with following message:
"https://updates.atomicorp.com/channels/tortix-common/debian/dists/bionic/main/binary-amd64/Packages 404 Not Found"
The correspondending archive ist empty:
"https://updates.atomicorp.com/channels/tortix-common/debian/dists/bionic/main/binary-amd64/"
Answer:
The Ubuntu releases are currently being updated therefore they are not available for download currently. I do not have an eta of when they will be released. I apologize for the inconvenience. Please see this article for downloading and installing our free rulesets:
https://wiki.atomicorp.com/wiki/index.php/Atomic_ModSecurity_Rules#.28Optional.29_Do_It_Yourself_Installation
Atomicorp Support
-> All in all this problem is not a bug. Atomic is currently not providing a release for amd64. I recommend switching to Comodo ruleset temporary as well as commenting the tortix source in "/etc/apt/sources.list" out to allow apt-get and plesk installer update to run smoothly.
Please sign in to leave a comment.