Let us look at how to remove the error Failed to update the ModSecurity rule set. With the support of our Apache hosting support services at Bobcares we will now learn more about the error.

Error: Failed to update the ModSecurity rule set: Symptoms

The ModSecurity rule set is an error message that appears when the ModSecurity web application firewall is unable to update its rules. This may be due to an incompatibility between the current version of ModSecurity and the rule set, or due to the rule set being unavailable.

Following the unsuccessful ModSecurity upgrade, the Plesk Home page displays the following error:

Error: Failed to update the ModSecurity rule set. Details

The following error may be seen in the Tools & Options > Web Application Firewall (ModSecurity) menu:

Code: [Select]
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 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.
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
[0m127.0.0.1
127.0.0.1
203.0.113.2
stderr:
Unable to download tortix rule set

Error: Failed to update the ModSecurity rule set: Resolution

To troubleshoot this issue, the user should first check to see if the server can connect to the update server. If it can, then you should check the server logs for any additional errors that may be present. The user should also make sure that the rule set is up to date and that the server is able to download the rule set updates. If all else fails, then the user may need to contact their hosting provider to see if they can provide any additional assistance.

When attempting to login to an Atomicorp account using credentials from the /etc/asl/config file, the following error is displayed:

The user name or password is incorrect

For resolving the ModSecurity rule set error follow the steps given below:

1. SSH is used to connect to the server.
2. Manually update the ModSecurity rule set:

# /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php -f UpdateModSecurityRuleSet

[Need assistance with similar queries? We are here to help]

Conclusion

To sum up, we have now seen how to remove the error Failed to update the ModSecurity rule set. With the support of our Apache hosting support services at Bobcares, we have now seen how to remove the error easily. We have now gone through the two major troubleshooting steps and the code line necessary to remove the error.