🛠️ Temporarily Disable Imunify360 on AlmaLinux 9 / CloudLinux 9

By /

🔍 Purpose

This guide helps you temporarily disable Imunify360 to isolate or verify whether it’s the source of issues such as blocked requests, firewall rules, or ModSecurity behavior. It applies to servers running AlmaLinux 9 or CloudLinux 9 with cPanel/WHM or Plesk.

✅ Environment

  • OS: AlmaLinux 9 / CloudLinux 9
  • Control Panel: WHM/cPanel or Plesk
  • Security Software: Imunify360 + ModSecurity

🔧 Step-by-Step Instructions

1. Stop the Imunify360 Services

SSH into the server as root, then run:

systemctl stop imunify360
systemctl stop imunify360-agent

This stops the main Imunify360 services temporarily without uninstalling the software.

2. Disable ModSecurity Vendor (Optional but Recommended)

🔹 On cPanel/WHM

Go to:
WHM » Security Center » ModSecurity® Vendors
Remove the Imunify360 ruleset (often named imunify360-full-apache).

Alternatively, run this from the terminal:

/scripts/modsec_vendor remove imunify360-full-apache

Adjust the vendor name if using LiteSpeed or a custom set.

🔹 On Plesk

Use the GUI:
Plesk » Tools & Settings » Web Application Firewall (ModSecurity)
Disable custom or Imunify360 ruleset.

Or via CLI:

plesk sbin modsecurity_ctl --disable-all-rules --ruleset custom

3. Perform Your Testing

Now that Imunify360 and ModSecurity (ruleset) are disabled, proceed with:

  • Application debugging
  • File or network testing
  • Connectivity troubleshooting
  • Checking for blocked requests

4. Re-Enable Imunify360 After Testing

When you’re done, re-enable Imunify360 and its rulesets:

systemctl start imunify360
imunify360-agent install-vendors

This ensures the rules and protection are re-applied correctly.

📚 Useful References

⚠️ Notes

  • This does not uninstall or permanently disable Imunify360.
  • Ensure you re-enable Imunify360 to maintain server security.
  • If you use LiteSpeed, also ensure ModSecurity integration is properly restored after testing.
Scroll to Top