- Plesk Onyx 17.8 for Linux
Debian 9 (Stretch) or Ubuntu 18.04 is installed on a server and Atomic repository is enabled in
# grep atomic /etc/apt/sources.list
deb http://updates.atomicorp.com/channels/tortix-common/debian stretch main
ModSecurity Rules by Atomicorp are missing in Plesk at Tools & Settings > Web Application Firewall (ModSecurity) even if the 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) firstname.lastname@example.org" not changed gpg: Total number processed: 1 gpg: unchanged: 1 gpg: assuming signed data in '/tmp/tmp0gqEvD/aum' gpg: Signature made Wed Jun 20 22:13:55 2018 +07 gpg: using RSA key FFBD5D0A4520AFA9 gpg: Good signature from "Atomicorp (Atomicorp Official Signing Key) email@example.com" [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.
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.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
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
CONFIG_TEXT: 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-i386/Packages 404 Not Found [IP: 188.8.131.52 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.
Plesk Installer fails with:
PLESK_ERROR: Installation will not continue
Reading package lists…
Building dependency tree…
Reading state information…
and the following error message appears in
CONFIG_TEXT: E: Version '17.8.11-debian9.0.build1708180314.14' for 'pp17.8.11-bootstrapper' was not found
E: Version '17.8.11-debian9.0.build1708180314.16' for 'plesk-l10n' was not found
Currently, Plesk does not support Atomicorp for Debian 9 (Stretch) and Ubuntu 18.04 yet.
For additional information refer to the article Unable to select Atomicorp rule set in Plesk for Ubuntu 18.04/ Debian 9
This is a bad error reporting bug with IDs PPPM-9037 (for Ubuntu 18.04) and PPP-31722 (for Debian 9).
Temporary disable Atomicorp repository on the 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
Note: Until Atomicorp starts supporting Debian 9 and Ubuntu 18.04, use Comodo rule set for ModSecurity. To get additional information, visit Plesk Administrator's Guide - Web Application Firewall (ModSecurity).