← Knowledge Base Getting Started

Installing Safety Monitor Pro on WHM

From a fresh WHM server to your first completed scan — the whole process, with the requirements and the gotchas.

5 min

Safety Monitor Pro is a native WHM plugin. There is no external agent to run, no daemon holding a resident process, and nothing to configure on a control panel you don't already own. Installation takes a few minutes and is done entirely from inside WHM as root. This guide walks the full path: requirements, install, license activation, first scan, clean uninstall, and the handful of things that trip people up.

Requirements

Before you begin, confirm your server meets the basics:

  • WHM root access. You need to be logged into WHM as the root user (or a reseller with root-equivalent WHM privileges). The installer registers the plugin through cPanel's AppConfig system, which requires root.
  • A supported OS. Safety Monitor Pro targets the standard cPanel-supported Enterprise Linux family: AlmaLinux, Rocky Linux, and CloudLinux. If cPanel & WHM installs and runs on your box, the plugin does too.
  • cPanel & WHM installed. The plugin reads signals cPanel already produces (ModSecurity audit log, CSF/LFD state, access logs, load metrics), so a working cPanel/WHM stack is the only hard dependency.
  • A valid license key. Your key is available in your customer portal immediately after checkout. Keep it handy for the activation step.

There is no minimum RAM or CPU tier beyond what cPanel itself requires. The plugin is event-driven and log-driven rather than a polling daemon, so it does not add a measurable resident footprint.

Installing from WHM

After checkout, your download and one-line install command are shown on your order page and in the portal. To install:

  1. Log into WHM as root.
  2. Open Terminal in WHM (Home → Server Configuration → Terminal), or connect over SSH as root.
  3. Run the one-line installer shown on your order page. It downloads the plugin package, unpacks it into the plugin directory, and registers it with AppConfig so it appears in the WHM sidebar.

The command looks like this (use the exact URL/token from your order page):

bash <(curl -s https://YOUR-ORDER-INSTALL-URL/install.sh)

When the installer finishes, refresh WHM. You'll find Safety Monitor Pro under the Plugins group in the left sidebar.

License activation

The first time you open the plugin it asks for your license key. Paste the key from your portal and activate. Activation is quick and ties the license to your server IP. If your server later moves to a new IP, the license is transferable — see the Activating Your cPanel License guide for how licensing and IP transfers work.

On first entry the plugin also offers to add your current IP to the firewall allowlist, so a future block rule can never lock you out of your own server. Accept this when prompted — it's the never-block-self safeguard.

Your first scan

Once activated, open the dashboard. The plugin reads what your server has already logged and populates the live view:

  • Intrusion Monitor parses the ModSecurity audit log and shows recent web attacks broken down per domain.
  • Load Guard reads the load average and flags high-consumption users — without ever killing or throttling anything.
  • Security Health / Site Doctor runs a first pass over SSH hardening, firewall status, and backup presence.

The first scan is a read pass. It changes nothing on your server — it surfaces what's already happening and, where relevant, recommends actions that you confirm before anything is applied. For the safety model in detail, read Read-Only Mode: What It Does and Doesn't Do.

Uninstalling

If you need to remove the plugin, it uninstalls cleanly through the same AppConfig registration it used to install. As root:

  1. Run the uninstall command from your order page / documentation, or
  2. Unregister the AppConfig entry and remove the plugin directory.

Uninstalling removes the plugin and its WHM sidebar entry. Because Safety Monitor Pro is read-only by default and does not rewrite your firewall or system configuration on its own, removing it does not undo any manual firewall changes you chose to apply through it — those live in CSF, where you made them.

Troubleshooting

A few common issues and their fixes:

  • The plugin doesn't appear in WHM. Refresh the WHM page (AppConfig registration is picked up on reload). If it's still missing, re-run the installer as root — a non-root install can't register the AppConfig entry.
  • Activation fails or reports the wrong server. Confirm the server can reach the licensing endpoint outbound over HTTPS, and that the key matches this server. Licenses are keyed to the server IP; if you've migrated, transfer the license to the new IP first.
  • The Intrusion Monitor is empty. That usually means ModSecurity isn't enabled or hasn't logged events yet. Enable ModSecurity in WHM and the monitor will populate as audit-log entries arrive.
  • Locked out after a firewall change. This is exactly what never-block-self is designed to prevent — accept the allowlist prompt on first entry. If you're already locked out, allow your IP from the server console via CSF.

Ready to install? Get Safety Monitor Pro, or read the full technical documentation for architecture and resource-footprint details. Support is available during business hours (8 AM–8 PM GMT).

Chat with us →