Failed to update the ModSecurity rule set: Authorization failed attempting to download an update

Created:

2016-11-16 12:41:43 UTC

Modified:

2017-08-08 13:15:04 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Failed to update the ModSecurity rule set: Authorization failed attempting to download an update

Symptoms

Attempting to update Atomic ModSecurity rule set results in error:

Error message or request description : Error: Failed to update 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 Tue Jun 23 00:10:58 2015 EEST 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.
aum failed with exitcode 3.
stdout:

Checking versions ...

ASL version is current: �[PASS]

Authorization failed attempting to download an update.
The username or password may be invalid, or your license may be expired.
Please log in to the License Manager at https://www.atomicorp.com/ame
mber/member.php and verify your account.

Further information may be found at: https://www.atomicorp.com/wiki/index.php/ASL_FAQ#HTTP_Error_401:_Authorization_Required.
-------------------------------------------------------------------------------
Errors were encountered:
L CODE SOURCE MESSAGE
- ---- ----------------------------- ------------------------------------------ �
[0;33m2 302 Core::distributed_update remote fail: E_GEN_RETRY 22 .. www3.atomic orp.com/channels/rules/subscription/modsec -201506230902.tar.bz2 �
[0m�[1;31m3 303 Core::distributed_update Invalid user credentials �[0m

stderr:
Unable to download tortix rule set

Cause

Incorrect username/password or license is expired.

Resolution

1. Move contents of /var/asl/rbc/etc/asl/config:

# mv /var/asl/rbc/etc/asl/config ./

2. Check username/password in /etc/asl/config configuration file

3. If Atomic ModSecurity (subscription) rule set is used, log in to the Atomic License Manager and verify the account. Ensure that credentials used in Plesk in /etc/asl/config file to download Atomic ModSecurity ruleset are valid. Further information can be found on Atomic website

Have more questions? Submit a request
Please sign in to leave a comment.