Uptime Monitor and Status Page for WHMCS
Checks your servers and services by HTTP, ping and port from WHMCS, opens and resolves Network Issues on its own, and runs a public status page.
What will the uptime monitor do?
It checks the servers and services you sell from your WHMCS server, on a schedule you set for each check: an HTTP or HTTPS request that expects a status code and, if you want, a word on the page; a ping; or a TCP connection to a port such as SSH, SMTP or a control panel. When a check fails a set number of times in a row, the module opens an incident in WHMCS Network Issues, emails your staff and shows a banner to the clients affected. When the check passes again, it marks the issue Resolved and sends a recovery email.
This product is built to order: you get the license key at purchase and the download within 15 business days.
What does WHMCS already do, and what does this add?
WHMCS has two related features. Network Issues lets you post outages and maintenance to the client area by hand, with a type, priority and status, and you can show that page to visitors who are not logged in by turning off Service Status Require Login. Server status monitoring shows load and uptime for Linux servers that have the WHMCS status folder uploaded, and the client area status page tests the HTTP, FTP and POP3 ports when someone opens it. Nothing in WHMCS runs checks on a schedule, alerts staff, or opens and closes a Network Issue by itself. This module adds scheduled checks, failure thresholds, staff alerts, automatic incidents and a status page built from the check results.
What is included?
| Part | What you get |
|---|---|
| Check types | HTTP or HTTPS (status code and optional keyword), ping, TCP port |
| Targets | A WHMCS server, or a single client service |
| Schedule | Interval per check, from one minute up |
| Threshold | Number of failures in a row before an incident opens |
| Incidents | WHMCS Network Issue opened on failure and resolved on recovery |
| Status page | Public page with current status, open incidents and 30-day uptime per check |
| Client banner | Notice on the client area home page for clients with services on an affected server |
| Alerts | Email to the staff you choose, on failure and on recovery |
Who is it for?
Hosting companies that bill in WHMCS and want customers to hear about an outage from them before they open a ticket. When a node goes down, the Network Issue and the banner are already up, staff have the alert, and the status page shows the same picture to visitors who cannot log in. When it recovers, the issue closes without anyone having to remember it.
What do you need, and what are the limits?
Requirements: WHMCS 8.13 or 9.x (I confirm your exact version at purchase), PHP 8.1 or newer, and a cron entry that runs every minute on the WHMCS server. Nothing is installed on the servers you watch. Ping checks need the system ping command available to PHP; where your host blocks it, use a port check instead.
Limits: every check runs from one place, your WHMCS server. If that server loses its own connection, checks can fail while your servers are fine, and if WHMCS itself is down, nothing is checked and the status page is down too, so host WHMCS away from the servers it watches. A failing check on one client's service alerts your staff and shows a banner to that client only, because Network Issues are meant for problems that affect many clients. The module sends email alerts only, and it does not replace a monitoring system that checks from several regions.
It costs $129 once for a lifetime license with twelve months of updates and support, the license key at purchase and the download within 15 business days, and a seven-day refund window.
Key features
- HTTP and HTTPS checks with status code and optional keyword
- Ping and TCP port checks
- Interval set per check, from one minute up
- Failure threshold before an incident opens
- WHMCS Network Issue opened on failure and resolved on recovery
- Public status page with 30-day uptime per check
- Client area banner for clients on an affected server
- Email alerts to chosen staff on failure and recovery
- Check history in the admin area
Why customers buy this module
- →Customers hear about an outage from you before they open a ticket
- →Network Issues open and close without staff doing it by hand
- →Staff learn about a failure from an alert, not from customers
- →Visitors who cannot log in still see what is down
Frequently asked questions
How is this different from the server status page WHMCS already has?
The built-in page shows load and uptime from the WHMCS status folder and tests a few ports when someone opens it. It does not check anything on a schedule, warn your staff, or post to Network Issues. This module checks around the clock at the interval you set, opens and resolves Network Issues itself, emails staff and keeps 30 days of uptime history for the status page.
Will a short network blip open an incident?
Only if it lasts. You set how many failures in a row open an incident for each check, so with a one-minute interval and a threshold of three, a server has to fail three checks in a row before anything is posted. A single missed check is kept in the history but changes nothing for clients.
When will I get it, and what if you can't deliver?
It is built to order. You get the license key at purchase and the download within 15 business days of purchase. If I do not deliver it in that time, you get a full refund. Once it is delivered, the store's 7-day refund window applies.
Technical specifications
- WHMCS
- 8.13 and 9.x (confirmed at purchase)
- PHP
- 8.1+
- Check types
- HTTP/HTTPS, ping, TCP port
- Cron
- Every minute on the WHMCS server
- Availability
- Built to order, delivered in 15 business days
- License
- Lifetime, 1 year of updates and support included
- Delivery
- Instant download and license key
- Refund window
- 7 days
Related modules
Discord Bot and Role Sync for WHMCS
I built this Discord bot to link your community server to WHMCS. Roles follow active products, paid-only channels open on payment and close on cancellation, and customers use slash commands for invoices, services and support.
SMS, Chat and Email Notification Hub for WHMCS
One WHMCS module I built to send notifications across eight channels from a single rules screen. You decide which events go where, customers set their own preferences, and failed messages fall back to email.
Telegram Support and Billing Bot for WHMCS
A Telegram bot I built that runs inside WHMCS as plain PHP. Customers use commands to see invoices, services and tickets, renew and pay; admins get push alerts and can search, assign and reply from Telegram.