Unable to update Atomic ModSecurity rule-set in Plesk: modsecurity_ctl failed: HTTP Error 404: Not Found

• 

  Tony March 12, 2019 15:33

  thanks. 

  0

  Comment actions Permalink
• 

  Siegfried Sbrzesny May 03, 2019 08:54

  Still there is this problem, how long? more than 2 or years and nothing changes, so slowly the management should make a head and exchange the whole floor responsible for this. If I were in this team, I would give myself a bullet, since I still have honor.

   

  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: assuming signed data in `/tmp/tmpIgsUZw/aum' gpg: Signature made Mon Apr 15 18:15:00 2019 CEST 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. converted 'https://www.atomicorp.com/RPM-GPG-KEY.atomicorp.txt' (ANSI_X3.4-1968) -> 'https://www.atomicorp.com/RPM-GPG-KEY.atomicorp.txt' (UTF-8) --2019-05-03 10:50:52-- https://www.atomicorp.com/RPM-GPG-KEY.atomicorp.txt Resolving www.atomicorp.com (www.atomicorp.com)... 74.208.77.16 Connecting to www.atomicorp.com (www.atomicorp.com)|74.208.77.16|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 1694 (1.7K) [text/plain] Saving to: 'STDOUT' 0K . 100% 32.3M=0s 2019-05-03 10:50:52 (32.3 MB/s) - written to stdout [1694/1694] W: Failed to fetch http://ftp.debian.org/debian/dists/jessie-updates/InRelease Unable to find expected entry 'main/binary-amd64/Packages' in Release file (Wrong sources.list entry or malformed file) 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

  0

  Comment actions Permalink
• 

  Lev Iurev May 06, 2019 02:33

  Hi @Siegfried Sbrzesny

  Looks like Plesk was not able to install rules due to repos issue:

  Failed to fetch http://ftp.debian.org/debian/dists/jessie-updates/InRelease Unable to find expected entry 'main/binary-amd64/Packages' in Release file (Wrong sources.list entry or malformed file) E: Some index files failed to download

  Please check the article below, apply solution and try to reinstall rules:

  https://support.plesk.com/hc/en-us/articles/360020561493

   

   

  0

  Comment actions Permalink
• 

  Pandy Legend July 30, 2019 06:19 (Edited July 30, 2019 06:20)

  I followed the above and now I get a different error:

  Failed to install the ModSecurity rule set: 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 Fri Jul 26 13:24:13 2019 BST 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. /bin/bash: line 86: /dev/?: No such file or directory /bin/bash: line 61: /dev/?: No such file or directory Required ruleset configs were not downloaded: /etc/httpd/conf/modsecurity.d/rules/tortix/modsec/*asl*.conf Unable to download tortix rule set

  This is a brand new install of Plesk on a clean server. Version 17.8.11 Update #62

  CentOS 7.6

  0

  Comment actions Permalink
• 

  Maxim Krasikov July 30, 2019 07:10

  Hello @Pandy Legend,

  Please submit a request to Plesk technical support for further investigation:
  https://support.plesk.com/hc/en-us/requests/new

  0

  Comment actions Permalink

Please sign in to leave a comment.