OVH VPS

Provisioning module

The OVH VPS module lets you resell OVH’s classic virtual servers, running Linux or Windows, from WHMCS. The customer chooses a location and an operating system in the usual WHMCS ordering process, and the module orders, delivers, renews and terminates the server through the OVH API. Customers don’t need an OVH account of their own; they get the service under the reseller’s account.

The module plugs in as a standard WHMCS provisioning module: the OVH plan chosen for the product, the configurable options and the WHMCS billing cycle determine what it orders from OVH. It is for server and hosting providers who want to offer OVH VPSs with their own billing and their own client area. It doesn’t handle OVH Public Cloud instances.

How it works

Connection to the OVH account. The module works with OVH API keys added as a server in WHMCS. The connection test also checks whether the account has a default payment method, because OVH charges every order and renewal to it. For each product, you can set a monthly price cap: if OVH’s price is higher, the order or renewal stops.

Ordering with real-time stock. On the order form, out-of-stock locations can’t be selected, and checkout also checks stock, for the chosen operating system family, because stock for Linux and Windows can differ. If stock runs out after payment, the service stays in the Module Queue, and the administrator is notified.

Provisioning after the invoice is paid. The module places the order with OVH, and the WHMCS cron checks the delivery on every run. When OVH is done, the module fills in the IP addresses and sends the welcome email; until then, the customer sees an “installation in progress” message. For Linux, OVH only sends the password by email, and the module reads it from the OVH account’s email history. For Windows, the customer sets the administrator password in the console at first boot.

Renewal. OVH’s automatic renewal is turned off, so OVH only charges once the customer has paid the invoice. The WHMCS billing cycle selects the OVH term: for six-monthly, annual and two-year cycles, the module orders with a prepaid commitment period if the plan offers one. The daily cron job extends the paid-up services that are close to expiry, and sends a summary of the items that need attention. It is a good idea to align the WHMCS invoicing and suspension timing with the OVH expiry date.

Suspension and termination. On suspension, the VPS is stopped, and all customer actions are blocked. On termination, OVH deletes the machine at the end of the paid period; until then, the termination can be reversed.

Admin tools. On the service’s admin page, an existing VPS can be linked without ordering, the IP addresses and the expiry date can be refreshed, a failed delivery can be rechecked, and the welcome email can be resent. With logging enabled, every API call goes into the Module Log, with passwords and email contents masked.

Main features

  • Ordering: location and operating system as configurable options, with real-time OVH stock on the order form and at checkout.
  • Lifecycle: provisioning, suspension and unsuspension, termination, renewal when the invoice is paid.
  • Client area: power on and off, reboot, rescue mode, reinstallation, console, status and details, IP addresses with reverse DNS, disks with storage and bandwidth limits, CPU and traffic graphs.
  • Firewall: a separate page for managing the OVH network firewall.
  • Automated backup: if OVH’s daily backup is enabled, the customer can copy files from a restore point, or restore the whole VPS to it.
  • Custom welcome, reinstallation and rescue email templates per product.

What it doesn’t include

Plan changes, snapshots, extra disks, additional IP addresses, changing the backup time, switching between Linux and Windows, and automatic creation of the configurable options.