OVH Public Cloud For WHMCS
Article update is ongoing on this page, watch out for broken links, unclear descriptions and images!
We are sorry for the inconvenience caused.
|OVH Public Cloud For WHMCS is a module which allows you to automatically provision virtual servers to your customers.|
The great advantage of this module is the fact that customers can order and manage virtual servers, backups and many more in their own WHMCS client area.
- Admin Area Features:
|✔ Create/Suspend/Unsuspend/Terminate Server|
|✔ Change Package - Supports Configurable Options|
|✔ View Server Status And Details|
|✔ View Interface Details|
|✔ View List Of Scheduled Tasks|
|✔ View Volumes Information|
|✔ Configure Client Area Features Per Product|
|✔ Define Backup Quantity Limit|
|✔ Set Security Groups|
|✔ Enable Backups Routing|
|✔ Run Extended Connection Test|
- Client Area Features:
|✔ View Server Status And Details|
|✔ Start/Stop/Pause/Unpause/Resume/Rebuild Server|
|✔ Reboot Server - Soft/Hard|
|✔ Access noVNC Console|
|✔ Create/Restore/Delete Backups - Supported By VPS Not Using Cinder Volumes|
|✔ Download Public & Private SSH Keys|
|✔ View List Of Scheduled Tasks|
|✔ View Volumes Information|
- General Info:
|✔ Automated Generation Of SSH Keys - Public SSH Key Is Injected To VM Automatically|
|✔ Integrated With Server Allocator For WHMCS - Automatic Assignment Of Most Suitable Servers To Products (read more)|
|✔ Multi-Language Support|
|✔ Supports PHP 5.6 Up To PHP 7.3|
|✔ Supports WHMCS Template Six|
|✔ Supports WHMCS V7.6 And Later|
|✔ Easy Module Upgrade To Open Source Version|
- Available Configurable Options:
|✔ VM Image|
|✔ IP Addresses|
|✔ Backups Files Limit|
Installation and Configuration
|This tutorial will show you how to successfully install and configure OVH Public Cloud For WHMCS. |
We will guide you step by step through the whole installation and configuration process.
|1. Log in to our client area and download the module.|
|2. In the downloaded file you will find two packages that support different PHP versions.|
As presented on the screen below, the first one is dedicated to PHP 5.6 up to PHP 7.0, while the second one is aimed at PHP 7.1 up to PHP 7.3.
It does not apply to open source versions.
Note: You can check the current PHP version in your WHMCS. To do so, proceed to 'Utilities' → 'System' → 'PHP Info'.
|3. Extract the downloaded file and choose the one with the right PHP version. Upload and extract the PHP file into the main WHMCS directory.|
The content of PHP version files should look like this.
|4. When you install OVH Public Cloud For WHMCS for the first time you have to rename 'license_RENAME.php' file.|
File is located in 'modules/servers/OVHPublicCloud/license_RENAME.php'. Rename it from 'license_RENAME.php' to 'license.php'.
|5. In order to configure your license key, you have to edit a previously renamed 'license.php' file.|
Enter your license key between quotation marks as presented on the following screen.
|6. Next step is setting up a cron job (each 5 minutes suggested).|
Use the cron job below but switch 'your_whmcs' with your root WHMCS path.
php -q /your_whmcs/modules/servers/OVHPublicCloud/cron/cron.php
Configuration of Server
|7. Now, we will show you how to configure a new product.|
Go to the 'Setup' → 'Products/Services' → 'Servers' and press 'Add New Server'. '
Note: If you have WHMCS V7.8.X or later, we recommend using your 'previous experience' of the server configuration instead of the new wizard tool.
|8. Next, enter your server name and connection details. |
Finally, press 'Save Changes' .
|9. While you configure your server details, you need to check if the connection with the OVH Public Cloud server is set up correctly.|
Simply press 'Test Connection' as shown on the screen below.
Additionally, you have to set up each endpoint address to the corresponding region you want to use to make sure that all services will be connected successfully.
Note: Any chosen endpoint address will be automatically saved after its selection so there is no need to save it manually after each change.
|10. It is time to create a server group. To do so, click on 'Create Server Group' .|
|11. Enter a name, click on your previously created server, press 'Add' and afterward 'Save Changes' .|
Configuration of Product
|12. In order to create and configure a product, go to the 'Setup' → 'Products/Services' → 'Products/Services'.|
Click on 'Create a New Group' .
|13. Enter product group name and press 'Save Changes'.|
|14. When you have a product group, you can create your product.|
To create a product click on 'Create a New Product'.
|15. Afterward, choose your product group and type from the dropdown menus, enter your product name and press 'Continue'. |
'Product Type' should be set to 'Hosting Account'.
|16. Now, go to the 'Module Settings' section, choose both 'OVHPublicCloud' and your previously created server group from the dropdown menus.|
Next, press 'Save Changes'.
|17. First of all, select 'Default Tenant'. |
'Check access' should return 'OK' if the permissions are set up correctly.
|18. Afterward, configure network settings. Choose 'Fixed Network', 'Floating Network' and 'Default Number Of IP Addresses'. |
You can set up a network in two ways. Find more information about the configuration here.
|19. At this step, you can configure backups.|
Mark the 'Backups Routing' checkbox if you want to replace the oldest backup with the newest one when the backups file limit is reached.
|20. Mark security group from 'Use Security Groups'. |
If you wish to use SSH keys, leave 'Inject SSH Key' marked (virtualization must support 'Inject File' feature).
|21. Finish through selecting features that will be available in the client area.|
Mark the checkbox next to a feature in order to enable it.
|22. Select 'Default Flavor' and 'Default VM Image'. |
'Default Flavor' defined resources assigned to a VM while 'Default VM Image' allows you to choose the VM image used to create a new VM.
|23. Choose 'Default Region' . |
'Default Region' will be set if no respective configurable option is defined.
Press 'Save Changes' when ready.
|24. Do not forget to generate default configurable options. Only then your clients will be allowed to adjust the virtual machine when placing an order.|
|Congratulations! You have just finished the installation and configuration of the product!|
| OVH Public Cloud For WHMCS allows your customers to manage their virtual machines via client area in your WHMCS system.|
You can monitor and manage each product from your WHMCS admin area.
|Owing to configurable options, you are able to offer a product which your clients can tailor according to their needs.|
Additionally, you are able to set up pricing for each configurable option, which make your offer even more competitive.
|Client area interface of OVH Public Cloud VPS should look like the one on the screen below.|
As you can see, the control panel contains useful options needed for managing VMs.
Module allows your customers to easily start/stop, pause/unpause, soft reboot, hard reboot and reset the network of their virtual servers.
|The rebuild feature allows your clients to change the server image.|
Click on the 'Rebuild' button as shown on the following screen to continue.
|To reinstall your server, choose an image and press the 'Rebuild' button.|
|One of the most interesting functionalities is access to a noVNC console where your clients can remotely manage their servers.|
To access it, simply click on 'Console' .
|noVNC consoloe is a browser based VNC client. It was implemented using HTML5 Canvas and WebSockets.|
|Your customers can also create a backup of VPS. To do so, press the 'Backups' button.|
Note: Backups are available only if the 'Use Volumes' option in 'Module Settings' is disabled.
|Now, type in the backup name and click on 'Backup Now' .|
|To restore VPS from backup, simply press the 'Restore' button next to it.|
|Due to a limitation in WHMCS product creation process, OVH Public Cloud For WHMCS generates a SSH key pair automatically.|
The public SSH key is automatically implemented into a VM while the private key can be downloaded from the client area.
|Public SSH key on the other hand, can be downloaded as many times as your client will need it.|
Press 'Download Public Key' as shown on the following screen to save it on your disk.
Network Configuration Cases
|OVH Public Cloud For WHMCS allows you to set up two types of network.|
The first one is the network without a floating IP address.
|The second type of network is the network with a floating IP address.|
Select 'Shared Network' as 'Fixed Network' and 'Public' as 'Floating Network' in 'Module Settings'.
|In case standard configuration does not suit your needs, you can adjust it through configurable options.|
To do so, go to 'Setup' → 'Products/Services' → 'Configurable Option' and press the edit button next to a configurable option used by your product.
|Here you can view the products, a given configurable option group is assigned to.|
Now we will show you how to edit options. Let's say that you want to add an option to order VPS with 5 IP addresses allowed..
|You should see a popup window, make sure that your browser does not block it.|
To add a new option, enter it in the text box under all other options. If you want to replace it with an option you currently have, simply edit its text box.
|1. Due to the fact that some requests may take time to be completed, we implemented 'Scheduled Tasks'. |
Tasks visible at 'Scheduled Tasks' are subsequently performed by regular cron jobs.
|Essential guidance through the process of updating the module is offered here.|
Keep in mind there is a quick and easy option in our client area that will let you upgrade the license of your module to an open source version at any time - and at a lower price!
|1. When you have problems with connection, check whether your SELinux or firewall does not block ports.|
|2. In case of persisting connection problems, please make sure you have the following ports open:
35357, 8774, 9292, 5000, 8777, 8776, 9696
|3. OVH Public Cloud For WHMCS module does not support dedicated servers.|
|4. The module's primary functionality refers to the OVH devices which benefit directly from the OpenStack structure, however they cannot be used interchangeably with OpenStack itself.|