WHMCS server setup builds the Linux machine your WHMCS installation lives on: operating system, web server, PHP, database, cron, SSL and backups, configured to the requirements WHMCS publishes before the software goes on. It suits hosting brands moving billing off a shared cPanel account or a busy hosting node, and new operators who want WHMCS on its own VPS from the start. One server starts at $199.
This page is about the billing server only. The cPanel/WHM machines you sell hosting from are covered by cPanel installation and WHMCS integration, and locking those down is WHM setup and hardening.
Why WHMCS deserves its own server
WHMCS holds an API token or password for every server it provisions on, your gateway keys and every customer's billing record. On a shared hosting node, one compromised customer site sits next to all of that. A small VPS used only for billing also makes PHP changes safe, because moving WHMCS to a newer PHP version cannot break a customer's old WordPress plugin.
The stack, matched to your WHMCS version
| Component | What we set up |
|---|---|
| PHP | 8.1 or later for WHMCS 8.13; 8.2 or later for 9.x (the 9.1 requirements list PHP 8.2, 8.3 and 8.4) |
| ionCube Loader | The build that matches your PHP and WHMCS release; 9.1 needs 15.0.0 or later |
| Database | MySQL 8, which WHMCS recommends; MariaDB only on request, since WHMCS describes it as binary-compatible rather than officially supported |
| Web server | Apache 2.4 with mod_rewrite and PHP-FPM, or Nginx |
| Operating system | Ubuntu LTS, Debian or AlmaLinux |
WHMCS lists December 31, 2026 as the end of life for 8.13. We install PHP so that both 8.13 and 9.x can run on the same machine, which means the later upgrade to WHMCS 9 does not require a rebuild.
Apache or Nginx
WHMCS validates Apache 2.x with mod_rewrite and calls Nginx support limited. Nginx ignores the .htaccess files WHMCS ships, so on an Nginx build we write the equivalents by hand: the deny rule for /vendor/ that WHMCS documents, plus rules that stop configuration.php, the admin directory and any leftover install folder from being served directly. With no strong preference either way, we pick Apache with the event MPM and PHP-FPM, the setup WHMCS support expects to see when you open a ticket.
What the build includes
- SSH key login, root password login disabled and unattended security updates
- A firewall that opens only HTTPS, SSH from your addresses, and the outbound ports WHMCS needs, such as 2087 to your WHM servers
- A PHP-FPM pool under its own system user, with OPcache on and memory_limit at or above the 128 MB WHMCS recommends
- The required PHP extensions (cURL with SSL, GD, IMAP, PDO_MySQL built on mysqlnd, XML) and the recommended ones (BC Math, Intl, mbstring, GMP, SOAP)
- A dedicated database and user, the InnoDB buffer pool sized to the server's RAM, and STRICT_TRANS_TABLES and ERROR_FOR_DIVISION_BY_ZERO removed from sql_mode, as WHMCS requires
- A Let's Encrypt certificate with automatic renewal for a hostname such as billing.yourbrand.com, or origin rules if you sit behind Cloudflare
- Private folders above the web root ready for attachments, downloads, templates_c and the crons directory
- The system cron calling the same PHP binary the web server uses, so WHMCS does not report a cron PHP mismatch
- An SMTP relay such as Amazon SES, Postmark or Mailgun, with SPF and DKIM published for your sending domain
- Nightly database and file backups sent off the server, with one test restore before handover
If your cron has already gone quiet on an old server, our cron troubleshooting guide explains what to check while the new one is built.
What we need from you
- Root access to a VPS or dedicated server, or access to a Hetzner, Vultr, DigitalOcean or OVHcloud account where we can create one
- The billing hostname and access to its DNS
- The WHMCS version you run or plan to run
- Fixed IP addresses for your staff, if you want SSH and the admin area restricted to them
For a new install, two vCPUs and 4 GB of RAM is a sensible starting size. Larger client bases or heavy module use need more, and we size it from your numbers on the call.
Pricing
| Scope | Price |
|---|---|
| One new server with the stack above, ready for a WHMCS install | From $199, one-time |
| Moving an existing WHMCS onto it: files, database, crons and DNS cutover | Fixed quote after the scoping call |
| Extra environments such as staging, or later changes | $65 per hour, or a fixed quote |
The written quote, sent within one business day of the free call, gives the delivery date.
Not included
- Your WHMCS license, server rental and SMTP provider fees
- Installing and configuring WHMCS itself, which is our WHMCS installation service and is often booked alongside
- Tuning a server that already runs WHMCS slowly; that is WHMCS performance tuning
- Servers that host customer websites
Not sure whether to move billing out of the cPanel account it lives in today? Bring the server details to the scoping call and we will tell you what the move changes and what it costs.