Dedicated Server IPMI Power Control for WHMCS
Customers power on, shut down, reset and check their dedicated server from WHMCS, through its IPMI or Redfish controller, with every action logged.
What will the IPMI power control module do?
It gives each dedicated server you sell through WHMCS a set of power controls: Power On, Power Off, Reset and the current power state. The module sends each action to that server's baseboard management controller (BMC), the management chip on the motherboard, using IPMI over LAN or, on BMCs that offer it, the Redfish REST API. Customers use the buttons in their client area and your staff use the same controls on the service page in the admin area, so a frozen server no longer means a ticket and a wait for someone with BMC access.
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 bills and tracks dedicated servers, and its server modules for virtualization panels such as SolusVM give customers boot and reboot buttons for virtual servers. It has no built-in way to reach a physical server's BMC, so power control for bare metal stays outside WHMCS. This module adds that link: a BMC address and login stored on each service, the power commands, and the checks around them.
What is included?
| Part | What you get |
|---|---|
| Power actions | Power on, power off (graceful shutdown or forced off, where the BMC supports both) and reset |
| Status | Current power state read from the BMC when the service page opens |
| Protocols | IPMI 2.0 over LAN, and Redfish where the BMC offers it, chosen per service |
| Credentials | BMC address, username and password stored encrypted on each service |
| Client area | Buttons with a confirmation step before any action runs |
| Safety | Action log (who, what, when, from which IP, result) and a rate limit per service |
| Network | Direct from the WHMCS server, or through a small relay script you run inside the BMC network |
Who is it for?
Hosts and data center operators who rent out bare-metal servers and bill them in WHMCS. A customer whose server hangs after a kernel update can reset it on their own in the middle of the night instead of opening a ticket, and your team stops handing out BMC web logins just so a customer can press a power button.
How should the BMCs be reached?
Keep them off the public internet. A BMC gives full control of the hardware, and IPMI over LAN in particular belongs on a private management network or behind a VPN. The module talks to each BMC from the WHMCS server when that server sits on the management network. When it does not, I include a small relay script that you run on a host inside that network, and WHMCS sends it signed requests over HTTPS. I suggest a dedicated BMC user with operator rights for the module, not the administrator account. Redfish connections check the BMC's TLS certificate, and a self-signed certificate can be trusted by its fingerprint for that one server.
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, BMCs that support IPMI 2.0 over LAN or Redfish, and a command-line IPMI tool on the WHMCS server or relay host for IPMI connections.
Limits: the module covers power and status only. It does not open a remote console, mount ISO images, reinstall operating systems or manage BMC users and firmware. The buttons stay hidden while a service is suspended or not active. When a BMC is busy or unreachable, the customer sees an error instead of a guessed power state.
It costs $149 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
- Power on, power off and reset from the WHMCS client area
- Current power state read from each server's BMC
- IPMI 2.0 over LAN, plus Redfish where the BMC offers it
- Graceful shutdown or forced power off, where the BMC supports both
- BMC address and login stored encrypted on each service
- Confirmation step before every client action
- Action log with user, time, IP address and result
- Rate limit on power actions per service
- Same controls for staff on the admin service page
- Relay script for BMCs on a private network
Why customers buy this module
- →Customers recover a hung server without opening a ticket
- →No more sharing BMC web logins with customers
- →A record of every power action when a customer asks what happened
- →BMCs stay on your private network
Frequently asked questions
Can I use it with servers from different makers?
Yes. You choose IPMI over LAN or Redfish for each service, so a mix of server brands works as long as each BMC supports one of the two. Redfish is the newer standard and runs over HTTPS; IPMI over LAN also works on older boards. If you are unsure about a model, send it to me before you order.
Do customers get access to the BMC itself?
No. They press a button in WHMCS, and the module checks that the service is theirs and active, applies the rate limit and logs the request before it sends one power command from your WHMCS server or relay. The BMC login is never shown to the customer. Keep the BMCs on a private network or VPN either way.
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+
- Protocols
- IPMI 2.0 over LAN, Redfish
- Power actions
- On, off, reset, status
- 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
Self-Service cPanel Transfer Wizard for WHMCS
I built this wizard so customers can move their own sites from another cPanel host to yours without a ticket. It uses WHM API tokens, never root passwords, and checks the site, mail and DNS after the move.
Hetzner Cloud Provisioning and Auto-Sync for WHMCS
I built this Hetzner Cloud module so your WHMCS catalog never falls behind Hetzner. Server types, locations and prices sync hourly with your markup, and customers manage power, console, snapshots, networks, firewalls and volumes.
Vultr Cloud Server Provisioning for WHMCS
I built this module to resell Vultr through WHMCS. A paid order deploys the instance in the plan, region and OS the customer chose, and they get power controls, console, snapshots and rDNS without seeing Vultr.