Applicable to:
- Plesk for Linux
- Plesk for Windows
Symptoms
-
This message is displayed in the panel after a failed ModSecurity ruleset update
Error: Failed to update the ModSecurity rule set. Details
-
Trying to log in to Atomicorp with the credentials inside
/etc/asl/config
returns this errorThe user name or password is incorrect
-
One of the following errors appears in Tools & Settings > Web Application Firewall (ModSecurity)
Press to expandError: 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 Thu Mar 15 01:24:49 2018 +07 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.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 Mon Apr 15 18:15:00 2019 CEST 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 ...
AUM version is current: package asl is not installed[75G[[1;31m[1;32mPASS[0m[0m]
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/amember/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-
---- ----------------------------- ------------------------------------------
[1;31m3 303 Core::distributed_update Invalid user credentials
[0m159.69.178.159
203.0.113.2
stderr:
Unable to download tortix rule setError: Failed to update the ModSecurity rule set: modsecuritymng failed: Error sending request 'channels/rules/plesk/modsec-201905100838.tar.bz2' to 'updates.atomicorp.com': status 401
at (WebRequest::executeRequest line 122)
at executeRequest(updates.atomicorp.com/channels/rules/plesk/modsec-201905100838.tar.bz2)(WebRequest::executeRequest line 127)
at downloadFile(updates.atomicorp.com/channels/rules/plesk/modsec-201905100838.tar.bz2)(WebRequest::downloadFile line 145)
at download(C:\Program Files (x86)\Plesk\PrivateTemp\460E7B5.tmp)(ModSecurity::TortixRuleSet::download line 90)
at installRuleSet(tortix, )(ModSecurity::Adapter::installRuleSet line 62)
at installRuleSet(tortix, , true)(ModSecurityManager::installRuleSet line 47)
at execute console command --install-ruleset(vconsoleapp::start line 93)
at execute "C:\Program Files (x86)\Plesk\admin\bin\modsecuritymng" --install-ruleset --with-backup "--ruleset=tortix"(vconsoleapp::run line 110)
(Error code 1)
Cause
Temporary issue on Atomicorp's end.
Resolution
Wait a few hours after the error, and then follow the appropriate steps for the system.
-
Connect to the server over SSH
-
Update the ModSecurity ruleset manually:
# plesk daily -f UpdateModSecurityRuleSet
-
Connect to the server over RDP
-
Update the ModSecurity ruleset manually using a command prompt:
"%plesk_bin%\modsecuritymng" --install-ruleset --with-backup "--ruleset=tortix"
Note: The command's ruleset name
tortix
has been taken from the error message
Comments
0 comments
Please sign in to leave a comment.