Issue
An Imunify360 user may need to temporarily turn off Imunify360 for testing, e.g., to verify whether some problem originates from Imunify360 or from elsewhere by turning off Imunify360 and verifying if that makes the problem eliminated.
Environment
- Imunify360
- ModSecurity
- WHM/cPanel
- Plesk
Solution
1. Stop the agent
- for CentOS 6/CloudLinux OS 6:
service imunify360 stop
service imunify360-agent stop
- for all other operating systems:
systemctl stop imunify360
systemctl stop imunify360-agent
2. On servers with WHM/cPanel and Plesk control panels, also turn off ModSecurity vendor
- cPanel: in WHM > ModSecurity® Vendors or via CLI (vendor name may vary according to the web server):
/scripts/modsec_vendor remove imunify360-full-apache
- Plesk: in the Plesk panel > WAF or via CLI:
plesk sbin modsecurity_ctl --disable-all-rules --ruleset custom
3. Once you are done with the troubleshooting, you can start the Imunify360 service and install the ModSecurity vendor:
systemctl start imunify360
systemctl start imunify360-agent
imunify360-agent install-vendors
Useful links
- https://cloudlinux.zendesk.com/hc/en-us/articles/4418850990226-How-can-I-disable-Imunify360-without-uninstalling-it-
- https://docs.imunify360.com/uninstall/#how-to-stop-imunify360
- https://docs.imunify360.com/hosting_panels_specific_settin/#cpanel
- https://docs.cpanel.net/whm/security-center/modsecurity-vendors/
- https://docs.imunify360.com/hosting_panels_specific_settin/#plesk
Comments
0 comments
Please sign in to leave a comment.