Fix Imunify360 license errors and unregistered agent

Imunify360 stops protecting the box and the dashboard throws No valid license was found for this Imunify360 installation, or the agent quietly drops to AV-only. The license itself is almost never gone — it's a registration mismatch, a stale binding to a server you've already retired, or a user count that's run past your tier. Each has a different fix, and running the wrong registration command for your license type is the single most common reason this drags on.

This is the order to work through it. Confirm each step before changing anything.

Step 1: read what the agent actually reports

Every diagnosis starts here. Ask the agent for its registration status:

imunify360-agent rstatus

A healthy server prints OK. For the detail you need to act on, get the full record:

imunify360-agent rstatus --json -v

Watch four fields: status, license_type, user_count, and user_limit. "status": true means the license is valid and the rest of this article doesn't apply — your problem is elsewhere (start with high CPU and RAM usage if the agent is installed but misbehaving). "status": false plus a message is what routes the rest of this decision tree.

Step 2: is the user count over the limit?

If user_count is at or above user_limit, the message is License is invalid for this server and nothing else is wrong — you've simply outgrown the tier. Imunify360 counts every cPanel/Plesk account with a home directory, including suspended ones. Count them:

ls -1 /var/cpanel/users | wc -l

Either delete dead accounts, or move up a tier. Flat per-server "unlimited users" licenses report user_limit: 2147483647 and never hit this — if you're on a per-user tier and bumping the ceiling repeatedly, the unlimited SKU is usually cheaper than babysitting the count. See the Imunify product tiers for where the lines fall, or the contact page to change tier.

Step 3: re-register with the correct license type

This is where most tickets are actually resolved. Imunify360 licenses are key-based or IP-based, and they register with different syntax.

Key-based — you were handed an activation key string:

imunify360-agent register IM250sdfkKK245kJHIL

IP-based — you gave a vendor your server's IP and no key. Register with the literal word IPL, not the actual IP address:

imunify360-agent register IPL

Then re-check:

imunify360-agent rstatus

Resellers (us included) issue IP-based licenses by default, so register IPL is the right command for most panellicense customers. If you bought direct from CloudLinux or bundled it through cPanel's store, you likely have a key.

Step 4: clear a stale binding after a migration

If registration fails because the key is already registered on another installation, the license is still bound to a server you've migrated off or rebuilt. Release it from the old box first:

# on the OLD server, if you can still reach it
imunify360-agent unregister

Then run the Step 3 register command on the new server. If the old server is gone — snapshot deleted, hardware returned — you can't unregister from it, so the binding has to be reset in the licensing backend. For licenses bought from us, the contact page clears a stale IP or key binding in minutes; for direct CloudLinux purchases, open a ticket with CLN to reset it.

Step 5: force a re-check after a renewal or tier change

If you just renewed, changed tier, or freed up accounts but rstatus still shows the old verdict, the agent is caching a stale licence state. Force it to re-poll CLN:

imunify360-agent update-license
imunify360-agent rstatus

If update-license itself fails, the box can't reach the licensing servers — check outbound HTTPS to *.imunify360.com isn't being eaten by a CSF or firewall rule. A blocked outbound connection produces the same "no valid license" symptom as an actual licensing problem.

Plesk-specific note

Plesk universal keys cover most extensions, but Imunify is licensed separately. If Plesk shows No valid license was found for this Imunify360 installation while other extensions are fine, the universal key doesn't include Imunify — you register the agent directly with imunify360-agent register exactly as above, independent of Plesk's key. See installing Imunify360 on Plesk for the full activation path.

Next steps

• Imunify AV vs AV+ vs Imunify360 — pick the right tier so you stop hitting the user-count ceiling
• Imunify360 agent CLI reference — the full command set beyond register and rstatus
• Activate or move an Imunify360 license — IP and key changes routed through in minutes