Imunify360 is not functioning in Plesk: Imunify agent is not running Follow the troubleshooting guide or contact support

Symptoms

• Imunify360 is not operable in Plesk with:

  Imunify agent is not running
  Follow the troubleshooting guide or contact support

• It is not possible to collect the report with the command below:

  # imunify360-agent doctor
  Traceback (most recent call last):
  File "/usr/bin/imunify360-agent", line 33, in <module>
  sys.exit(load_entry_point('imunify360-firewall==6.10.1', 'console_scripts', 'imunify360-agent')())
  File "/usr/bin/imunify360-agent", line 25, in importlib_load_entry_point
  return next(matches).load()
  File "/opt/alt/python38/lib/python3.8/importlib/metadata.py", line 77, in load
  module = import_module(match.group('module'))
  File "/opt/alt/python38/lib/python3.8/importlib/__init__.py", line 127, in import_module
  return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
  File "<frozen importlib._bootstrap>", line 991, in _find_and_load
  File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 843, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/opt/alt/python38/lib/python3.8/dist-packages/im360/cli.py", line 2, in <module>
  from defence360agent import defence360
  ModuleNotFoundError: No module named 'defence360agent'

Cause

Issue on Cloudlinux side: https://cloudlinux.statuspage.io/incidents/xc78wfbwhbj4 which is under investigation by Imunify360 developers.

Resolution

Until the issue is resolved, as a workaround force Imunify360 updates with the commands below:

1. Connect to the server via SSH.

2. Download and launch the script:

   # wget -O imunify-force-update.sh https://repo.imunify360.cloudlinux.com/defence360/imunify-force-update.sh && bash imunify-force-update.sh

   Note: When the script stops at The default action is to keep your current version. *** ossec-init.conf (Y/I/N/O/D/Z) [default=N] ? just hit Enter to proceed.