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

Applicable to:

  • Plesk 17.8 for Linux

Symptoms

  • Debian 9 (Stretch) or Ubuntu 18.04 is installed on a server.

  • 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

  • The following error messages appear when installing system updates:

    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.

  • ModSecurity with Atomic Ruleset is missing at Tools & Settings > Web Application Firewall (ModSecurity) even when the license key is applied.

    OR

    It is not possible to use ModSecurity with Atomic Ruleset 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

  • Plesk Installer fails with the following message:

    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

This case was registered in our system to make it easier to track down: PPP-31722.

Resolution

Temporary disable Atomicorp repository:

  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

    Note: Until Atomicorp starts supporting Debian 9, it is possible to use Comodo rule set for ModSecurity. To get additional information, visit Plesk Administrator's Guide - Web Application Firewall (ModSecurity)

  3. Run the command:

    # apt-get update

Comments

5 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
    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
    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
    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
    Permalink
  • Avatar
    Matthias Gaede

    Hi Artyom,

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

     

    Best regards

    Matthias

    0
    Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles