Monitoring CyberPanel with Vigilmon

CyberPanel is a modern open-source hosting control panel built on OpenLiteSpeed, offering LiteSpeed Cache integration, Docker-friendly workflows, and a free alternative to cPanel or DirectAdmin for high-performance PHP and WordPress hosting. Managing your own CyberPanel server means you own the uptime story — there's no managed support tier watching whether the panel itself is reachable. Vigilmon gives you HTTP availability checks, REST API health probes, TCP port monitoring, SSL certificate alerts, and heartbeat monitoring for CyberPanel's scheduled tasks, all in one place.

What You'll Set Up

• HTTP monitor for the CyberPanel web UI (port 8090 HTTPS login page)
• REST API endpoint availability check (/api/cyberPanel)
• TCP port monitor for the OpenLiteSpeed admin UI (port 7080)
• SSL certificate expiry alerts for the management interface and hosted sites
• Cron heartbeat monitoring for CyberPanel scheduled tasks (backups, Let's Encrypt renewal, malware scans)

Prerequisites

• CyberPanel installed and running on a VPS or dedicated server
• At least one website managed through CyberPanel
• A free Vigilmon account

Step 1: Monitor the CyberPanel Web UI (Port 8090)

CyberPanel's management interface runs on HTTPS port 8090. If this port goes down, you and your customers lose access to the entire control panel.

1. Log in to vigilmon.online and click Add Monitor.
2. Set Type to HTTP / HTTPS.
3. Enter your CyberPanel URL: https://your-server-ip:8090 or https://panel.yourdomain.com:8090.
4. Set Check interval to 1 minute.
5. Set Expected HTTP status to 200.
6. Click Save.

CyberPanel's login page returns HTTP 200 for the initial page load. If the panel service has crashed or the port is blocked by a firewall rule change, Vigilmon alerts you immediately.

Step 2: Monitor the CyberPanel REST API Endpoint

CyberPanel exposes a REST API at /api/cyberPanel that drives all panel operations — website creation, DNS management, email provisioning. Monitoring the API endpoint separately from the UI catches backend failures where the login page is still served by a cached proxy but the API layer is broken.

1. In Vigilmon, click Add Monitor → HTTP / HTTPS.
2. Set the URL to https://your-server-ip:8090/api/cyberPanel.
3. Set Expected HTTP status to 200.
4. Under Response body, enable Contains keyword and enter {"status": to verify a JSON response is returned.
5. Set Check interval to 2 minutes.
6. Click Save.

The API returns a JSON body on every valid request. A keyword check on {"status": ensures the application layer is healthy, not just the web server.

Step 3: Monitor OpenLiteSpeed Admin UI (TCP Port 7080)

OpenLiteSpeed — the web server powering CyberPanel — has its own admin interface on port 7080. Monitoring this port confirms that OpenLiteSpeed itself is running, independent of the CyberPanel application layer.

1. In Vigilmon, click Add Monitor → TCP Port.
2. Enter your server's hostname or IP.
3. Set Port to 7080.
4. Set Check interval to 2 minutes.
5. Click Save.

A TCP connection failure on port 7080 means OpenLiteSpeed has stopped, which also means all hosted websites are down. This is the broadest availability signal in your CyberPanel stack.

Step 4: SSL Certificate Alerts for CyberPanel and Hosted Sites

CyberPanel manages Let's Encrypt certificates for both the management interface and every hosted site. Auto-renewal runs as a scheduled task, but it can fail silently when DNS propagation is slow or the HTTP challenge port is temporarily blocked.

Management interface certificate (port 8090)

1. Open the HTTP monitor you created in Step 1 for port 8090.
2. Enable Monitor SSL certificate under the SSL section.
3. Set Alert when certificate expires in less than 21 days.
4. Click Save.

Hosted site certificates

For each website you host through CyberPanel, add a separate SSL monitor:

1. Click Add Monitor → HTTP / HTTPS.
2. Enter the site's URL: https://customersite.com.
3. Enable Monitor SSL certificate and set the alert threshold to 21 days.
4. Click Save.

CyberPanel's renewal cron runs daily at the system level. A 21-day alert window gives you three full weeks to investigate a renewal failure and manually trigger renewal from the CyberPanel dashboard (SSL → Manage SSL → Issue SSL) before visitors start seeing certificate errors.

Step 5: Heartbeat Monitoring for CyberPanel Scheduled Tasks

CyberPanel runs several critical background tasks through its built-in scheduler: automated backups, Let's Encrypt certificate renewal, and malware scans via the CyberPanel security module. These tasks have no HTTP endpoint to probe — use Vigilmon's cron heartbeat to confirm they complete successfully on schedule.

Create a heartbeat monitor

1. In Vigilmon, click Add Monitor → Cron Heartbeat.
2. Set the Expected ping interval to match your task frequency (e.g., 1440 minutes for a daily backup job).
3. Copy the heartbeat URL: https://vigilmon.online/heartbeat/your-token.
4. Click Save.

Wire the heartbeat to CyberPanel's scheduled tasks

CyberPanel schedules jobs using the system cron. Add the Vigilmon ping at the end of the relevant cron entry:

# Edit the system crontab
crontab -e

For the daily backup task (adjust the time to match your existing CyberPanel backup schedule):

0 2 * * * /usr/local/CyberCP/bin/python /usr/local/CyberCP/plogical/backupManager.py && curl -s https://vigilmon.online/heartbeat/your-token

For Let's Encrypt renewal (CyberPanel's default renewal check runs daily):

0 3 * * * /usr/local/CyberCP/bin/python /usr/local/CyberCP/plogical/sslManager.py autoRenewSSL && curl -s https://vigilmon.online/heartbeat/your-ssl-token

If the backup or renewal script exits with an error, the && operator prevents the curl ping from running — Vigilmon detects the missing heartbeat and sends an alert.

Step 6: Configure Alert Channels

1. Go to Alert Channels in Vigilmon and add your preferred notification method: email, Slack, or a webhook to PagerDuty or similar.
2. Set Consecutive failures before alert to 2 for the web UI and API monitors — a single failed probe during a CyberPanel cache flush or restart is normal.
3. For the TCP port monitor (OpenLiteSpeed), you may prefer an immediate alert (1 failure) since a port-down condition means all hosted sites are offline.

Summary

| Monitor | Target | What It Catches | |---|---|---| | HTTP (CyberPanel UI) | https://server:8090 | Panel service crash, firewall change | | HTTP (REST API) | https://server:8090/api/cyberPanel | API layer failure, backend error | | TCP port | :7080 (OpenLiteSpeed admin) | OpenLiteSpeed process down | | SSL certificate | Panel + each hosted site | Let's Encrypt renewal failure | | Cron heartbeat | Backup/renewal/scan tasks | Scheduled task failure or skipped run |

CyberPanel's performance advantages over older panels come with the responsibility of self-managed uptime. With Vigilmon watching the panel UI, REST API, OpenLiteSpeed service, SSL certificates, and scheduled tasks, you get the observability layer that turns a powerful self-hosted stack into a reliably monitored one.