Troubleshooting
- ImportError: cannot import name 'HTTPError' from 'urllib3.exceptions'
- Plesk update fails: Errors during downloading metadata for repository 'imunify360-alt-php'
- ModSecurity rule cannot be disabled for the punycode domain
- IPSetNotFoundError: ipset restore failed in the Imunify360 logs
- IM360 deploy script hangs at Reading package lists
- Unable to install Imunify360 on CentOS getting errors from the `baseos` repo
- Getting `libpython3.8.so.1.0: cannot open shared object file: No such file or directory` for Imunify installation
- ImunifyAV restarts with the message: Shutting down due to inactivity.
- No implementation for feature: hardened-php
- FTP files transfer is interrupted on the server with Imunify360
- Update installation error due to Imunify360 alt-python38-PyYAML package
- Error when installing Imunify360 on a server with ARM architecture.
- Default iptables rules and Imunify360
- Imunify agent is not started due to the initialized module 'MySQLdb'
- Imunify360 dashboard displays "Medium" or "Poor" protection status
- ImunifyAV+ does not detect the KernelCare license
- ModSecurity related errors on server with Nginx and Imunify360
- Wrong IP detection
- Error during installation process: iptables required on Debian 10
- Failed to start ossec-hids service on server with Imunify360
- ModSec (WAF) ruleset is outdated
- Keep receiving Proactive Defense events though it is disabled
- ImunifyAV (ex. Revisium) scanning fails with the status "Failed to Scan"
- Imunify cleanup failed with "Failed to store original"
- Yum cannot install the best update candidate for package on server with Imunify360
- Your OS virtualization technology openvz has limited support for ipset in containers / ipset v7.1: Cannot open session to kernel
- Detect and clean the source account(s) of the outgoing email spam
- WAF rules prevent updating a website/accessing the admin area
- Imunify360 - Unable to Install on Ubuntu 20.04
- Questions and answers about RBL