Requirements & Installation
PUQ Web Hosting module WHMCS
Order now | Download | Community
Requirements
- A working WHMCS installation (see the PHP/WHMCS compatibility table below).
- ionCube Loader enabled on the WHMCS host, matching the PHP version it runs.
- One or more HestiaCP servers reachable over SSH from the WHMCS host. The module drives Hestia entirely over SSH (the panel HTTP API is not required); set up
sudoNOPASSWD for the management user, or use the Hestiaadminuser with key/password auth. - (Optional) PowerDNS servers if you want PowerDNS as a DNS backend alongside HestiaCP.
- Outbound HTTPS from the Hestia nodes for Let's Encrypt and for the optional file‑manager / PHP installers.
PHP & WHMCS compatibility
The module is distributed as ionCube‑encoded builds, one per PHP version: 7.4, 8.1 and 8.2. Always install the build that matches the PHP version your WHMCS host runs under — not the PHP versions you offer to hosting customers (those are independent and managed on each Hestia web server).
| WHMCS version | PHP it runs on | Module build to install |
|---|---|---|
| WHMCS 8.x | 7.4, 8.1 or 8.2 | the 7.4 / 8.1 / 8.2 build matching your PHP |
| WHMCS 9.x | 8.2 | the 8.2 build |
| any host on PHP 8.3 / 8.4 or newer | 8.3+ | the 8.2 build |
How to choose, in plain terms:
- Check the PHP version your WHMCS server runs (WHMCS → Utilities → System → PHP Info, or
php -von the host). - On WHMCS 8 you may run PHP 7.4, 8.1 or 8.2 — download the build with the same number.
- On WHMCS 9 the host runs PHP 8.2 — use the 8.2 build.
- If your host runs a PHP version newer than 8.2 (8.3, 8.4, …), use the 8.2 build — it is the latest supported and is compatible with newer PHP runtimes.
Downloads for every supported PHP version are on the Download page. After any module update, re‑run the schema check (below).
Install both modules
The product is two WHMCS modules — install both:
| Upload to | Module |
|---|---|
modules/servers/puqWebHosting/ |
the server module |
modules/addons/puq_web_hosting/ |
the addon module |
Then in WHMCS go to Setup → Addon Modules, find PUQ Web Hosting, and Activate it (grant access to the admin roles that should manage hosting). Activating the addon creates the database tables the server module needs.
First run: check the schema & find the panels
After activation you have a new PUQ Web Hosting admin page (via Addons). Its top navigation gives you everything: Home, Services, Statistics, Infrastructure, Logs, Settings, Help.
Open Settings → Maintenance and click Run schema check once. It scans every module table and brings it in sync with the current code — creating missing tables, adding missing columns and dropping columns that no longer exist. You should run this after every module update.
The same tab has a “delete all tables on deactivate” toggle — leave it off unless you are fully uninstalling, so your data survives an accidental deactivation.
What's next
With both modules installed you build your service from the bottom up:
- Add your servers and tag their capabilities — see Add web / mail / DNS servers.
- Group them and apply role‑targeted configuration — see Server groups.
- Create a product pointed at a group — see Create a product.
The module Settings (timeouts, retry policy, SSL cadence, DNS/SOA defaults, integrations, notifications) are covered in Addon Module → Settings; the defaults are sensible, so you can come back to them later.