• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Imunify upgrade failed!

LionKing

Regular Pleskian
Server operating system version
Ubuntu 24.04.1
Plesk version and microupdate number
Version 18.0.66 Update #2
Hello fellas.
I just attempted to run and upgrade Imunify as per announced recommendation but it fails and will not start the Imunify service.

Here is the error when I tried to start it in the command prompt:

1738367671130.png

I have no clue what to do from here....
Thoughts?

Thanks in advance!
 
Here is the installation log on Pastebin:
imunify-installation-log - Pastebin.com
The main issue seems to be this (?):
Code:
[2025-02-01 01:02:04] [2025-02-01 01:02:04] Waiting for ImunifyAV to start...[2025-02-01 01:02:05] [2025-02-01 01:02:05] ERROR: imunify360 service is stopped.

Thanks again.
Kind regards
 
Well...
I solved it myself (Cheating a bit with the help of ChatGPT :cool:) .

So I will post the solution for others that might run into the same issue:

In systemd (which Plesk uses on most Linux distributions), a "masked" service means it has been explicitly disabled and cannot be started or enabled until it is "unmasked."

To check the status and fix it, follow these steps:

1. Check if the service is masked​

Run this command in SSH:

bash

Code:
systemctl is-enabled imunify-antivirus

If it returns masked, then the service is indeed disabled.

2. Unmask the service​

Run the following command to unmask it:

bash

Code:
systemctl unmask imunify-antivirus

3. Enable and Start the Service​

After unmasking, try enabling and starting the service:

bash

Code:
systemctl enable imunify-antivirus --now

4. Verify the Service Status​

Check if it’s running correctly:

Bash

Code:
systemctl status imunify-antivirus

If the issue persists, try reinstalling ImunifyAV:

bash

Code:
plesk installer --select-release-current --install-component imunify-antivirus

Result:
1738369562420.png

Hope this helps other people here on the forums! ;)
Kind regards
 
Back
Top