Cannot successfully upgrade from ImunifyAV to Imunify360 with cPanel.

[ross]

I'm giving WP Squared a try: https://wpsquared.com/

Imunify360 is included as part of the bundle.

I semi-accidentally installed ImunifyAV first on my CloudLinux 8.9 cPanel 120 server, and now I'm attempting to upgrade it to Imunify360.

https://support.cpanel.net/hc/en-us/...-to-Imunify360 - this article suggests that it's NOT necessary to first uninstall ImunifyAV.

https://cloudlinux.zendesk.com/hc/en...-to-Imunify360 - this article suggests that it IS necessary to first uninstall ImunifyAV

Either way, I've tried both.

The upgrade to Imunify360 *appears* to go smoothly. In the left-hand nav of WHM > Plugins I can now see Imunify360. BUT if I click on the Imunify360 link, the page I see is titled ImunifyAV




If I click on the 'Firewall' menu option for ImunifyAV it says "Firewall integration is available in Imunify360 only. Upgrade to protect against known web attacks." If I click on the 'Upgrade Imunify' button... I just get taken back to the ImunifyAV page in WHM.

So I'm guessing that ImunifyAV did NOT uninstall fully/cleanly?

Solutions?

THx!

[ross]

A-ha!

This issue has "fixed itself". I logged in the next day, and all was well, i.e. Imunify360 was fully installed, replacing ImunifyAV

I assume that this was a caching issue that was causing my confusion. Not sure.

[alevchenko]

Hi Ross,

Happy to know it's fine!

Indeed, it could be the cache case - we had some similar cases that despite the successful upgrade the UI still reflected IMAV due to cache.
For reference: https://cloudlinux.zendesk.com/hc/en...ImunifyAV-logo

We usually recommend uninstalling ImunifyAV before installing Imunify360 to ensure there will be no leftovers that could later cause dependency issues or affect Imunify360's installation.

Best Regards!

[ross]

For the record, I definitely completely uninstalled ImunifyAV before installing Imunify360, but somehow this caching issue remained. I'm guessing others will be similarly confused by this. Perhaps documentation can be updated to caution about this, and to advise what steps to take if it does happen? I'm not sure that a simple "clear your browser cache" will work, as I'm sure I tried that (but could be mis-remembering!)

[mzhdanov]

Hello Ross,

There could be a problem with leftover ui packages. Did you check if there are any Imunify packages remaining after uninstalling IMAV? (rpm -qa | grep imunify)
In our KB, we have recommendation to remove IMAV before installation of IM360:

https://cloudlinux.zendesk.com/hc/en-us/articles/4410830256146-How-to-upgrade-from-ImunifyAV-to-Imunify360

If you still experiencing this issue, please contact our support via ticket and we will assist you with this case. If possible, please share steps to reproduce the problem.

https://cloudlinux.zendesk.com/hc/en-us/requests/new