We currently don't support environments which already use ea-nginx installed, but support is coming soon.
The initial conversion directly depends on the number of sites and can take a significant time on servers with a large number of them. For example, the conversion time for 3000 sites is approximately ~ 2.5 hours.
High idle memory usage - each Nginx process uses about ~2GB of memory on a server with 3000 domains.
A new account or accounts unt with changed handlers encounter conversion errors and issues with - proxy_pass. Workaround: re-trigger the conversion for the account after a few seconds.
cPanel port protection is missing.
- Workarounds:
- Whitelist the admin IP. (Note: I If the IP is already greylisted, logging in via SSH may not be possible.)
- Use cPanel service subdomains (e.g., whm.<hostname> instead of <hostname>:2087).
Python/Ruby/Node apps: Only proxy mode is supported.
Disabling ModSecurity rules per domain is not functional because there is no way to configure Coraza on a per-virtual host basis.
Uploaded file scan rule is currently blocking the upload of clean files.
Status: The rule is temporarily disabled, but real-time scans will still detect malicious files.
can be up to 90 seconds (though typically less). Efforts are underway to reduce this delay.
The imunify360-webshield-ssl-cache service is still running on the system even though it is no longer needed in an Apache-to-Nginx environment.
Coraza rules are delivered within the imunify360-modsec3-full-openlitespeed.zip file.