• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved Error by activating ModSecurity with Atomic Basic Ruleset

Tobias Reinhard

New Pleskian
Hi Pleskians,

yesterday i installed a fresh Debian 9.4 installation to check the new Plesk Onyx 17.8.11. Everything runs fine, except for the error named in title. I really don't know what i can do. I'm not able to activate the Web Application Firewall with the Atomic ModSecurity Ruleset (Free Version), Plesk only gives me this error:

Failed to install the ModSecurity rule set: modsecurity_ctl failed: gpg: key FFBD5D0A4520AFA9: "Atomicorp (Atomicorp Official Signing Key) <[email protected]>" not changed gpg: Total number processed: 1 gpg: unchanged: 1 gpg: assuming signed data in '/tmp/tmpbB35DF/aum' gpg: Signature made Mon Mar 19 19:35:49 2018 CET gpg: using RSA key FFBD5D0A4520AFA9 gpg: Good signature from "Atomicorp (Atomicorp Official Signing Key) <[email protected]>" [unknown] 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. --2018-03-22 08:47:40-- 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... Warning: apt-key output should not be parsed (stdout is not a terminal) connected. HTTP request sent, awaiting response... 200 OK Length: 1694 (1.7K) [text/plain] Saving to: 'STDOUT' 0K . 100% 166M=0s 2018-03-22 08:47:41 (166 MB/s) - written to stdout [1694/1694] W: The repository 'Atomicorp stretch Release' does not have a Release file. E: Failed to fetch http://updates.atomicorp.com/channels/tortix-common/debian/dists/stretch/main/binary-i386/Packages 404 Not Found [IP: 173.203.184.213 80] 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
 
Back
Top