Articles in this section

See more

Atomicorp Rule Set/Atomicorp Update Manager does not work on Debian 9/Ubuntu 18.04: E: Failed to fetch http://updates.atomicorp.com 404 Not Found

Avatar
Kuzma Ivanov
Updated
Follow
Plesk Onyx 17.8 for Linux kb: bug

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:

      # grep atomic /etc/apt/sources.list
      deb http://updates.atomicorp.com/channels/tortix-common/debian stretch main

 

Possible consequences

  • ModSecurity Rules by Atomicorp are missing in Plesk at Tools & Settings > Web Application Firewall (ModSecurity) even if the license key is installed.

    OR

    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 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) support@atomicorp.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

    OR

    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: 46.105.121.84 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 /var/log/plesk/install/autoinstaller3.log:

    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

Cause

Plesk Onyx does not support Atomicorp for Debian 9 (Stretch) and Ubuntu 18.04. Atomicorp rule-set for ModSecurity on Debian 9 (Stretch) and Ubuntu 18.04 has been introduced in Plesk Obsidian 18.0.21.0.

 

This is a bad error reporting bug with IDs PPPM-9037 (for Ubuntu 18.04) and PPP-31722 (for Debian 9).

Resolution

Upgrade to Plesk Obsidian.

 

Alternatively, disable Atomicorp repository on the Plesk server:

  1. Connect to the Plesk server via SSH.

  2. Run the command:

    # sed -i.backup 's@deb http://updates.atomicorp.com@#deb http://updates.atomicorp.com@g' /etc/apt/sources.list

  3. Update system packages:

    # apt-get update

Comments

13 comments

Sort by Date Votes
  • Avatar
    Graham Jones

    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...!

    0
    Comment actions Permalink
  • Avatar
    Bato Tsydenov

    @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?

    0
    Comment actions Permalink
  • Avatar
    Matthias Gaede

    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...

    0
    Comment actions Permalink
  • Avatar
    Artyom Volov (Edited )

    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.

    0
    Comment actions Permalink
  • Avatar
    Matthias Gaede

    Hi Artyom,

    thank you for your quick reply... Looking forward to hearing from you again soon

     

    Best regards

    Matthias

    0
    Comment actions Permalink
  • Avatar
    rwl (Edited )

    Regarding my today´s ticket with Atomicorp support for Ubuntu 18 will be available in summer 2019.

    0
    Comment actions Permalink
  • Avatar
    Denis Bykov

    @rwl

    Thank you for sharing this information!

    0
    Comment actions Permalink
  • Avatar
    Roman Gräbner

    Same Problem on CentOS Linux release 7.6.1810 (Core)

    0
    Comment actions Permalink
  • Avatar
    Alisa Kasyanova

    @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.

    0
    Comment actions Permalink
  • Avatar
    Roman Gräbner

    @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"

    0
    Comment actions Permalink
  • Avatar
    Dinara Aspembitova

    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
    -----

    0
    Comment actions Permalink
  • Avatar
    Mariusz Lisowski

    https://www.atomicorp.com/RPM-GPG-KEY.atomicorp.txt

    wget -q https://www.atomicorp.com/RPM-GPG-KEY.atomicorp.txt -O- | apt-key add -

     

    0
    Comment actions Permalink
  • Avatar
    Julian Bonpland Mignaquy

    Mariusz Lisowski could you provide more information on what you are trying to achieve.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles