• 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!
  • 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.

Resolved ModSecurity: unable to download tortix rule set

MicheleB

Regular Pleskian
I've this error message on my Plesk installation about Firewall (ModSecurity to Atomic Basic):
*****
modsecurity_ctl failed: HTTP Error 403: Forbidden
Unable to download tortix rule set
*****
 
Ok, thanks!
This morning the error message was disappeared without my intervention.
 
Last edited:
Hi guys,
i`m sorry for posting in this old thread. But i have exactly the same problem as MicheleB had in the past:
"Failed to install the ModSecurity rule set: modsecurity_ctl failed: HTTP Error 403: Forbidden Unable to download tortix rule set"

I can activate the "OWASP ModSecurity" rule set without any error message. What can i do to activate the "Atomic Basic ModSecurity" rule set?

I hoped that the error message would disappear by itself (so i waited 2 days befor posting here). Unfortunately this didn't happend.. error message as shown above comes every time i try to activate "Atomic Basic ModSecurity".

As prprtl mentioned the issue is regarding the free Atomic Basic ModSecurity ruleset. The article posted in this thread doesn`t help.

Thank you all in advanced for any kind of help!
 
At the moment bugreport PPPM-6302 is under developer's investigation.
 
Back
Top