RootManage.com Rootscan Plugin: Quick Overview & Benefits

Running a website or application on a VPS or dedicated server means you constantly juggle performance, security, and reliability. Even with a solid hosting provider like AtoZNode, the tools you choose can make a big difference in how easily you keep your environment healthy. One such tool is the RootsCan plugin from RootManage.com. In this article, we’ll walk through what RootsCan does, why it matters for Indian server owners, and how to get it up and running on the most common Linux distributions.

What is the RootsCan plugin?

RootsCan is a lightweight, open-source scanning utility that integrates with the RootManage platform. Its primary purpose is to identify:

• Out-of-date system packages and libraries.
• Known vulnerable binaries and configuration files.
• Unusual file permissions that could expose sensitive data.
• Potentially unwanted services that waste resources.

The plugin runs as a scheduled job, generates a concise HTML report, and can optionally push findings to RootManage’s dashboard for centralized monitoring. Because it focuses on the operating-system layer rather than application-specific checks, it works well on any Linux server that hosts websites, APIs, or container workloads.

Why Indian VPS owners should consider RootsCan

India’s internet landscape is growing rapidly, and so are the threats targeting local servers. While AtoZNode provides robust network infrastructure, patch management and hardening still rest with the administrator. RootsCan helps you:

1. Stay compliant with local regulations. The Ministry of Electronics and Information Technology recommends regular vulnerability assessments for servers handling personal data.
2. Reduce downtime. Early detection of outdated packages prevents unexpected crashes during traffic spikes.
3. Save bandwidth. By spotting unused services, you can shut them down and keep your monthly data quota under control.
4. Maintain a clean audit trail. The HTML reports are easy to archive and share with auditors or development teams.

Installation Overview

RootsCan is distributed as a single .tar.gz archive. The installation steps are identical on Debian-based systems (Ubuntu, Debian) and on RHEL-based systems (AlmaLinux, Rocky Linux, CentOS). Below, we provide separate command blocks for each family, explain what each line does, and note any Windows-specific considerations.

Prerequisites

• Root (or sudo) access to the server.
• Internet connectivity to download the plugin.
• Basic utilities: wget, tar, curl.

Step-by-step for Debian/Ubuntu (apt)

# Update package index
sudo apt update
# Install required utilities if they are missing
sudo apt install -y wget tar curl
# Create a directory for the plugin
sudo mkdir -p /opt/rootscan
# Download the latest release (replace URL with the current version)
sudo wget -O /opt/rootscan/rootscan.tar.gz \
    https://rootmanage.com/downloads/rootscan-latest.tar.gz
# Extract the archive
sudo tar -xzvf /opt/rootscan/rootscan.tar.gz -C /opt/rootscan --strip-components=1
# Set executable permissions on the main script
sudo chmod +x /opt/rootscan/rootscan.sh
# Verify the installation
/opt/rootscan/rootscan.sh --version

What each command does:

• apt update refreshes the local package list so you get the newest versions of dependencies.
• apt install -y wget tar curl ensures the three tools needed for download and extraction are present.
• mkdir -p /opt/rootscan creates a dedicated directory under /opt, a common location for third-party software.
• wget -O … fetches the compressed plugin archive and saves it with a predictable name.
• tar -xzvf … extracts the archive, removing the top-level folder so files land directly in /opt/rootscan.
• chmod +x makes the main script executable.
• Running the script with --version confirms that the binary works and shows the installed version.

Step-by-step for AlmaLinux/Rocky/CentOS (dnf)

# Refresh the repository metadata
sudo dnf makecache
# Install required utilities if they are missing
sudo dnf install -y wget tar curl
# Create a directory for the plugin
sudo mkdir -p /opt/rootscan
# Download the latest release
sudo wget -O /opt/rootscan/rootscan.tar.gz \
    https://rootmanage.com/downloads/rootscan-latest.tar.gz
# Extract the archive
sudo tar -xzvf /opt/rootscan/rootscan.tar.gz -C /opt/rootscan --strip-components=1
# Make the script executable
sudo chmod +x /opt/rootscan/rootscan.sh
# Verify the installation
/opt/rootscan/rootscan.sh --version

The commands mirror the Debian/Ubuntu flow; the only differences are the package manager (dnf instead of apt) and the cache-refresh command (makecache).

Configuring a regular scan

Running RootsCan manually is fine for a one-off check, but the real value appears when you schedule it. Below are example cron entries for daily scans that store the report in /var/www/html/reports (a typical web-accessible path on AtoZNode servers).

Debian/Ubuntu cron job

# Open the root crontab
sudo crontab -e
# Add the following line (runs at 02:30 am every day)
30 2 * * * /opt/rootscan/rootscan.sh --output /var/www/html/reports/rootscan-$(date +\%F).html

AlmaLinux/Rocky/CentOS cron job

sudo crontab -e
30 2 * * * /opt/rootscan/rootscan.sh --output /var/www/html/reports/rootscan-$(date +\%F).html

Explanation:

• 30 2 * * * schedules the job for 02:30 am server time.
• --output tells RootsCan where to write the HTML report.
• $(date +\%F) inserts the current date (YYYY-MM-DD) into the filename, creating a new report each day.

If your server runs Windows Server, you would use Task Scheduler instead of cron. The same command-line arguments apply; just point the task to powershell.exe and the script’s Windows path.

Understanding the generated report

After a scan completes, open the HTML file in a browser. The report is divided into four sections:

1. Package Updates – Lists installed packages with newer versions available in the official repositories.
2. Vulnerability Findings – Shows CVE identifiers (if any) matched against the installed binaries. The plugin pulls data from the public NVD feed; no proprietary database is required.
3. Permission Anomalies – Highlights files or directories that are world-writable or owned by unexpected users.
4. Service Audit – Enumerates listening ports and the associated services, flagging any that are not part of your documented stack.

Each entry includes a short description and a recommended remediation command. For example, a missing security patch for openssl will show:

Package: openssl
Current version: 1.1.1f-1ubuntu2
Latest version: 1.1.1k-1ubuntu2
Remediation: sudo apt upgrade openssl   # (or sudo dnf upgrade openssl on RHEL-based)

You can copy the suggested command directly into your terminal, or use the “Apply All” button on the RootManage dashboard to automate the upgrade via an API token.

Integrating RootsCan with RootManage’s dashboard

While the HTML report is useful for local review, many administrators prefer a central view, especially when managing multiple VPS instances on AtoZNode. To enable dashboard integration:

1. Create an API token on your RootManage account (Settings → API → Generate Token).
2. Save the token in a secure file on the server, e.g., /etc/rootscan/token, with permissions 600.
3. Edit the plugin’s configuration file (/opt/rootscan/config.ini) and add:

[dashboard]
api_url = https://api.rootmanage.com/v1/report
token_file = /etc/rootscan/token

Now every scheduled run will POST the JSON payload to RootManage, where you can view trends, set alerts, and assign tickets to your team. The plugin respects the --dry-run flag, allowing you to test the upload without actually sending data.

Best practices for using RootsCan on AtoZNode servers

• Run scans after major updates. Schedule an additional scan 30 minutes after a system upgrade to verify that no new vulnerabilities were introduced.
• Keep the plugin up to date. The RootsCan project releases minor updates roughly every month. Replace the archive with the latest version using the same steps as the initial install.
• Combine with application-level checks. RootsCan covers the OS layer; consider complementary tools like OWASP ZAP for web-app security.
• Archive reports. Retain at least three months of HTML reports for compliance audits. A simple logrotate configuration can automate cleanup.

Conclusion

The RootsCan plugin from RootManage.com offers a pragmatic way for Indian developers and sysadmins to keep their AtoZNode VPS or dedicated servers secure and up to date. By installing a single script, scheduling daily scans, and optionally feeding results into a central dashboard, you gain visibility into package health, vulnerability exposure, and service hygiene without adding heavy overhead. Follow the installation steps for your distribution, adopt the suggested cron schedule, and you’ll have a reliable, low-maintenance safety net for the servers that power your websites and applications.