Emergency server help: get in touch

Imunify360 Missing from WHM: 4 Fixes

Restore the Imunify360 icon in WHM when the plugin is registered but disabled, the agent is stopped, the install was corrupted, or a cPanel update removed the plugin registration, using imunify360-agent enable-plugin and reinstall steps.

Published Updated 6 min read

Short answer: A missing Imunify360 icon in WHM usually means the WHM plugin is disabled, not that protection has stopped. Run imunify360-agent enable-plugin as root, then log out of WHM and back in. If the icon still does not return, confirm the agent and licence are healthy, restart the imunify360 service if it has stopped, and as a last resort download i360deploy.sh again and rerun it. Check the agent and licence first with imunify360-agent rstatus. (Reviewed October 2026.)

Applies to Imunify360 on cPanel & WHM servers, using the current imunify360-agent CLI and the i360deploy.sh installer (ImunifyAV uses imav-deploy.sh)

Imunify360 normally appears as an icon under the Plugins section of WHM and as a menu entry in the left sidebar. When it disappears, the firewall may still be running perfectly underneath, or it may have stopped entirely; the interface gives no clue which. The causes fall into a handful of buckets: the plugin was deliberately or accidentally disabled, the agent service is down so the plugin refuses to render, the WHM plugin files were removed or corrupted by an interrupted install, or a cPanel upgrade rebuilt the plugin registry without the entry. Each has a quick check and a quick fix.

Check whether the plugin is disabled

Imunify360 keeps a plugin state separate from the agent. Support staff sometimes disable it to isolate a problem, and a scripted deployment may leave it off. Re-enable and check the agent state:

imunify360-agent enable-plugin
imunify360-agent rstatus
imunify360-agent version

Then log out of WHM completely and log back in, because the sidebar and plugin list are built at login. If the icon is present but clicking it shows a page stating the agent is not running, the plugin is fine and the service is the problem.

Restart a stopped agent

The agent service must be active for the WHM page to load anything:

systemctl status imunify360
systemctl restart imunify360
journalctl -u imunify360 --since "15 min ago" | tail -50

The journal shows whether the agent failed on startup, commonly because of a corrupt SQLite database after a disk-full event, an expired licence, or a Python dependency broken by an OS update. A licence problem shows in rstatus; a database problem shows as an integrity error in the log and is checked with imunify360-agent checkdb, which saves a backup copy of a corrupt database in /var/imunify360 but destroys the broken database if it cannot restore it. imunify360-agent doctor does not repair anything; it collects a report and gives you a key to send to Imunify360 support. Disk space should be confirmed with df -h /var before anything else.

Re-register the WHM plugin

cPanel tracks third-party WHM plugins in its own registry. If the plugin is enabled but still missing, confirm its files and WHM registration exist and enable it again:

ls -la /usr/local/cpanel/whostmgr/docroot/cgi/imunify/
ls /var/cpanel/apps/ | grep -i imunify
imunify360-agent enable-plugin

Do not use /usr/local/cpanel/scripts/install_plugin for this: it installs cPanel interface plugins into a cPanel theme, while WHM plugins are registered through AppConfig files in /var/cpanel/apps/. If the directory under the WHM docroot is empty, the plugin was removed and a reinstall is the fastest route.

Reinstall the plugin cleanly

Download the deployment script fresh and rerun it. A message such as “file too short” during a previous install indicates a truncated download, often caused by a proxy or a full disk, and the resulting package is unusable:

cd /root
wget -O i360deploy.sh https://repo.imunify360.cloudlinux.com/defence360/i360deploy.sh
bash i360deploy.sh

The script detects the existing installation, verifies the packages and restores the WHM plugin. Licences, blocked lists, whitelists and WAF settings are stored in the agent’s database and survive the reinstall. If the deploy script itself fails to download, check outbound HTTPS from the server and any local CSF rule that might be blocking the repository host, then compare the file size with the one on the vendor site before running it. For ImunifyAV installations the equivalent script is imav-deploy.sh.

Verify

Log in to WHM and confirm the Imunify360 entry under Plugins opens the dashboard with the version shown in the footer. From the shell, imunify360-agent rstatus should report the licence as valid and imunify360-agent version should match the latest rollout stage for your server; if it is behind, see Update, force-update or roll back Imunify360. Check that systemctl is-active imunify360 imunify360-webshield prints active for both.

The common pitfall is assuming a missing icon means the firewall is off and hastily installing CSF or another firewall on top. Imunify360 does support running alongside CSF (it then switches off its own Blocked Ports, DoS Protection and SMTP Traffic Manager features), but adding a firewall does nothing for a missing WHM icon. Confirm the state of the agent first, and if you really need to remove Imunify360, use the documented bash i360deploy.sh --uninstall (add --downgrade to keep the free ImunifyAV scanner).

Imunify360 missing from WHM at a glance

Imunify360 Missing from WHM – short answer
In short: Restore the Imunify360 icon in WHM when the plugin is registered but disabled, the agent is stopped, the install was corrupted, or a cPanel update removed the plugin registration, using imunify360-agent enable-plugin and reinstall steps.
Imunify360 Missing from WHM – what this guide covers
Imunify360 Missing from WHM: what this guide covers.
Imunify360 Missing from WHM – questions answered
Imunify360 Missing from WHM: the questions this guide answers.

Official documentation (checked 9 October 2026): cPanel Support: Imunify360 missing in WHM interface · Imunify360 docs: Command-line interface · Imunify360 docs: Installation · Imunify360 docs: Uninstall · Imunify360 docs: IDS integration (CSF) · cPanel Support: Are Imunify360 and CSF compatible · cPanel Support: Install Imunify360 · cPanel docs: The install_plugin Script · cPanel Developer Docs: Guide to WHM Plugins – Add Plugins · Imunify360 docs: ImunifyAV

Related guides: Fix WordPress “cURL error 28: Failed to connect” caused by Imunify360 or CSF · Whitelist IPs and countries in Imunify360 from the CLI · Imunify360 in 2026: WAF by default, L7 rate limiting and Under Attack Mode tuning.

Frequently asked questions

Does Imunify360 missing from WHM mean the firewall has stopped protecting the server?

Not necessarily. The WHM plugin is only the interface; the agent, WebShield and WAF continue running if the service is active, which systemctl status imunify360 and imunify360-agent rstatus confirm.

How long does reinstalling the Imunify360 plugin take?

Running enable-plugin and re-logging takes a minute. A full rerun of i360deploy.sh takes five to ten minutes depending on how many packages need to be re-downloaded.

Can I undo a plugin reinstall or restore a previous state?

Nothing needs undoing: the reinstall replaces only the interface files and packages. Whitelists, blacklists and settings remain in the agent’s database, which you can back up beforehand with a copy of /var/imunify360/. (imunify360-agent backup-systems manages backup-system integrations; it does not back up Imunify360’s own settings.)

Share this guide

Free website test

Is your website set up right?

Check SSL, security headers, redirects, robots.txt, sitemap, llms.txt and security.txt in one test. It takes about 30 seconds.