• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question ModSecurity Comodo no rule update for weeks?

straddi

Basic Pleskian
Server operating system version
Debian 11.5
Plesk version and microupdate number
Plesk Obsidian 18.0.46 Update #1
Hi,
I use Comodo (free)
updated daily
A rule or rule set for ModSecurity has been installed, notification turned on.

I haven't received a notification that a new ruleset has been installed for weeks now. Is that the case with you too or do I have a problem?
How can I check when the last rule set was installed on my system?
Is there a cli command or a way in Plesk to start installing rulesets manually.
Thanks
Straddi
 
In the same situation.

I have Immunify360 and I get a notification that my ModSecurity (WAF) ruleset is out of date. I currently have version 4.93 and it is prompting me to upgrade to version 5.0.

Data:

- I have the daily ruleset update setting enabled.
- I have already tried the command via SSH of " # plesk daily UpdateModSecurityRuleSet" and no result appears.
- I have even tried reinstalling ModSecurity.

Note:

- For those who want to check their ruleset version (On Linux), the command is as follows:

#cat /etc/apache2/modsecurity.d/rules/custom/VERSION
 
Can I force an update after a reported failed attempt due to mis-configuration of the service?

And if so, how could this be achieved / done?
 
Can I force an update after a reported failed attempt due to mis-configuration of the service?

And if so, how could this be achieved / done?

I contacted Imunify support and they gave me the following steps, which solved the problem and the updates were continuous again.

1. update the agent to the latest version as described here: Update Guide
2. After that, please use the install-vendors command (if done before, do it again):
Code:
# imunify360-agent install-vendors
OK

The output should be like the below:

Code:
# plesk bin server_pref --show-web-app-firewall | grep "\[waf-rule-set\]" -A2
[waf-rule-set]
custom
 
I was looking to force an update of the rule set, which on my case, is not managed by imunify360.
 
Back
Top