• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Imunify 360 ext breaks webmail secure access when no domain website hosting

TomBoB

Silver Pleskian
Server operating system version
AlmaLinux 8.10
Plesk version and microupdate number
18.0.80 #3
Domain subscription with no website hosting selected, only email set up. Secured with Lets Encrypt. Plesk Email Security extension loaded (in case it matters). Free Imunify extension loaded.
Webmail can be accessed on http and https, no issues.
Upgrade Imunify Free to Imunify 360. Wait the length of time until Apache [setup: Nginx as a proxy in front of Apache] has restarted. 600 secs on our case. Result: Security cert for webmail.clientdomain.com is not recognized, instead the servers main security cert is provided, leading to a security warning. Ignoring that, no access to webmail is provided as HSTS is enabled and blocks access completely.
Removing the license, then removing the extension and replacing it with the free Imunify version restores access to webmail.

Can anyone confirm? Do I need to file a bug report?
 
Back
Top