Issue Cannot install new Imunify

[IT Ufficio Key-One]

Server operating system version

Centos 7.9

Plesk version and microupdate number

Obsidian 18.0.63 #4

Hi, I've seen an alert that ImunifiAV will be deprecated and replaced by Imunify Extension. I'm trying to evaluate it on a spare Centos 7 with up-to-date Plesk (all our production environments are already Almalinux).

I uninstalled ImunifyAV and tried to install Imunify both from Plesk panel and from SSH, but getting a "Failed to get package version". I also followed the troubleshooting https://cloudlinux.zendesk.com/hc/e...ot-be-installed-Failed-to-get-package-version that should completely remove ImunifyAV but with no luck. Error persists.

I was able then to re-install ImunifyAV with no problem.

As I can read from the alert, we're forced to move to new Imunify Extension. Could you please help about this error?

 

[Sebahat.hadzhi]

@IT Ufficio Key-One I attempted to reproduce the issue on a CentOS 7 server with Plesk Obsidian 18.0.63, however, the installation went though without an issue. Could you please run:

yum update

and let us know if you see any errors?

 

[IT Ufficio Key-One]

@IT Ufficio Key-One I attempted to reproduce the issue on a CentOS 7 server with Plesk Obsidian 18.0.63, however, the installation went though without an issue. Could you please run:



and let us know if you see any errors?

I had to run

yum update --disablerepo=mariadb

as this spare server has an old 10.1.48 mariadb, but apart this, no errors. The server is fully updated.

 

[Tobias Sorensson]

got the same issue the extension installs via plesk extensions list and after that when i go into it.. it will try and install but all i see is just it loads the repositories and nothing else then it stopps and i have to manually uninstall the dpkg --purge --force-all imunify360-venv and do
bash i360deploy.sh --uninstall..

OS: Ubuntu 22.04.
System is up to date.
apt update
Hit:1 http://asi-fs-u.contabo.net/ubuntu jammy InRelease
Hit:2 http://asi-fs-u.contabo.net/ubuntu jammy-updates InRelease
Hit:3 http://asi-fs-u.contabo.net/ubuntu jammy-backports InRelease
Hit:4 Index of /pool/PSA_18.0.63_15508 jammy InRelease
Hit:5 Index of /PHP81_17 jammy InRelease
Hit:6 Index of /PHP82_17 jammy InRelease
Hit:7 Index of /PHP83_17 jammy InRelease
Hit:8 Index of /grafana/deb stable InRelease
Hit:9 Index of /ubuntu jammy-security InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.

i have fail2ban installed and Comodo (free) running on Apache (ModSecurity 2.9)

 

[Sebahat.hadzhi]

@IT Ufficio Key-One, the issue in your case can be caused particularly by the MariaDB repository. Please try temporarily renaming the repository as explained here and let us know if that sorted the issue.

@Tobias Sorensson the usual reason for that error is due to broken repositories. From the output, I can't see anything out of the ordinary, hence, I am not quite sure what could be causing the issue in your case, but I will try to dig deeper.

 

[IT Ufficio Key-One]

@IT Ufficio Key-One, the issue in your case can be caused particularly by the MariaDB repository. Please try temporarily renaming the repository as explained here and let us know if that sorted the issue.

@Tobias Sorensson the usual reason for that error is due to broken repositories. From the output, I can't see anything out of the ordinary, hence, I am not quite sure what could be causing the issue in your case, but I will try to dig deeper.

Thanks. Now I was able to install Imunify and activate a trial of Imunify360.

Just to clarify about the functionalities of Imunify360. It will work in conjunction with Plesk Firewall / Fali2Ban / ModSecurity or it will deactivate and substitute them with its own?

 

[Sebahat.hadzhi]

I believe ModSecurity should be automatically disabled when Imunify360 is enabled. But, if it's not, please disable it as it will most definitely cause conflicts. Fail2Ban can also cause compatibility issues with Imunify360. More about it here. As for the Plesk Firewall, there shouldn't be an issue using it along with Imunify360.