Proxmox VE Cloud VPS For WHMCS
(→About Proxmox Cloud VPS For WHMCS) |
(→Backup Jobs) |
||
(168 intermediate revisions by 6 users not shown) | |||
Line 1: | Line 1: | ||
− | <meta name="keywords" content="proxmox cloud vps for whmcs, proxmox cloud vps configuration, whmcs proxmox cloud vps management, whmcs proxmox cloud vps installation, whmcs proxmox cloud vps common problems, about whmcs proxmox cloud, whmcs proxmox cloud vps documentation, whmcs proxmox cloud vps faq, whmcs proxmox cloud vps help, whmcs proxmox cloud vps guide, whmcs proxmox cloud vps wiki, whmcs proxmox cloud vps tutorial, whmcs proxmox cloud vps tips, whmcs proxmox cloud vps wiki"></meta> | + | <meta name="keywords" content="proxmox ve cloud vps for whmcs, proxmox ve cloud vps configuration, whmcs proxmox ve cloud vps management, whmcs proxmox ve cloud vps installation, whmcs proxmox ve cloud vps common problems, about whmcs proxmox ve cloud, whmcs proxmox ve cloud vps documentation, whmcs proxmox ve cloud vps faq, whmcs proxmox ve cloud vps help, whmcs proxmox ve cloud vps guide, whmcs proxmox ve cloud vps wiki, whmcs proxmox ve cloud vps tutorial, whmcs proxmox ve cloud vps tips, whmcs proxmox ve cloud vps wiki, proxmox cloud vps whmcs module, proxmox virtual environment whmcs"></meta> |
− | <meta name="description" content="ModulesGarden Wiki Contains All The Information You Need About The Proxmox Cloud VPS For WHMCS Module."></meta> | + | <meta name="description" content="ModulesGarden Wiki Contains All The Information You Need About The Proxmox VE Cloud VPS For WHMCS Module."></meta> |
− | + | =About [https://www.modulesgarden.com/products/whmcs/proxmox-ve-cloud-vps Proxmox VE Cloud VPS For WHMCS]= | |
− | + | ||
− | + | ||
− | =About [https://www.modulesgarden.com/products/whmcs/proxmox-cloud-vps Proxmox Cloud VPS For WHMCS]= | + | |
{| | {| | ||
− | |style="padding: 10px 0px 10px 0px;"|'''Proxmox Cloud VPS For WHMCS''' offers your clients the flexibility to create, remove and freely resize their own virtual servers within resource limits defined by you. | + | |style="padding: 10px 0px 10px 0px;"|'''Proxmox VE Cloud VPS For WHMCS''' offers your clients the flexibility to create, remove and freely resize their own virtual servers within resource limits defined by you. |
Your customers will be able to create as many servers as they need, manage such essential aspects like backups or firewall, and access noVNC, SPICE, or Xterm.js console.<br /> | Your customers will be able to create as many servers as they need, manage such essential aspects like backups or firewall, and access noVNC, SPICE, or Xterm.js console.<br /> | ||
− | The module supports Cloud-Init for the KVM virtualization type, and features Proxmox Addon allowing you to easily manage servers, IP addresses and clusters. | + | The module supports Cloud-Init for the KVM virtualization type, and features Proxmox Addon allowing you to easily manage servers, IP addresses and clusters.<br/><br> |
+ | ModulesGarden is official [https://www.proxmox.com/en/partners/all/partner/modulesgarden '''Proxmox Solution Partner'''] and this module is recommended by '''Proxmox Server Solutions GmbH.''' | ||
|} | |} | ||
<!--comments are awesome --> | <!--comments are awesome --> | ||
Line 59: | Line 57: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 45px;"|✔ Network | + | |style="padding: 0px 0px 0px 45px;"|✔ Network And Private Network Settings With SDN Support |
|} | |} | ||
{| | {| | ||
Line 183: | Line 181: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 45px;"|✔ Statuses, Resources Usage, IP Assignments | + | |style="padding: 0px 0px 0px 45px;"|✔ Statuses, Resources Usage, IP Assignments And Details |
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 30px;"|✔ Manage | + | |style="padding: 0px 0px 0px 30px;"|✔ Manage Public And Private IP Addresses Per Server/VLAN/Tag/Node/Bridge: |
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 45px;"|✔ IPv4 Addresses | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 45px;"|✔ IPv6 Addresses | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 45px;"|✔ IPv6 Subnets | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 30px;"|✔ View Logs Of IP Assignment Changes | ||
|} | |} | ||
{| | {| | ||
Line 195: | Line 205: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 30px;"|✔ Define VM | + | |style="padding: 0px 0px 0px 30px;"|✔ Define VM ID Ranges Per Server |
|} | |} | ||
{| | {| | ||
Line 204: | Line 214: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 30px;"|✔ Configure | + | |style="padding: 0px 0px 0px 30px;"|✔ Configure Scheduled Backups, Firewall And Operating Systems Templates |
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 30px;"|✔ Configure Resource Weights For Load Balancer Prioritization | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 30px;"|✔ Configure Tasks Repetition Threshold And Email Notifications | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 30px;"|✔ Configure Console Proxy | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 30px;"|✔ Synchronize User Permissions | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 10px 30px;"|✔ Create And Manage Custom Cloud-Init Scripts | ||
+ | |} | ||
+ | *'''Proxmox VE Widget''' | ||
+ | {| | ||
+ | |style="padding: 10px 0px 0px 30px;"|✔ View Faulty VM Deployments | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 30px;"|✔ View Failed Tasks | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 30px;"|✔ | + | |style="padding: 0px 0px 0px 30px;"|✔ View Cluster Remaining Resources |
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 10px 30px;"|✔ | + | |style="padding: 0px 0px 10px 30px;"|✔ View Node Resources |
|} | |} | ||
*'''Client Area Features:''' | *'''Client Area Features:''' | ||
{| | {| | ||
− | |style="padding: 10px 0px 0px 30px;"|✔ Create/Edit/Delete Servers | + | |style="padding: 10px 0px 0px 30px;"|✔ Create/Edit/Delete VM Instances On Selected Servers |
|} | |} | ||
{| | {| | ||
Line 224: | Line 256: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 30px;"|✔ Set Up Virtual Machines | + | |style="padding: 0px 0px 0px 30px;"|✔ Set Up Virtual Machines: |
|} | |} | ||
{| | {| | ||
Line 287: | Line 319: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 30px;"|✔ | + | |style="padding: 0px 0px 0px 30px;"|✔ Start/Reboot/Stop/Shut Down/Delete Server |
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 30px;"|✔ Reconfigure Server Network | ||
|} | |} | ||
{| | {| | ||
Line 302: | Line 337: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 30px;"|✔ Take, Manage And Restore Snapshots | + | |style="padding: 0px 0px 0px 30px;"|✔ Take, Manage, Schedule And Restore Snapshots |
|} | |} | ||
{| | {| | ||
|style="padding: 0px 0px 0px 30px;"|✔ Create, Manage And Restore Backups | |style="padding: 0px 0px 0px 30px;"|✔ Create, Manage And Restore Backups | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 30px;"|✔ Restore Backups From: | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 45px;"|✔ Any Owned Server | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 45px;"|✔ Proxmox Backup Server (PBS) | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 30px;"|✔ Restore Backups Of: | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 45px;"|✔ Selected Single Files And Directories With Option To Download Them (PBS) | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 45px;"|✔ Full Server Backups | ||
|} | |} | ||
{| | {| | ||
Line 342: | Line 395: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 45px;"|✔ CPU | + | |style="padding: 0px 0px 0px 45px;"|✔ CPU Limit |
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 45px;"|✔ CPU | + | |style="padding: 0px 0px 0px 45px;"|✔ CPU Units Limit |
|} | |} | ||
{| | {| | ||
Line 358: | Line 411: | ||
{| | {| | ||
|style="padding: 0px 0px 0px 45px;"|✔ IPv6 Addresses | |style="padding: 0px 0px 0px 45px;"|✔ IPv6 Addresses | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 45px;"|✔ IPv6 Subnets | ||
|} | |} | ||
{| | {| | ||
Line 379: | Line 435: | ||
{| | {| | ||
|style="padding: 0px 0px 0px 45px;"|✔ Virtual Networks | |style="padding: 0px 0px 0px 45px;"|✔ Virtual Networks | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 45px;"|✔ Snapshot Jobs | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 45px;"|✔ Storage Disk Space | ||
|} | |} | ||
{| | {| | ||
Line 384: | Line 446: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 45px;"|✔ CPU | + | |style="padding: 0px 0px 0px 45px;"|✔ CPU Limit |
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 45px;"|✔ CPU | + | |style="padding: 0px 0px 0px 45px;"|✔ CPU Units Limit |
|} | |} | ||
{| | {| | ||
Line 403: | Line 465: | ||
{| | {| | ||
|style="padding: 0px 0px 0px 45px;"|✔ IPv6 Addresses | |style="padding: 0px 0px 0px 45px;"|✔ IPv6 Addresses | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 45px;"|✔ IPv6 Subnets | ||
|} | |} | ||
{| | {| | ||
Line 408: | Line 473: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 45px;"|✔ Backups Files | + | |style="padding: 0px 0px 0px 45px;"|✔ Backups Files Limit |
|} | |} | ||
{| | {| | ||
Line 420: | Line 485: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px | + | |style="padding: 0px 0px 0px 45px;"|✔ Virtual Networks |
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 45px;"|✔ Snapshot Jobs | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 10px 45px;"|✔ Storage Disk Space | ||
|} | |} | ||
Line 431: | Line 502: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 30px;"|✔ Supports KVM | + | |style="padding: 0px 0px 0px 30px;"|✔ Supports KVM And LXC Virtualization |
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 30px;"|✔ | + | |style="padding: 0px 0px 0px 30px;"|✔ Supports Proxy For Proxmox Console Connections |
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 30px;"|✔ Integrated With < | + | |style="padding: 0px 0px 0px 30px;"|✔ Integrated With [https://www.modulesgarden.com/products/whmcs/advanced-billing Advanced Billing For WHMCS] - Actual Server Resource Usage Billing |
+ | |} | ||
+ | <!-- | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 30px;"|✔ Integrated With [https://www.modulesgarden.com/products/whmcs/proxmox-cloud-autoscaling Proxmox Cloud Autoscaling For WHMCS] - Automated Servers Resizing | ||
+ | |} | ||
+ | --> | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 30px;"|✔ Integrated With [https://www.modulesgarden.com/products/whmcs/proxmox-ve-vps Proxmox VE VPS For WHMCS] - Remote Provisioning And Management Of Virtual Servers | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 30px;"|✔ Integrated With | + | |style="padding: 0px 0px 0px 30px;"|✔ Integrated With [https://www.modulesgarden.com/products/whmcs/ip-manager IP Manager For WHMCS] - Complete Control And Easy Assignment Of IP Subnets (LXC) |
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 30px;"|✔ Integrated With | + | |style="padding: 0px 0px 0px 30px;"|✔ Fully Integrated With Lagom Client Theme |
|} | |} | ||
{| | {| | ||
Line 449: | Line 528: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 30px;"|✔ Supports Proxmox VE 6.X, 7.X And | + | |style="padding: 0px 0px 0px 30px;"|✔ Supports Proxmox VE 6.X, 7.X And 8.X |
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 30px;"|✔ Supports IPv4 | + | |style="padding: 0px 0px 0px 30px;"|✔ Supports IPv4 And IPv6 |
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 30px;"|✔ Supports PHP | + | |style="padding: 0px 0px 0px 30px;"|✔ Supports PHP 8.2 Back To PHP 7.4 |
|} | |} | ||
{| | {| | ||
Line 461: | Line 540: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 30px;"|✔ Supports WHMCS | + | |style="padding: 0px 0px 0px 30px;"|✔ Supports V8.11 Back To WHMCS V8.8 |
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 30px 30px;"|✔ Easy Module Upgrade To [https://www.modulesgarden.com/products/whmcs/proxmox-cloud-vps#open-source-version Open Source Version] | + | |style="padding: 0px 0px 0px 30px;"|✔ Requires ionCube Loader V13 Or Later |
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 30px 30px;"|✔ Easy [https://www.docs.modulesgarden.com/How_To_Upgrade_WHMCS_Module Module Upgrade] To [https://www.modulesgarden.com/products/whmcs/proxmox-ve-cloud-vps#open-source-version Open Source Version] | ||
|} | |} | ||
=Installation and Configuration= | =Installation and Configuration= | ||
{| | {| | ||
− | |style="padding: 10px 0px 30px 15px;"|'''This tutorial will show you how to successfully install and configure [https://www.modulesgarden.com/products/whmcs/proxmox-cloud-vps Proxmox Cloud VPS For WHMCS.]''' <br /> | + | |style="padding: 10px 0px 30px 15px;"|'''This tutorial will show you how to successfully install and configure [https://www.modulesgarden.com/products/whmcs/proxmox-ve-cloud-vps Proxmox VE Cloud VPS For WHMCS.]''' <br /> |
We will guide you step by step through the whole installation and configuration process.<br/> <br/> | We will guide you step by step through the whole installation and configuration process.<br/> <br/> | ||
'' '''Note:''' If you are still using any of the module's previous versions '''prior to v3.0''', [https://www.docs.modulesgarden.com/Proxmox_Cloud_2.X_For_WHMCS follow these instructions].'' | '' '''Note:''' If you are still using any of the module's previous versions '''prior to v3.0''', [https://www.docs.modulesgarden.com/Proxmox_Cloud_2.X_For_WHMCS follow these instructions].'' | ||
Line 480: | Line 562: | ||
|style="padding: 0px 0px 20px 25px;"|[[File:PXC3__1.png]] | |style="padding: 0px 0px 20px 25px;"|[[File:PXC3__1.png]] | ||
|} | |} | ||
+ | <!-- | ||
{| | {| | ||
|style="padding: 0px 0px 15px 15px;"|'''2. In the downloaded file you might find one or two packages that support different PHP versions.'''<br/> | |style="padding: 0px 0px 15px 15px;"|'''2. In the downloaded file you might find one or two packages that support different PHP versions.'''<br/> | ||
− | In the most recent versions of the module, you will find only one package that supports PHP 7. | + | In the most recent versions of the module, you will find only one package that supports PHP 7.4 and later.<br/> If you need a package for the previous versions of PHP, please [https://www.modulesgarden.com/support/ticket/general-support contact our support]. |
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 20px 25px;"|[[File: | + | |style="padding: 0px 0px 20px 25px;"|[[File:PHP74_81.png]] |
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px | + | |style="padding: 0px 0px 10px 15px;"| '' '''Important''': This situation does not affect [https://www.modulesgarden.com/products/whmcs/proxmox-cloud#open-source-version '''the open source version'''] of this module which can be applied to any PHP from version 5.6 and later.''<br/>' '''Note''': You can check the current PHP version in your WHMCS. To do so, proceed to ''' 'Utilities' → 'System' → 'PHP Info'.''' |
− | + | ||
− | + | ||
|} | |} | ||
+ | --> | ||
{| | {| | ||
− | |style="padding: 0px 0px | + | |style="padding: 0px 0px 15px 15px;"|'''2. Extract the package and upload its content into the main WHMCS directory. |
+ | The content of the package to upload should look like this. | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px | + | |style="padding: 0px 0px 20px 25px;"|[[File:PX2_2_1.png]] |
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px | + | |style="padding: 0px 0px 10px 15px; color: #ff0000;"|'''Warning: The next step is important, make sure you do not skip it!''' <br/> |
− | The | + | |
− | + | ||
− | + | ||
− | + | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 15px 15px;"|''' | + | |style="padding: 0px 0px 15px 15px;"|'''3. Open '' 'UploadOnProxmoxServer' '' and upload content of the proper version on all Proxmox Virtual Environment servers into the '' '/' '' path.'''<br />You should upload these files '''not only during the first installation of the module but also each time you update it.'''<br/> |
− | '''''Note:''' If you wish to allow noVNC consoles, you need to configure a product using the PVE realm and set user permissions to 'PVEVMUser.' '' <br/> | + | '''''Note 1:''' If the version of the Proxmox server you are using is not available, choose the package with the '''highest version number that is lower than the one you are currently using.''''' <br/> |
+ | '''''Note 2:''' If you wish to allow noVNC consoles, you need to configure a product using the PVE realm and set user permissions to 'PVEVMUser.' '' <br/> | ||
'''''Important:''' Open Folder UploadOnProxmoxServer/5.2-10 and upload content on all your proxmox servers. Scripts must be updated on proxmox server v2.6.0 to allow Xterm.js console work.'' | '''''Important:''' Open Folder UploadOnProxmoxServer/5.2-10 and upload content on all your proxmox servers. Scripts must be updated on proxmox server v2.6.0 to allow Xterm.js console work.'' | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 15px 15px;"|''' | + | |style="padding: 0px 0px 15px 15px;"|'''4. When you install Proxmox VE Cloud VPS For WHMCS for the first time, you have to rename the '' 'license_RENAME.php' '' file.'''<br /> |
This file is located in '' 'modules/servers/proxmoxCloudVps/license_RENAME.php'. '' Rename it from '' 'license_RENAME.php' '' to '' 'license.php'. '' | This file is located in '' 'modules/servers/proxmoxCloudVps/license_RENAME.php'. '' Rename it from '' 'license_RENAME.php' '' to '' 'license.php'. '' | ||
|} | |} | ||
Line 518: | Line 598: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 15px 15px;"|''' | + | |style="padding: 0px 0px 15px 15px;"|'''5. In order to configure your license key, you have to edit a previously renamed '' 'license.php' '' file.'''<br /> |
Enter your license key between quotation marks as presented on the following screen.<br /> | Enter your license key between quotation marks as presented on the following screen.<br /> | ||
You can find your license key in our client area → '' 'My Products'. '' | You can find your license key in our client area → '' 'My Products'. '' | ||
Line 526: | Line 606: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 15px 15px;"|''' | + | |style="padding: 0px 0px 15px 15px;"|'''6. In the next step, set up the '' 'storage' '' folders as recursively writable.'''<br /> |
− | + | These folders are available under two locations: | |
− | '' your_whmcs/modules/addons/proxmoxAddon/ '' | + | * '' your_whmcs/modules/addons/proxmoxAddon/ '' |
+ | * '' your_whmcs/modules/servers/ProxmoxCloudVps/ '' | ||
|} | |} | ||
{| | {| | ||
Line 537: | Line 618: | ||
{| | {| | ||
|style="padding: 10px 0px 15px 15px;"|'''8. Firstly, you should activate Proxmox Addon.''' <br /> | |style="padding: 10px 0px 15px 15px;"|'''8. Firstly, you should activate Proxmox Addon.''' <br /> | ||
− | To do so, log in into your WHMCS and | + | To do so, log in into your WHMCS and navigate to'' 'System Settings' → 'Addon Modules'. '' Find'' 'Proxmox Addon' ''and press'' 'Activate'. ''<br/> |
'' '''Note:''' The Proxmox addon version might '''not match''' the current version of the provisioning module itself. This is completely normal due to the specific structure of the product.'' | '' '''Note:''' The Proxmox addon version might '''not match''' the current version of the provisioning module itself. This is completely normal due to the specific structure of the product.'' | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 20px 25px;"|[[File: | + | |style="padding: 0px 0px 20px 25px;"|[[File:PXC3_5.png]] |
|} | |} | ||
{| | {| | ||
Line 549: | Line 630: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 30px 25px;"|[[File: | + | |style="padding: 0px 0px 30px 25px;"|[[File:PXC3_6.png]] |
|} | |} | ||
Line 555: | Line 636: | ||
{| | {| | ||
|style="padding: 10px 0px 15px 15px;"|'''10. Now, we will show you how to configure a new product.''' <br /> | |style="padding: 10px 0px 15px 15px;"|'''10. Now, we will show you how to configure a new product.''' <br /> | ||
− | Go to '' ' | + | Go to '' 'System Settings' '' → '' 'Servers' '' and press '' 'Add New Server'. '' |
|} | |} | ||
{| | {| | ||
Line 564: | Line 645: | ||
Choose '' 'Proxmox Cloud VPS' '' from a dropdown menu and press '' 'Save Changes'. '''''<br /> | Choose '' 'Proxmox Cloud VPS' '' from a dropdown menu and press '' 'Save Changes'. '''''<br /> | ||
The last step is choosing authentication from the '' 'Authentication' '' dropdown menu.<br /> | The last step is choosing authentication from the '' 'Authentication' '' dropdown menu.<br /> | ||
− | ''Note: Authentication depends on the realm used by the user on a Proxmox server.'' | + | ''Note: Authentication depends on the realm used by the user on a Proxmox VE server.'' |
|} | |} | ||
{| | {| | ||
Line 571: | Line 652: | ||
{| | {| | ||
|style="padding: 0px 0px 15px 15px;"|'''12. After you have configured your server correctly, you will see the following screen.'''<br /> | |style="padding: 0px 0px 15px 15px;"|'''12. After you have configured your server correctly, you will see the following screen.'''<br /> | ||
− | You can check connection with the Proxmox server. To do so, simply press '' 'Test Connection' '' as shown on the screen below. | + | You can check connection with the Proxmox Virtual Environment server. To do so, simply press '' 'Test Connection' '' as shown on the screen below. |
|} | |} | ||
{| | {| | ||
Line 591: | Line 672: | ||
==Configuration of Product== | ==Configuration of Product== | ||
{| | {| | ||
− | |style="padding: 10px 0px 15px 15px;"|'''15. In order to create and configure a product, go to '' ' | + | |style="padding: 10px 0px 15px 15px;"|'''15. In order to create and configure a product, go to '' 'System Settings' → 'Products/Services'. '''''<br /> |
Click on '' 'Create a New Group'. '' | Click on '' 'Create a New Group'. '' | ||
|} | |} | ||
Line 648: | Line 729: | ||
'''Important: Keep in mind that the root password is generated automatically for KVM virtualization upon its creation and reset.'''<br /> | '''Important: Keep in mind that the root password is generated automatically for KVM virtualization upon its creation and reset.'''<br /> | ||
'''If you want to set your own password on KVM virtualization, use the [[#Cloud-Init_.28KVM.29|Cloud-Init]] option.'' | '''If you want to set your own password on KVM virtualization, use the [[#Cloud-Init_.28KVM.29|Cloud-Init]] option.'' | ||
+ | |||
+ | '''''Note:''' If you want to allow creating VMs based on 'Installation From Archive' remember to enable and select 'Archives' for the clients to choose from. <br/>List of 'Archives' to select from can be found under 'Client Area Features'.'' | ||
|} | |} | ||
{| | {| | ||
Line 683: | Line 766: | ||
===Finalizing The Configuration=== | ===Finalizing The Configuration=== | ||
{| | {| | ||
− | |style="padding: 0px 0px 15px 15px;"|'''23. Private Network Management - in order to allow clients to manage their private networks, set up the '' 'Network' '' | + | |style="padding: 0px 0px 15px 15px;"|'''23. Private Network Management - in order to allow clients to manage their private networks, set up the '' 'Network' '' and '' 'Private Network' '' sections properly.<br/> |
*Define '' 'Private Network Model' '' | *Define '' 'Private Network Model' '' | ||
*Select '' 'Bridge' '' as well as '' 'Private Bridge' '' from the dropdown menus. | *Select '' 'Bridge' '' as well as '' 'Private Bridge' '' from the dropdown menus. | ||
Line 689: | Line 772: | ||
'''''Note:''' Configure these three options for the KVM and LXC virtualization.''<br/> | '''''Note:''' Configure these three options for the KVM and LXC virtualization.''<br/> | ||
If you skip this step, clients will not be allowed to add private networks.<br/> | If you skip this step, clients will not be allowed to add private networks.<br/> | ||
+ | |||
+ | '''''Note2:''' For SDN Private Network type please refer to Tips section, [[#Tips|point 12]].'' | ||
|} | |} | ||
{| | {| | ||
Line 728: | Line 813: | ||
{| | {| | ||
|style="padding: 0px 0px 20px 15px;"|'''27. In the end of the product configuration, you have to add a cron job that is shown below (5 minutes interval suggested). | |style="padding: 0px 0px 20px 15px;"|'''27. In the end of the product configuration, you have to add a cron job that is shown below (5 minutes interval suggested). | ||
− | php -q /your_whmcs/modules/ | + | php -q /your_whmcs/modules/addons/proxmoxAddon/cron/cron.php queue |
− | Do not forget to replace '' 'your_whmcs' '' with your WHMCS root location. | + | Do not forget to replace '' 'your_whmcs' '' with your WHMCS root location. The cron can be also executed every single minute in order to perform the action more often.<br/> |
+ | In the ''Configuration of Addon'' settings, you will find the personalized URL for the cron on your server as well as more possible crons to set up for execution. | ||
|} | |} | ||
{| | {| | ||
Line 738: | Line 824: | ||
{| | {| | ||
|style="padding: 10px 0px 15px 15px;"|'''28. Proceed to '' 'Addons' '' → '' 'Proxmox Addon' '' → '' 'Settings' '' → '' 'General Settings' '' and set up cron jobs listed under the '' 'Cron' '' section.<br/> | |style="padding: 10px 0px 15px 15px;"|'''28. Proceed to '' 'Addons' '' → '' 'Proxmox Addon' '' → '' 'Settings' '' → '' 'General Settings' '' and set up cron jobs listed under the '' 'Cron' '' section.<br/> | ||
− | Please note that there are separate cron jobs dedicated to Proxmox VPS and Proxmox Cloud VPS modules - these jobs are the most important to assure fluent work of the modules, suggested frequency is 5 minutes.<br/> If you are using only Proxmox VPS, there is no need to set up the second one and the other way round.<br/> | + | Please note that there are separate cron jobs dedicated to Proxmox VE VPS and Proxmox VE Cloud VPS modules - these jobs are the most important to assure fluent work of the modules, suggested frequency is 5 minutes.<br/> If you are using only Proxmox VE VPS, there is no need to set up the second one and the other way round.<br/> |
The other ones are responsible for: | The other ones are responsible for: | ||
* Users synchronization - ''run only once'' | * Users synchronization - ''run only once'' | ||
Line 744: | Line 830: | ||
* VM migration synchronization - ''optionally run every 24 hours or just after the VM migration'' | * VM migration synchronization - ''optionally run every 24 hours or just after the VM migration'' | ||
* Tasks synchronization - ''optionally run every one hour'' | * Tasks synchronization - ''optionally run every one hour'' | ||
+ | * VM names synchronization - ''run only once'' | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 20px 25px;"|[[File: | + | |style="padding: 0px 0px 20px 25px;"|[[File:PXC3_35.png]] |
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 15px 15px;"|'''29. Next, under the Cron settings, find the '' 'Minimum VMID' '' field.'''<br/> Fill it in with a number that will be used as an ID of the first VM, the second VM will be asigned the next ID number. <br/> Here it is also possible to turn on '' 'Debug Mode' '' if you need to register module logs. | + | |style="padding: 0px 0px 15px 15px;"|'''29. Next, under the Cron settings, find the '' 'Minimum VMID' '' field.'''<br/> Fill it in with a number that will be used as an ID of the first VM, the second VM will be asigned the next ID number.<br/> Define the limit of tasks that will be executed with a single cron run, just type in the required number into the '' 'Tasks Limit' '' field.<br/> |
+ | Here it is also possible to turn on '' 'Debug Mode' '' if you need to register module logs. | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 20px 25px;"|[[File: | + | |style="padding: 0px 0px 20px 25px;"|[[File:PXC2__35_1.png]] |
|} | |} | ||
{| | {| | ||
Line 758: | Line 846: | ||
In order to create a new product, you have to add '' 'Dedicated IP'' ' to the '' 'IP Addresses' '' list in '' 'Proxmox' '' addon module.<br /> | In order to create a new product, you have to add '' 'Dedicated IP'' ' to the '' 'IP Addresses' '' list in '' 'Proxmox' '' addon module.<br /> | ||
To do so, go to '' 'IP Management' '' and press '' 'New IP Addresses'. ''<br /> | To do so, go to '' 'IP Management' '' and press '' 'New IP Addresses'. ''<br /> | ||
− | '''''Note:''' You can add | + | '''''Note:''' You can add IPv4, IPv6 addresses and IPv6 subnets. The process is the same for all types.'' |
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 20px 25px;"|[[File: | + | |style="padding: 0px 0px 20px 25px;"|[[File:PXC3_30.png]] |
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 15px 15px;"|'''31. Start | + | |style="padding: 0px 0px 15px 15px;"|'''31. Start with defining the IP address type, choose among: '' 'IPv4', IPv6' '' and '' 'IPv6 subnet'.'' '''<br/> |
− | + | Then, depending on the selected type, provide: <br/> | |
− | + | ||
+ | '''For IPv4 and IPv6 addresses types''' | ||
+ | * "Network Address" ''(eg: 192.168.1.0/24)'' | ||
+ | * "Gateway" | ||
+ | * "First IP Address" and "Last IP Address" - defines the border '''from which and up to which''' of the IP address the generation ''(including the provided addresses)'' | ||
|} | |} | ||
{| | {| | ||
|style="padding: 0px 0px 20px 25px;"|[[File:PX2__23.png]] | |style="padding: 0px 0px 20px 25px;"|[[File:PX2__23.png]] | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 15px 15px;"| | ||
+ | '''For "IPv6 Subnet" address type''' | ||
+ | *"Network Address" ''(eg: 2a00:1911:5::/64)'' | ||
+ | *"Gateway" | ||
+ | *'Number of Subnets" | ||
+ | *"CIDR" | ||
+ | *"First IP Address" and "Last IP Address" - defines the border '''from which and up to which''' of the IP address the generation ''(including the provided addresses)'' | ||
+ | |||
+ | Decide whether the created addresses will be private or not. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 25px;"|[[File:PX2__23_1.png]] | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 15px 15px;"|Move to the '' 'Details' '' tab. Choose a server from the 'Server' dropdown menu and define which virtualization it should be applied to through selecting it from the 'Virtualization' dropdown menu.<br/> | ||
+ | Remember to press '' 'Confirm' '' button when ready. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 25px;"|[[File:PX2__23_2.png]] | ||
|} | |} | ||
{| | {| | ||
Line 848: | Line 961: | ||
|} | |} | ||
--> | --> | ||
+ | |||
+ | ==[https://www.docs.modulesgarden.com/Proxmox_Proxy_Application Proxy] Installation For Console Connection== | ||
+ | {| | ||
+ | |style="padding: 10px 0px 5px 15px;"|'''A comprehensive guide detailing the installation, update instructions, and operational flow for the Proxmox Proxy application can be found in a dedicated article accessible through the following [https://www.docs.modulesgarden.com/Proxmox_Proxy_Application link].'''<br/> | ||
+ | We encourage you to refer to it for further insight into the Proxmox Proxy application. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 5px 15px;"|'''The proxy feature can be looked on as an added security boost for your infrastructure.'''<br/> | ||
+ | It hides your Proxmox server so that your clients will not get to know its actual address when connecting to the server via the console in your system.<br/> | ||
+ | To work properly, the proxy must be accessible from both the public and private net as clients connect with the proxy from the public net, without the need to connect directly to proxmox. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 5px 15px;"|'''[https://www.docs.modulesgarden.com/Proxmox_Proxy_Application Proxy]''' must be '''connected with Proxomx server'''. To verify if the connection between these two is successful, you may run the following command: | ||
+ | curl -v <nowiki>https://10.10.11.48:8006</nowiki> | ||
+ | where 10.10.11.48:8006 is the '''node IP address'''. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 10px 0px 5px 15px;"|'''Before you begin the process of connecting the console to the server through a proxy, you need to download the proxy application file.'''<br/> | ||
+ | The file can be found under the following '''[https://www.modulesgarden.com/client-area/dl.php?type=d&id=5290 link]''' after you have logged in to your ModulesGarden account. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 10px 0px 5px 15px;"|'''1. Create a new VPS server, which you may run on a Proxmox server.'''<br/> | ||
+ | It is advised to use the KVM virtualization type. <br/> | ||
+ | |||
+ | <span style="color: Red">'' '''Warning!''' The used VPS may NOT have any services running, such as: PHP, WebServer (e.g. apache, nginx) or MySQL server.'' </span> | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 5px 15px;"|'''2. Configure the network on the virtual machine, make sure the network works correctly, to do so you may use the below command:''' | ||
+ | ping modulesgarden.com | ||
+ | |||
+ | If everything is fine, assure that basic server security settings have been established.<br/> | ||
+ | You may turn off login with a password and turn on login with a key, change the SSH port, set up firewalls etc. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 10px 15px;"|'''3. Log into the machine on which you are going to set up proxy. ''' | ||
+ | |} | ||
+ | {|' | ||
+ | |style="padding: 0px 0px 5px 15px;"|'''4. Install the docker engine and the docker compose:''' | ||
+ | ''https://docs.docker.com/engine/install/''<br/> | ||
+ | ''https://docs.docker.com/compose/install/'' | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 5px 15px;"|'''5. Upload the application files into a proper directory, eg: ''/root/proxmox-proxy'' (create if needed).''' <br/> | ||
+ | Then unzip the files. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 5px 15px;"|'''6. Move to the following catalog:''' | ||
+ | cd /root/proxmox-proxy | ||
+ | Note that the exact directory depends on the previous step where you uploaded te files. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 10px 15px;"|'''7. Purchase or generate your own SSL certificate, and then use the certificate to overwrite the following files: '' 'nginx/localhost.crt' '' and '' 'nginx/localhost.key' ''. ''' | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 10px 15px;"|'''8. Find the '' 'example.env' '' file and rename it to '' '.env'.'' '''<br/> | ||
+ | Then open the just renamed '' '.env' '' file and provide a random set of signs to create the database and root passwords: ''DB_PASSWORD'' and ''MYSQL_ROOT_PASSWORD'' <br/> | ||
+ | These data will be automatically used when creating the database. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 5px 15px;"|'''9. Run the below command:'''<br/> | ||
+ | docker-compose up --build -d | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 5px 15px;"|'''10. Move to docker container:''' | ||
+ | docker exec -it proxyphp bash | ||
+ | |||
+ | and run the installation script: | ||
+ | php -q /var/www/html/installer.php install | ||
+ | When ready, find the API Key and keep it safe, you will need it later on when pasting the data into the ''Proxmox Addon'', see point 12 for details. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 5px 15px;"|'''11. Next, copy your machine IP address to WHMCS. You may check the IP address using the below command:''' | ||
+ | ip a | ||
+ | '''''Note:''' Remember to check the IP address in your virtual machine, not in the proxyphp conatiner.'' | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 15px 15px;"|'''12. Configure all the required data in the Proxomox addon in your WHMCS.'''<br/> | ||
+ | Move to '' 'Addons' → 'Proxmox Addon' → 'Settings'.'' At the bottom you will find section '' 'Console Proxy' '' with '' 'Host' '' and '' 'API Key' '' fields.<br/> | ||
+ | |||
+ | Note that the '''Host''' field may include either an '''IP address''' or a '''domain'''. It is extremely important that you paste here '''the same data as the ones used in the SSL certificate'''.<br/> The below screen shows an example with an IP address which is not the only correct possible option here.<br/> | ||
+ | |||
+ | Provide the necessary data and confirm the changes. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 25px;"|[[File:PX3_4_2.png]] | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 5px 15px;"|'''13. Make sure the server works. In order to do so, please open the address: ''<nowiki>https://{vmip}:8443</nowiki>''.'''<br/> | ||
+ | Remember to replace ''{vmip}'' with a valid virtual machine IP address, for example: ''https://192.168.8.113:8443/''<br/> | ||
+ | When you see ''{"errors":["Invalid API Endpoint"]}'' it means that the servers correctly responds. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 15px;"|'''14. Finally, try to open the noVNC console on your WHMCS Proxmox product to check if the proxy configuration is working properly.''' | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 5px 15px;"|'''Important:''' If your certificate expires in the meantime, you will need to '''buy/generate''' a new one and follow the below steps: | ||
+ | * move to the '''/root/proxmox-proxy'' catalog ''(the directory may differ depending on your setup)'' | ||
+ | * replace the '''nginx/localhost.crt''' and '''nginx/localhost.key''' files | ||
+ | * run the following command: | ||
+ | docker-compose up --build -d | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 5px 15px;"|'''''Note:''' If you ever encounter an iconcube error while rerunning the 'docker-compose up' command, delete all local docker images related to your docker file using the following command and try again.'' | ||
+ | $ docker rmi -f $(docker images -a -q) | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 30px 15px;"|For instruction on how to react in case an '''update is required''', please refer to the dedicated article including all details on the [https://www.docs.modulesgarden.com/Proxmox_Proxy_Application Proxmox Proxy] application. | ||
+ | |} | ||
==Cloud-Init (KVM)== | ==Cloud-Init (KVM)== | ||
Line 902: | Line 1,123: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 15px 15px;"|A full list of available variables related to a Proxmox Cloud VPS type of the product/service: | + | |style="padding: 0px 0px 15px 15px;"|A full list of available variables related to a Proxmox VE Cloud VPS type of the product/service: |
{$vm.id} {$vm.name} {$vm.password} {$vm.passwordHash} {$vm.ipv4Addresses} {$vm.ipv6Addresses} {$vm.ciuser} {$vm.sshkeys} | {$vm.id} {$vm.name} {$vm.password} {$vm.passwordHash} {$vm.ipv4Addresses} {$vm.ipv6Addresses} {$vm.ciuser} {$vm.sshkeys} | ||
+ | |||
+ | Where: | ||
+ | *''$model'' variables - stands for following [https://classdocs.whmcs.com/8.3/WHMCS/Service/Service.html services] | ||
+ | *''$customfields'' variable - stands for all custom fields that exist in your service | ||
+ | |||
+ | '''''Important:''' If you want to use a '''{} sign''' in your script that has '''no variable''' inside, you must place it inside: '''{literal}{/literal}''', for example: '{literal}{"X": "Y"}{/literal}'. <br/>Otherwise, errors will occur.'' | ||
+ | |||
|} | |} | ||
{| | {| | ||
Line 933: | Line 1,161: | ||
*'''Enable Cloud-Init''' <br/> | *'''Enable Cloud-Init''' <br/> | ||
*'''Default User''' - provide the username that will be used for the VM instead of using the '' 'Service Username' '' field or the default user of the configured image. Otherwise, leave empty.<br/> | *'''Default User''' - provide the username that will be used for the VM instead of using the '' 'Service Username' '' field or the default user of the configured image. Otherwise, leave empty.<br/> | ||
− | *'''Custom Cloud-Init Configuration''' - specify custom files to replace the automatically generated ones at the start. | + | *'''Custom Cloud-Init Configuration''' - specify custom files to replace the automatically generated ones at the start. |
+ | *'''Storage''' - the directory on which the CD-ROM ISO image is stored | ||
<!-- | <!-- | ||
*'''Cloud Init''' - select what scripts will be executed on VM create or change package. If you are using the configurable options you can also define the '' 'cloudInit|Cloud Init' '' option (Proxmox VPS only).<br/>'' '''Important:''' If you use multiple scripts configuration of the same type (e.g. 'Network Config'), remember that they will be connected into '''one script''' before sent to the server.<br/>Therefore, make sure that these scrips can work properly with each other.'' | *'''Cloud Init''' - select what scripts will be executed on VM create or change package. If you are using the configurable options you can also define the '' 'cloudInit|Cloud Init' '' option (Proxmox VPS only).<br/>'' '''Important:''' If you use multiple scripts configuration of the same type (e.g. 'Network Config'), remember that they will be connected into '''one script''' before sent to the server.<br/>Therefore, make sure that these scrips can work properly with each other.'' | ||
*'''CD/DVD-ROM Type''' - an additional CD-ROM in which the ISO image is mounted with a ready-to-use script for the VM | *'''CD/DVD-ROM Type''' - an additional CD-ROM in which the ISO image is mounted with a ready-to-use script for the VM | ||
− | + | ||
--> | --> | ||
|} | |} | ||
Line 994: | Line 1,223: | ||
=Management= | =Management= | ||
{| | {| | ||
− | |style="padding: 10px 0px 15px 15px;"|''' Proxmox Cloud VPS For WHMCS allows your customers to manage their PVE servers in the WHMCS client area.'''<br /> | + | |style="padding: 10px 0px 15px 15px;"|''' Proxmox VE Cloud VPS For WHMCS allows your customers to manage their PVE servers in the WHMCS client area.'''<br /> |
At the same time, you can monitor and handle each product from your WHMCS admin area.<br /> You can find here: | At the same time, you can monitor and handle each product from your WHMCS admin area.<br /> You can find here: | ||
*Module Commands | *Module Commands | ||
*Available Resources | *Available Resources | ||
− | *Virtual Machines | + | *Virtual Machines: |
+ | **Import VM | ||
+ | **Delete VM | ||
+ | **Migrate VM <br/> You may enable '' 'Online''' migration ''(no need to shut down the server before migration)'' and toggle '' 'Migration With Local Disks'.'' | ||
*IP Addresses | *IP Addresses | ||
*User Details | *User Details | ||
Line 1,015: | Line 1,247: | ||
:Total - full server RAM | :Total - full server RAM | ||
:Free - difference between Total Server RAM and Assigned RAM | :Free - difference between Total Server RAM and Assigned RAM | ||
− | '''Suspended''' - number of suspended accounts per size in MB ''E.g.: (1/500 MB) when there is only one suspended account (occupying 500MB of that account) assigned to Proxmox VPS server.'' | + | '''Suspended''' - number of suspended accounts per size in MB ''E.g.: (1/500 MB) when there is only one suspended account (occupying 500MB of that account) assigned to Proxmox VE VPS server.'' |
|} | |} | ||
{| | {| | ||
Line 1,026: | Line 1,258: | ||
=====VMs===== | =====VMs===== | ||
{| | {| | ||
− | |style="padding: 10px 0px 20px 15px;"| The '' ' | + | |style="padding: 10px 0px 20px 15px;"| The '' 'Services' '' tab includes a list of created virtual machines on this server. Take a quick look at information on domain, status, bandwidth and IP addresses.<br/> |
To view information about a VM, simply press the more info icon. | To view information about a VM, simply press the more info icon. | ||
|} | |} | ||
Line 1,041: | Line 1,273: | ||
=====Clusters===== | =====Clusters===== | ||
{| | {| | ||
− | |style="padding: 10px 0px | + | |style="padding: 10px 0px 15px 15px;"| The next tab contains the list of clusters with information on uptime, CPU as well as CPU, SWAP, memory and disk usage data.<br/> |
+ | '''''Important:''' Defined here node limits are strongly connected with the [[#Load_Balancer|Load Balancer]] and [[#Node_Prioritization_Method|node prioritization method]] used by the module to create new virtual machines.'' | ||
|} | |} | ||
{| | {| | ||
Line 1,047: | Line 1,280: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px | + | |style="padding: 0px 0px 15px 15px;"|Press the "Edit" icon to manage the node and its limits. |
+ | * Allow To Create VM - if enabled, a VM can be created on this node | ||
+ | * Virtual Machines Number - define the maximum number of VM that can be created on this node | ||
+ | * Maximum Number of CPUs - set the top limit of CPUs on this single node | ||
+ | * Maximum Disk Size - set the top storage size allowed on this node | ||
+ | * Maximum RAM Size - set the maximum amount of RAM allowed on this node | ||
+ | * Default Storage - select the default storage for the VM created on this node<br/> | ||
+ | Setting node limits is crucial as creating virtual machines is largely based on them, once reached, a new virtual machine cannot be created on that node. | ||
|} | |} | ||
{| | {| | ||
Line 1,077: | Line 1,317: | ||
{| | {| | ||
|style="padding: 0px 0px 15px 15px;"|Next, choose a VM to convert.<br /> | |style="padding: 0px 0px 15px 15px;"|Next, choose a VM to convert.<br /> | ||
− | Fill out '' 'Description' '' field and press '' ' | + | Fill out '' 'Description' '' field and press '' 'Confirm'. ''<br/> |
'''Important: Selected VM will be destroyed in the process.''' | '''Important: Selected VM will be destroyed in the process.''' | ||
|} | |} | ||
Line 1,090: | Line 1,330: | ||
|} | |} | ||
− | =====Settings===== | + | =====Server Settings===== |
{| | {| | ||
|style="padding: 10px 0px 15px 15px;"|Here you can define the VM IDs range that will be used for newly created VMs on this server. Please note that to use this feature, you also need to enable the "Use VM Ranges" setting in the product configuration.<br />Define ID range and save changes. <br/> | |style="padding: 10px 0px 15px 15px;"|Here you can define the VM IDs range that will be used for newly created VMs on this server. Please note that to use this feature, you also need to enable the "Use VM Ranges" setting in the product configuration.<br />Define ID range and save changes. <br/> | ||
Line 1,106: | Line 1,346: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 20px 25px;"|[[File: | + | |style="padding: 0px 0px 20px 25px;"|[[File:PX3_34_1.png]] |
|} | |} | ||
{| | {| | ||
Line 1,112: | Line 1,352: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 20px 25px;"|[[File: | + | |style="padding: 0px 0px 20px 25px;"|[[File:PX3_34_2.png]] |
|} | |} | ||
{| | {| | ||
Line 1,121: | Line 1,361: | ||
|} | |} | ||
− | ==== | + | ====Services List==== |
{| | {| | ||
− | |style="padding: 10px 0px 15px 15px;"|In '' 'Addons' '' → '' 'Proxmox Addon' '' → '' 'Servers' '' → '' ' | + | |style="padding: 10px 0px 15px 15px;"|In '' 'Addons' '' → '' 'Proxmox Addon' '' → '' 'Servers' '' → '' 'Services List' '' you can find details of any Proxmox product.<br /> |
|} | |} | ||
{| | {| | ||
Line 1,169: | Line 1,409: | ||
===IP Management=== | ===IP Management=== | ||
{| | {| | ||
− | |style="padding: 10px 0px 15px 15px;"|In the '' 'IP Management' '' tab you can manage the IP addresses of Proxmox products.<br/> You can create both single IP addresses and IP pools which then can be assigned to created VMs. | + | |style="padding: 10px 0px 15px 15px;"|In the '' 'IP Management' '' tab you can manage the IP addresses of Proxmox products.<br/> You can create both single IP addresses ''(IPv4 and IPv6 are supported)'' and IP pools which then can be assigned to created VMs.<br/> |
+ | '''''Important!:''' In order to create a virtual machine, you must previously add '''public''' IP addresses. <br/> In case you do not own any public IP addresses in the database, you must previously enable the '''"cloud-init" '''option, only then it will be possible to create a VM with a '''private IP address'''.'' | ||
|} | |} | ||
{| | {| | ||
Line 1,179: | Line 1,420: | ||
*servers or nodes that will use them | *servers or nodes that will use them | ||
*virtualization types ''(different VMs will use different IP pools)'' | *virtualization types ''(different VMs will use different IP pools)'' | ||
+ | '''''Note:''' please go back to point '''31''' of the [[#Configuration_of_Addon|addon configuration]] to learn more details about adding IP addresses.'' | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px | + | |style="padding: 0px 0px 20px 25px;"|[[File:PX2_30_1.png]] |
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 30px 25px;"|[[File:PX2_30_11.png]] | ||
+ | |} | ||
+ | ====IP Logs==== | ||
+ | {| | ||
+ | |style="padding: 10px 0px 15px 15px;"|The '' 'IP Logs' '' includes the history of the IP addresses that were removed by the admin and which are again available in the proxmox addon IP Management pool.<br/> | ||
+ | Keep in mind that only addresses that were automatically added when creating the VM. Removed IP addresses, that were the manually assigned, are not logged here. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 25px;"|[[File:PXC2_30_0.png]] | ||
|} | |} | ||
===IP Manager Integration=== | ===IP Manager Integration=== | ||
{| | {| | ||
− | |style="padding: 10px 0px 15px 15px;"|Owing to the integration with [https://www.modulesgarden.com/products/whmcs/ip_manager/features IP Manager For WHMCS], you are able to easily create subnets with IP addresses and assign them to the desired products.<br/> | + | |style="padding: 10px 0px 15px 15px;"|Owing to the integration with [https://www.modulesgarden.com/products/whmcs/ip_manager/features IP Manager For WHMCS], you are able to easily create subnets with IP addresses, and assign them to the desired products.<br/> |
By activating the IP Manager submodule, settings concerning IP addresses such as 'Configurable Options' and 'Default Options' will be ignored by Proxmox VPS.<br/> | By activating the IP Manager submodule, settings concerning IP addresses such as 'Configurable Options' and 'Default Options' will be ignored by Proxmox VPS.<br/> | ||
'' '''Note:''' This integration works for '''LXC''' and '''KVM''' virtualization types.'' | '' '''Note:''' This integration works for '''LXC''' and '''KVM''' virtualization types.'' | ||
<br/><br/> | <br/><br/> | ||
− | 1. Proceed to the IP Manager For WHMCS → [https://www.docs.modulesgarden.com/IP_Manager_For_WHMCS#Subnets Subnets] tab in order to prepare IP addresses subnet for Proxmox VPS For WHMCS.<br/> | + | 1. Proceed to the IP Manager For WHMCS → [https://www.docs.modulesgarden.com/IP_Manager_For_WHMCS#Subnets Subnets] tab in order to prepare the IP addresses subnet for Proxmox VPS For WHMCS.<br/> |
− | 2. Edit the previously created | + | 2. Edit the previously created subnet, and create a custom field '' 'MAC Address' '' with a desired MAC address at each IP address in the subnet.<br/> |
− | ''' ''Note:'' Setting up MAC address is optional and can be skipped.'''<br/> | + | ''' ''Note:'' Setting up the MAC address is optional and can be skipped.'''<br/> |
More details about creating custom fields can be found [https://www.docs.modulesgarden.com/IP_Manager_For_WHMCS#Default_Custom_Fields here]. | More details about creating custom fields can be found [https://www.docs.modulesgarden.com/IP_Manager_For_WHMCS#Default_Custom_Fields here]. | ||
|} | |} | ||
Line 1,199: | Line 1,452: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 15px 15px;"|3. Afterward, create a [https://www.docs.modulesgarden.com/IP_Manager_For_WHMCS# | + | |style="padding: 0px 0px 15px 15px;"|3. Afterward, create a [https://www.docs.modulesgarden.com/IP_Manager_For_WHMCS#IP_Manager_For_WHMCS#Configurations_and_Automatic_IP_Assignment new configuration], and assign the previously created subnet to it.<br />''Note: Multiple subnets can be assigned to a single configuration.''<br /> |
− | ''Note: Multiple | + | |
− | 4. Now, link the configuration with Proxmox VPS product via a product, | + | 4. Now, link the configuration with Proxmox VPS product via a product, server or configurable option.<br /> |
− | On the following screen we have | + | On the following screen, we have carried out the linking via a product. |
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 20px 25px;"|[[File: | + | |style="padding: 0px 0px 20px 25px;"|[[File:PX_50b.png]] |
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 15px 15px;"| | + | |style="padding: 0px 0px 15px 15px;"|4. When Proxmox starts creating a virtual machine, it retrieves the assigned IP address to the service and assigns it directly to the virtual machine.<br/> |
− | + | It is possible to add '''VLAN Tag Custom Filed''' in the very same way as the "MAC Address" field.<br/> | |
− | + | The only element you need to change is the custom field name, which should be ''' 'Tag' ''' in this case. | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | The only | + | |
|} | |} | ||
{| | {| | ||
Line 1,236: | Line 1,469: | ||
|} | |} | ||
− | ===Settings=== | + | ===General Settings=== |
====Load Balancer==== | ====Load Balancer==== | ||
{| | {| | ||
|style="padding: 10px 0px 15px 15px;"|Load Balancer is an advanced tool that allows smooth rotation between nodes to find the most preferable one and create virtual machine on it.<br/> | |style="padding: 10px 0px 15px 15px;"|Load Balancer is an advanced tool that allows smooth rotation between nodes to find the most preferable one and create virtual machine on it.<br/> | ||
Set the weight of the resource that will prioritize its selection when sorting the Nodes according to the free resources.<br/> | Set the weight of the resource that will prioritize its selection when sorting the Nodes according to the free resources.<br/> | ||
− | '''''Note:''' The lowest possible weight is 1. You cannot set for example 0,5.'' | + | '''''Note:''' The lowest possible weight is 1. You cannot set for example 0,5.''<br/> |
+ | |||
+ | To learn more about nodes and their allowed limits please go back to the [[#Clusters|Clusters]] section of this documentation.<br/> | ||
|} | |} | ||
{| | {| | ||
Line 1,334: | Line 1,569: | ||
If you decide to use the '' 'Load Balancer' '' tool, define the resource weights to adjust their prioritization of nodes according to your needs. | If you decide to use the '' 'Load Balancer' '' tool, define the resource weights to adjust their prioritization of nodes according to your needs. | ||
|} | |} | ||
+ | |||
+ | ====Global Limitations==== | ||
+ | {| | ||
+ | |style="padding: 10px 0px 15px 15px;"| | ||
+ | *'' 'VLANs Limit' '' - enter the maximum number of allowed VLANS per customer | ||
+ | *'' 'Default Limit of Backup Tasks Per Node' '' - put a global limit on the number of allowed tasks to create backups per node.<br/> This general limit may be overwritten per single node in the [[#Clusters|cluster settings]] section at: ''Addon → Servers → Server Details → Edit Cluster → Tasks Limit'' | ||
+ | *'' 'Default Limit of Backup Tasks Per Storage' '' - put a global limit on the number of allowed tasks to create backups per storage. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 30px 25px;"|[[File:PXC3_30_5_0.png]] | ||
+ | |} | ||
+ | |||
+ | ====Task Settings==== | ||
+ | {| | ||
+ | |style="padding: 10px 0px 15px 15px;"|This setting can help you stay informed about failed tasks. When a threshold of task retries is reached a notification email message will be sent out.<br/> | ||
+ | You can set up a three-tier notification system with separate email contents. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 25px;"|[[File:PXC3_30_5_1.png]] | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 15px 15px;"|The default email templates include: | ||
+ | *Task name | ||
+ | *Task ID | ||
+ | *Client ID | ||
+ | *Service ID | ||
+ | *Product/Service information | ||
+ | *Domain | ||
+ | *Error Message <br/> | ||
+ | You can pick different email templates from the dropdown fields in the tasks settings or edit the default templates by navigating to '' 'System Settings' '' → '' 'Email Templates'.'' | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 30px 25px;"|[[File:PXC3_30_5_2.png]] | ||
+ | |} | ||
+ | |||
+ | ====Admin Area Features==== | ||
+ | {| | ||
+ | |style="padding: 10px 0px 15px 15px;"|The '' 'Admin area Features' '' section includes a list of all possible features that can be activated and then available or not for the admin under the product's details.<br/> Below you can find a list of features dedicated to: | ||
+ | |||
+ | *'''Proxmox VE Cloud VPS''' | ||
+ | **Virtual Machines | ||
+ | |||
+ | *'''Proxmox VE VPS''' | ||
+ | **Start | ||
+ | **Stop | ||
+ | **Reboot | ||
+ | **Shut Down | ||
+ | **Reinstall | ||
+ | **Spice Console | ||
+ | **noVNC console | ||
+ | **Xterm.js Console | ||
+ | **Information | ||
+ | **IP Set | ||
+ | **Graphs | ||
+ | |||
+ | *'''Both''' | ||
+ | **Available Resources | ||
+ | **IP Addresses | ||
+ | **Migrate | ||
+ | **User Details | ||
+ | **Reconfigure Network | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 30px 25px;"|[[File:PXC3_30_6.png]] | ||
+ | |} | ||
+ | <!-- ===Scheduled Backups Templates=== | ||
+ | {| | ||
+ | |style="padding: 10px 0px 15px 15px;"|In this section, you can create scheduled backup templates, that can be included in your products by default.<br/> | ||
+ | Preparing a template means there will be no need for the clients to set up their own scheduled backups and their virtual machines will be backed up on a predefined schedule from the get-go.<br/> | ||
+ | Start by creating and naming a scheduled backups template. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 25px;"|[[File:PX3_30_6_1.png]] | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 15px 15px;"|Once the template has been created, backup tasks can be included in it.<br/> Click on the '' 'Create Task Template' ''button. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 25px;"|[[File:PX3_30_6_2.png]] | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 15px 15px;"|Configure the backup schedule as you see fit, you can create as many task templates in the scheduled backups template as you need. <br/> | ||
+ | *'''Start Time''' - The time when the task for a backup will be issued. Make sure the time you input meets the format: 24-hour time notation with the zeroes included. For example, 07:05, 20:30 | ||
+ | *'''Day of the Week''' - The days the backups should take place each week. | ||
+ | *'''Compression type''' - Compression method to be used. | ||
+ | *'''Backup Mode''' - Decide on the backup mode. | ||
+ | *'''Send Email Message''' - Decide if an email notification about the backup should be sent always, never, or only on failure. | ||
+ | *'''Recipients''' - include the email addresses you would like the notification to be sent to. Separate each address with a comma.<br/>You can include the {clientEmail} variable to include the client's default address in the list or leave the field empty to only send the notification to that default address. | ||
+ | Click on '' 'Confirm' ''when ready. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 25px;"|[[File:PX3_30_6_3.png]] | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 15px;"|You can add more task templates if you wish, edit or delete them. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 25px;"|[[File:PX3_30_6_4.png]] | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 15px 15px;"|The scheduled backup template you create can be included as the default backup schedule of your products.<br/> | ||
+ | The '' 'Scheduled Backup template' '' field can be found in the product's module settings under '' 'Backup'.'' You can also select the '' 'Scheduled Backup Email' '' under '' 'Client Notifications'.''<br/> | ||
+ | Finally, you may allow your clients to change their scheduled backups by enabling the '' 'Backup Schedule' '' option under '' 'Client Area Features'.'' | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 30px 25px;"|[[File:PX3_30_6_5.png]] | ||
+ | |} | ||
+ | --> | ||
+ | <!-- ===Firewall Templates=== | ||
+ | {| | ||
+ | |style="padding: 10px 0px 15px 15px;"|Proxmox VE VPS For WHMCS allows you to prepare firewall templates for your clients. Those templates can be added to the product's configuration and will be applied in virtual machine creation.<br/> | ||
+ | Start by clicking on the '' 'Create Template' '' button and naming your new template. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 25px;"|[[File:PX3_30_6_6.png]] | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 15px;"|Configure the firewall options according to the needs of your clients. Make sure to click on '' 'Submit' '' to save the changes. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 25px;"|[[File:PX3_30_6_7.png]] | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 15px;"|Next, click on the '' 'Add Rule' '' button and add as many firewall rules as you need. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 25px;"|[[File:PX3_30_6_8.png]] | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 15px;"|The last step is to add the firewall template to a product. Navigate to your product's module settings and find the firewall section. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 30px 25px;"|[[File:PX3_30_6_9.png]] | ||
+ | |} | ||
+ | --> | ||
+ | |||
+ | <!-- ===Operating Systems Groups=== | ||
+ | {| | ||
+ | |style="padding: 10px 0px 15px 15px;"|Create Operating Systems Groups in the Proxmox Addon to allow clients to reinstall their virtual machines using the virtual machine templates that you allow. <br/> | ||
+ | In this section, the process of creating operating systems groups will be showcased.<br/> | ||
+ | Navigate to '' 'Settings' '' → '' 'Operating Systems Groups' '' and create a new group and name it. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 25px;"|[[File:PX3 30_6_10.png]] | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 15px 15px;"|Next we need to add templates that we want to include in this group.<br/> | ||
+ | Click on the '' 'Add Template' '' button and type in the name of the template that you want to include.<br/> '''It is crucial the name you input in the following window does not contain any typos.'''<br/> If you are not sure how your virtual machine template is named exactly. You can always check the list at a product module settings → Client Area Features → OS Templates. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 25px;"|[[File:PX3_30_6_11.png]] | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 15px 15px;"|Add all the templates you want to include in the group.<br/> | ||
+ | When finished all that remains is to add the group to the product's configuration.<br/> | ||
+ | '''''Note:''' Keep in mind that clients will '''not''' be able to transfer from one group to another after the creation of the initial virtual machine, and will only be able to pick templates from the same group when reinstalling.'' | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 30px 25px;"|[[File:PX3_30_6_12.png]] | ||
+ | |} | ||
+ | --> | ||
+ | |||
===Tasks=== | ===Tasks=== | ||
{| | {| | ||
Line 1,340: | Line 1,737: | ||
{| | {| | ||
|style="padding: 0px 0px 30px 25px;"|[[File:PXC4_30_5.png]] | |style="padding: 0px 0px 30px 25px;"|[[File:PXC4_30_5.png]] | ||
+ | |} | ||
+ | |||
+ | ===Widget=== | ||
+ | {| | ||
+ | |style="padding: 10px 0px 15px 15px;"|Proxmox VE VPS For WHMCS features a dedicated widget that displays crucial information about the module right in the WHMCS dashboard.<br/> | ||
+ | The information displayed includes: | ||
+ | * '''Faulty VM Deployments''' - a list of virtual machines that failed to be created. | ||
+ | ** Related Domain | ||
+ | ** Virtual Machine's ID | ||
+ | ** Related Task | ||
+ | ** Message | ||
+ | * '''Failed Tasks''' - a list of tasks that failed to complete | ||
+ | ** Job ID | ||
+ | ** Related Customer | ||
+ | ** Related Task | ||
+ | ** Message | ||
+ | * '''Cluster Remaining Resources''' - a list of resources still available | ||
+ | ** Server Name | ||
+ | ** Remaining Virtual Machine slots | ||
+ | ** Remaining IPv4 Addresses | ||
+ | ** Remaining IPv6 Addresses | ||
+ | ** Remaining IPv6 Subnet | ||
+ | * '''Node Resources''' - a list of the nodes available | ||
+ | ** Server Name | ||
+ | ** Node | ||
+ | ** Virtual Machine Limit | ||
+ | Each list can be hidden by disabling it in the addon's general settings.<br/> | ||
+ | Make sure to enable the widget in the '' 'Show/Hide Widgets' '' menu. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 25px;"|[[File:PX3_32_2.png]] | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 30px 15px;"| You can change the height of the widget by editing the '' 'widget.tpl' '' file located in '' '/whmcs/modules/widgets/ModulesGardenProxmoxAddon/templates'.''<br/> | ||
+ | Find this code fragment: | ||
+ | <code> | ||
+ | <style> | ||
+ | #MGProxmoxAddonWidget{ | ||
+ | height: 300px; | ||
+ | } | ||
+ | </style> | ||
+ | |||
+ | </code> | ||
+ | and change it to include <code>max-height: none !important;</code>, like this: | ||
+ | <code> | ||
+ | <style> | ||
+ | #MGProxmoxAddonWidget{ | ||
+ | height: 300px; | ||
+ | max-height: none !important; | ||
+ | } | ||
+ | </style> | ||
+ | </code> | ||
+ | Now you will be able to adjust the widget's height by editing the <code>height: value;</code> from the default '' '300px' '' to any value that fits your needs. | ||
|} | |} | ||
==Client Area== | ==Client Area== | ||
{| | {| | ||
− | |style="padding: 10px 0px 15px 15px;"|Client area interface of Proxmox Cloud VPS For WHMCS allows your clients to create their own virtual servers.<br /> | + | |style="padding: 10px 0px 15px 15px;"|Client area interface of Proxmox VE Cloud VPS For WHMCS allows your clients to create their own virtual servers.<br /> |
They can also view resources used and manage existing virtual machines. | They can also view resources used and manage existing virtual machines. | ||
|} | |} | ||
Line 1,360: | Line 1,810: | ||
|style="padding: 0px 0px 15px 15px;"|Now, provide a name of your new virtual machine and choose a proper type from the dropdown menu.<br /> | |style="padding: 0px 0px 15px 15px;"|Now, provide a name of your new virtual machine and choose a proper type from the dropdown menu.<br /> | ||
Moreover, you can add '' 'New Virtual Network' '' and '' 'New Additional Disk' '' here. | Moreover, you can add '' 'New Virtual Network' '' and '' 'New Additional Disk' '' here. | ||
− | Confirm creation through pressing '' ' | + | Confirm creation through pressing '' 'Confirm'. ''<br /> |
− | ''Note | + | '''''Note:''' Data to be filled in may differ according to which type LXC or KVM you have chosen.'' |
|} | |} | ||
{| | {| | ||
Line 1,377: | Line 1,827: | ||
{| | {| | ||
|style="padding: 10px 0px 20px 15px;"|Move to '' 'Virtual Networks' '' section to add, delete and edit your virtual networks.<br/> | |style="padding: 10px 0px 20px 15px;"|Move to '' 'Virtual Networks' '' section to add, delete and edit your virtual networks.<br/> | ||
− | Please keep in mind that this option must be enabled by administrator in your product's '' 'Module Settings' '' previously and a private IP address must be added in the Proxmox Addon.<br/> Otherwise you will not be able to add any virtual network successfully. <br/> Moreover, you can also '' 'Edit' '' (1) or '' 'Delete' '' (2) existing private networks. | + | Please keep in mind that this option must be enabled by administrator in your product's '' 'Module Settings' '' previously and a private IP address must be added in the Proxmox Addon.<br/> Otherwise you will not be able to add any virtual network successfully. <br/> If you have reached the set by the admin limit of allowed networks, the button will not be active either.<br/> |
+ | Moreover, you can also '' 'Edit' '' (1) or '' 'Delete' '' (2) existing private networks. | ||
|} | |} | ||
{| | {| | ||
Line 1,460: | Line 1,911: | ||
====Backups List==== | ====Backups List==== | ||
{| | {| | ||
− | |style="padding: 10px 0px 20px 15px;"|To create a single backup, proceed to'' 'Backups List' '' section and click '' ' | + | |style="padding: 10px 0px 20px 15px;"|To create a single backup, proceed to'' 'Backups List' '' section and click '' 'Add Backup' ''. |
|} | |} | ||
{| | {| | ||
Line 1,467: | Line 1,918: | ||
{| | {| | ||
|style="padding: 0px 0px 15px 15px;"|Now choose '' 'Compress' '' and '' 'Mode' '' from dropdown menus.<br /> | |style="padding: 0px 0px 15px 15px;"|Now choose '' 'Compress' '' and '' 'Mode' '' from dropdown menus.<br /> | ||
− | Afterwards, press '' ' | + | Afterwards, press '' 'Confirm' '' button. |
|} | |} | ||
{| | {| | ||
Line 1,476: | Line 1,927: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px | + | |style="padding: 0px 0px 20px 25px;"|[[File:PXC4__49.png]] |
|} | |} | ||
+ | <!-- | ||
+ | {| | ||
+ | |style="padding: 0px 0px 15px 15px;"|If you would like to restore singular files instead of the whole machine, or simply download them you can do that by clicking on the '' 'Browse Files' '' button. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 30px 25px;"|[[File:PXC4__49_1.png]] | ||
+ | |} | ||
+ | --> | ||
====Backup Jobs==== | ====Backup Jobs==== | ||
{| | {| | ||
|style="padding: 10px 0px 15px 15px;"|By pressing '' 'Backup Jobs' '' in the client area, you will be carried to a backup jobs management page.<br /> | |style="padding: 10px 0px 15px 15px;"|By pressing '' 'Backup Jobs' '' in the client area, you will be carried to a backup jobs management page.<br /> | ||
− | To add a new backup job press '' ' | + | To add a new backup job press '' 'Add Backup Job' '' . |
|} | |} | ||
{| | {| | ||
Line 1,489: | Line 1,948: | ||
{| | {| | ||
|style="padding: 0px 0px 15px 15px;"|Now, define backup time, mark days to run it and choose '' 'Compression' '' and '' 'Mode' '' from dropdown menus.<br /> | |style="padding: 0px 0px 15px 15px;"|Now, define backup time, mark days to run it and choose '' 'Compression' '' and '' 'Mode' '' from dropdown menus.<br /> | ||
− | Next, press '' ' | + | Next, press '' 'Confirm' '' button. You may also enable email notifications here. |
|} | |} | ||
{| | {| | ||
|style="padding: 0px 0px 30px 25px;"|[[File:PXC4__51.png]] | |style="padding: 0px 0px 30px 25px;"|[[File:PXC4__51.png]] | ||
+ | |} | ||
+ | |||
+ | ====Available Resources==== | ||
+ | {| | ||
+ | |style="padding: 10px 0px 15px 15px;"|NExt to the '' 'Backup Jobs','' there is a table with information on '' 'Available Resources'.'' <br /> You will find there data on limits put on backups: | ||
+ | *Backup Size: ''used/allowed'' | ||
+ | *Backup Files: ''used/allowed'' <br/> | ||
+ | Next to the statistics there is a comfortable and easy to read progressive chart to illustrate the usage. If size is set to '' 'Unlimited','' the chart does not show any progress.<br/> | ||
+ | Once you have reached the limits, the option to create new backups is blocked. . | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 30px 25px;"|[[File:PXC4__51_0.png]] | ||
|} | |} | ||
Line 1,515: | Line 1,986: | ||
===Network=== | ===Network=== | ||
{| | {| | ||
− | |style="padding: 10px 0px 15px 15px;"|Under the '' 'Network' '' section, you will find | + | |style="padding: 10px 0px 15px 15px;"|Under the '' 'Network' '' section, you will find '' 'Virtual Network' '' and '' 'Interfaces' '' subsections. <br /> |
Depending on the settings of the product (private network is used), they can also create/remove them. This feature is optional. | Depending on the settings of the product (private network is used), they can also create/remove them. This feature is optional. | ||
|} | |} | ||
Line 1,527: | Line 1,998: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px | + | |style="padding: 0px 0px 20px 25px;"|[[File:PXC4__52_1.png]] |
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 15px;"|It is also possible to set up '' 'Snapshot Jobs' '' where snapshots can be created according to your preferences (daily or hourly). Click on '' 'New Job' '' in order to add a new snapshot job. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 25px;"|[[File:PXC3_52_2.png]] | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 15px;"|As you complete the form, remember to fill in the '' 'Name' '' field without spaces or special characters- ''only capital letters and numbers are allowed here.'' | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 30px 25px;"|[[File:PXC3_52_3.png]] | ||
|} | |} | ||
Line 1,544: | Line 2,027: | ||
The second way (blue) consist of choosing protocol and filling source and destination ports out.<br /> | The second way (blue) consist of choosing protocol and filling source and destination ports out.<br /> | ||
Additionally, you can enable rule and add a comment to it.<br /> | Additionally, you can enable rule and add a comment to it.<br /> | ||
− | Press '' ' | + | Press '' 'Confirm' '' to create a rule. |
|} | |} | ||
{| | {| | ||
Line 1,552: | Line 2,035: | ||
|style="padding: 0px 0px 15px 15px;"|Inserting a security group consists of choosing security group and interface on which group has to be used.<br /> | |style="padding: 0px 0px 15px 15px;"|Inserting a security group consists of choosing security group and interface on which group has to be used.<br /> | ||
Additionally, you can enable security group and add a comment to it.<br /> | Additionally, you can enable security group and add a comment to it.<br /> | ||
− | Click '' ' | + | Click '' 'Confirm' '' to use the security group. |
|} | |} | ||
{| | {| | ||
|style="padding: 0px 0px 20px 25px;"|[[File:PXC4__53_3.png]] | |style="padding: 0px 0px 20px 25px;"|[[File:PXC4__53_3.png]] | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 15px 15px;"|Additional Actions: | ||
+ | *'''Download Rules''' - use this option to simply create a backup, once pressed, a file will be downloaded | ||
+ | *'''Restore Rules''' - restore any of the previously created backups created. Select one of the previously downloaded files with rules | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 25px;"|[[File:PXC4_53_01.png]] | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 15px 15px;"|You may manage the hierarchy of rules on the list. In front of each rule, you can find its '' 'Position' '' marker.<br/> The higher the rule is on the list, the higher priority the rule has assigned.You may change the rule position using the '' 'Move up/down' '' arrows. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 30px 25px;"|[[File:PXC4__53_0.png]] | ||
|} | |} | ||
Line 1,629: | Line 2,126: | ||
--> | --> | ||
− | ==IP Manager Integration== | + | ===IP Manager Integration=== |
{| | {| | ||
− | |style="padding: 10px 0px 15px 15px;"|Owing to integration with [https://www.modulesgarden.com/products/whmcs/ | + | |style="padding: 10px 0px 15px 15px;"|Owing to the integration with [https://www.modulesgarden.com/products/whmcs/ip_manager/features IP Manager For WHMCS], you are able to easily create subnets with IP addresses, and assign them to the desired products.<br/> |
− | '' '''Note:''' This integration works for | + | By activating the IP Manager submodule, settings concerning IP addresses such as 'Configurable Options' and 'Default Options' will be ignored by Proxmox VPS.<br/> |
+ | '' '''Note:''' This integration works for '''LXC''' and '''KVM''' virtualization types.'' | ||
<br/><br/> | <br/><br/> | ||
− | 1. Proceed to IP Manager For WHMCS → [https://www.docs.modulesgarden.com/IP_Manager_For_WHMCS#Subnets Subnets] tab in order to prepare IP addresses subnet for Proxmox | + | 1. Proceed to the IP Manager For WHMCS → [https://www.docs.modulesgarden.com/IP_Manager_For_WHMCS#Subnets Subnets] tab in order to prepare the IP addresses subnet for Proxmox VPS For WHMCS.<br/> |
− | 2. Edit | + | 2. Edit the previously created subnet, and create a custom field '' 'MAC Address' '' with a desired MAC address at each IP address in the subnet.<br/> |
− | More about creating custom fields can be found [https://www.docs.modulesgarden.com/IP_Manager_For_WHMCS#Default_Custom_Fields here]. | + | ''' ''Note:'' Setting up the MAC address is optional and can be skipped.'''<br/> |
+ | More details about creating custom fields can be found [https://www.docs.modulesgarden.com/IP_Manager_For_WHMCS#Default_Custom_Fields here]. | ||
|} | |} | ||
{| | {| | ||
Line 1,642: | Line 2,141: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 15px 15px;"|3. | + | |style="padding: 0px 0px 15px 15px;"|3. Afterward, create a [https://www.docs.modulesgarden.com/IP_Manager_For_WHMCS#IP_Manager_For_WHMCS#Configurations_and_Automatic_IP_Assignment new configuration], and assign the previously created subnet to it.<br />''Note: Multiple subnets can be assigned to a single configuration.''<br /> |
− | ''Note: Multiple | + | |
− | 4. Now, link the configuration with Proxmox | + | 4. Now, link the configuration with Proxmox VPS product via a product, server or configurable option.<br /> |
− | On the following screen, we have | + | On the following screen, we have carried out the linking via a product. |
|} | |} | ||
{| | {| | ||
Line 1,651: | Line 2,150: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 15px 15px;"| | + | |style="padding: 0px 0px 15px 15px;"|4. When Proxmox starts creating a virtual machine, it retrieves the assigned IP address to the service and assigns it directly to the virtual machine.<br/> |
− | + | It is possible to add '''VLAN Tag Custom Filed''' in the very same way as the "MAC Address" field.<br/> | |
+ | The only element you need to change is the custom field name, which should be ''' 'Tag' ''' in this case. | ||
|} | |} | ||
{| | {| | ||
− | + | |style="padding: 0px 0px 30px 25px;"|[[File:PX_49_1.png]] | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | |style="padding: 0px 0px 30px 25px;"|[[File: | + | |
|} | |} | ||
Line 1,675: | Line 2,168: | ||
{| | {| | ||
|style="padding: 0px 0px 15px 15px;"|Afterwards, choose the preferred virtual machine from the dropdown menu and complete the '' 'Password' '' field..<br /> | |style="padding: 0px 0px 15px 15px;"|Afterwards, choose the preferred virtual machine from the dropdown menu and complete the '' 'Password' '' field..<br /> | ||
− | Confirm importing through pressing '' ' | + | Confirm importing through pressing '' 'Confirm' '' button. |
|} | |} | ||
{| | {| | ||
Line 1,745: | Line 2,238: | ||
--> | --> | ||
+ | <!-- | ||
==Products Autoscaling== | ==Products Autoscaling== | ||
{| | {| | ||
Line 1,761: | Line 2,255: | ||
|style="padding: 0px 0px 30px 25px;"|[[File:PXC51.png]] | |style="padding: 0px 0px 30px 25px;"|[[File:PXC51.png]] | ||
|} | |} | ||
+ | --> | ||
=Tips= | =Tips= | ||
Line 1,795: | Line 2,290: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px | + | |style="padding: 0px 0px 20px 25px;"|[[File:PXC2_70_1.png]] |
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 10px 15px;"|10. Configuring '' 'Default User' '' per template. Move to '' 'Proxmox Addon' → 'Servers' → 'Server Details' → 'Templates' → 'Create/Edit Template'.''<br/> | ||
+ | You may assign a default user to a single template, that user will be automatically assigned to the newly created VM. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 15px;"|11. Creating a VM '''without any CPU limits'''. In the module settings, under '' 'Server Limits','' set up '' 'CPU Limit' '' to: '''0-1'''. Next, make sure that all values under '' 'CPU Priority' '' section are cleared. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 10px 15px;"|12. '''SDN Support''':<br/> | ||
+ | The module supports SDN private network type. It is possible to create virtual networks (vnets) at datacenter level thanks to the Software Defined Network (SDN).<br/> To learn all the details on SDN in proxmox, please navigate to the official proxmox [https://pve.proxmox.com/pve-docs/chapter-pvesdn.html documentation]. <br/> | ||
+ | |||
+ | In the module, the whole configuration of SDN is located in '' 'Module Settings' → 'Private Network' '' section. There you will find dedicated options, these are: | ||
+ | *Private Network Type | ||
+ | *SDN Zone | ||
+ | *SDN TAG Range Minimum Number | ||
+ | *SDN TAG Range Maximum Number | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 25px;"|[[File:PXC2_32.png]] | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 30px 15px;"|13. Some sections of the Proxmox Addon, such as '' 'Scheduled Backup Templates','' '' 'Firewall Templates' '' and '' 'Operating Systems Groups' '' are only applicable for Proxmox VE VPS For WHMCS.<br/> | ||
+ | Those features do not provide any functionality for Proxmox VE Cloud VPS For WHMCS. | ||
|} | |} | ||
Line 1,801: | Line 2,320: | ||
{| | {| | ||
|style="padding: 10px 0px 0px 15px;"|1. Essential guidance through the process of updating the module is offered '''[https://www.docs.modulesgarden.com/How_To_Update_WHMCS_Module here]'''.<br/> | |style="padding: 10px 0px 0px 15px;"|1. Essential guidance through the process of updating the module is offered '''[https://www.docs.modulesgarden.com/How_To_Update_WHMCS_Module here]'''.<br/> | ||
− | + | Ensure successful completion of the module update by carefully following each step, thereby preventing data loss or any unforeseen issues.<br/> Additionally, you will find a current list of supplementary actions necessary for a smooth update process there. | |
− | + | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 30px 15px;"|2. To upgrade the module from '''Proxmox Cloud For WHMCS''' to '''Proxmox Cloud VPS For WHMCS''' correctly, you need to follow these steps: <br/> | + | |style="padding: 0px 0px 30px 15px;"|2. To upgrade the module from '''Proxmox Cloud For WHMCS''' to '''Proxmox VE Cloud VPS For WHMCS''' correctly, you need to follow these steps: <br/> |
− | *Delete all old files of '' 'Proxmox Cloud For WHMCS' '' from: | + | *Delete all old files of '' 'Proxmox VE Cloud For WHMCS' '' from: |
<pre> your_whmcs/modules/servers/proxmoxCloud </pre> | <pre> your_whmcs/modules/servers/proxmoxCloud </pre> | ||
*Delete the previous cron job: | *Delete the previous cron job: | ||
Line 1,820: | Line 2,338: | ||
'''Important!''' Please remember to reissue the licence in the client area after uploading new files to the main WHMCS directory.<br/> | '''Important!''' Please remember to reissue the licence in the client area after uploading new files to the main WHMCS directory.<br/> | ||
''If you do not do this, you will get a notification about the wrong licence, and the upgrade process will not succeed.'' <br/> | ''If you do not do this, you will get a notification about the wrong licence, and the upgrade process will not succeed.'' <br/> | ||
− | *Finally, proceed to the configuration of your server and change the module type to '''Proxmox Cloud VPS''' <br/> and the '' 'Module Name' '' to '''Proxmox Cloud VPS''' in the 'Module Settings' tab of your product configuration. | + | *Finally, proceed to the configuration of your server and change the module type to '''Proxmox Cloud VPS''' <br/> and the '' 'Module Name' '' to '''Proxmox VE Cloud VPS''' in the 'Module Settings' tab of your product configuration. |
+ | |} | ||
+ | =Upgrade Guide= | ||
+ | {| | ||
+ | |style="padding: 10px 0px 30px 15px;"|Seeking a solution that offers greater flexibility, customization tailored to your precise needs, and unrestricted availability?<br/> There is an option that not only proves to be cost-effective in the long run but also includes prioritized support services, making it a truly valuable investment.<br/> | ||
+ | |||
+ | Opt for the [https://www.modulesgarden.com/products/whmcs/proxmox-ve-cloud-vps#open-source-version Open Source version] of your Proxmox VE Cloud VPS For WHMCS module to unlock these benefits.<br/> Simply click on either the '''Get Source Code''' or '''Upgrade To Lifetime''' button found on the product's page in our client area to complete the one-step upgrade process, with a '''dedicated discount''' already applied.<br/> | ||
+ | |||
+ | Follow a [https://www.docs.modulesgarden.com/How_To_Upgrade_WHMCS_Module comprehensive guide] covering the transition process, the advantages it brings, and step-by-step instructions on what to do next after the order has been successfully finalized. | ||
|} | |} | ||
Latest revision as of 08:28, 15 October 2024
Contents
|
[edit] About Proxmox VE Cloud VPS For WHMCS
Proxmox VE Cloud VPS For WHMCS offers your clients the flexibility to create, remove and freely resize their own virtual servers within resource limits defined by you.
Your customers will be able to create as many servers as they need, manage such essential aspects like backups or firewall, and access noVNC, SPICE, or Xterm.js console. |
- Admin Area Features:
✔ Create/Suspend/Unsuspend/Terminate User Account |
✔ Change Package |
✔ Change User Role |
✔ Reset Bandwidth |
✔ Migrate/Import/Delete Server |
✔ View Available Resources (Memory, vCPUs, Disks, Networks) |
✔ Display Disk And Bandwidth Usage Of Each Product |
✔ View Servers Status And Details |
✔ View Available IP Addresses |
✔ View User Details |
✔ Set Up KVM And LXC Product Configuration: |
✔ Main Configuration Limits |
✔ Server Limits |
✔ Mount Point (LXC) |
✔ Backup |
✔ Network And Private Network Settings With SDN Support |
✔ Hard Disk (KVM) |
✔ Additional Disks (KVM) |
✔ Boot |
✔ Firewall |
✔ Firewall Options (KVM) |
✔ Cloud-Init (KVM) |
✔ Guest Agent (KVM) |
✔ User |
✔ Miscellaneous |
✔ Load Balancer |
✔ KVM And LXC Configuration |
✔ Additional KVM And LXC Configuration |
✔ High Availability Cluster |
✔ Console |
✔ Client Area Features |
✔ Configurable Option Units |
✔ CPU Priority |
✔ Generate Configurable Options |
✔ Additional Configuration Features: |
✔ Define Resource Limits: |
✔ Static |
✔ Dynamic |
✔ Define Server Minimum And Maximum Resource Values |
✔ Import IP Address To Hosting IP Addresses Table |
✔ Return IP Address To IP Addresses Subnet |
✔ Add Additional IP Address To VM |
✔ Enable Backups Routing |
✔ Enable Auto VM Backups Before Reinstallation |
✔ Enable Reset Usage First Day Of Month |
✔ Define Node Selection: |
✔ Server-Node |
✔ Auto-Node |
✔ Custom Chosen Node |
- Proxmox Addon Features:
✔ Display Servers: |
✔ List Per VPS And Cloud |
✔ Clusters List |
✔ VMs List |
✔ KVM Templates |
✔ Recovery VM Configurations List With Export To Backup File |
✔ Tasks History |
✔ Statuses, Resources Usage, IP Assignments And Details |
✔ Manage Public And Private IP Addresses Per Server/VLAN/Tag/Node/Bridge: |
✔ IPv4 Addresses |
✔ IPv6 Addresses |
✔ IPv6 Subnets |
✔ View Logs Of IP Assignment Changes |
✔ VM Cleaner - Manage VM Not Existing In Your WHMCS |
✔ Convert KVM VPS To KVM Template |
✔ Define VM ID Ranges Per Server |
✔ Set Minimum VM ID For Product Without ID Ranges Defined |
✔ Provide Server Credentials For Cloud-Init Scripts |
✔ Configure Scheduled Backups, Firewall And Operating Systems Templates |
✔ Configure Resource Weights For Load Balancer Prioritization |
✔ Configure Tasks Repetition Threshold And Email Notifications |
✔ Configure Console Proxy |
✔ Synchronize User Permissions |
✔ Create And Manage Custom Cloud-Init Scripts |
- Proxmox VE Widget
✔ View Faulty VM Deployments |
✔ View Failed Tasks |
✔ View Cluster Remaining Resources |
✔ View Node Resources |
- Client Area Features:
✔ Create/Edit/Delete VM Instances On Selected Servers |
✔ Create/Edit/Delete Virtual Networks |
✔ View Available Resources And Usage (Memory, vCPUs, Disks, Networks) |
✔ Set Up Virtual Machines: |
✔ Define Machine Settings: |
✔ Name |
✔ Type |
✔ Description |
✔ Define Machine Parameters: |
✔ Location |
✔ Sockets (KVM) |
✔ Cores (LXC) |
✔ vCPU (KVM) |
✔ CPU Priority |
✔ VM RAM |
✔ SWAP (LXC) |
✔ Disk Size |
✔ Default User (KVM) |
✔ Password |
✔ SSH Key |
✔ Search Domain (KVM) |
✔ Name Servers (KVM) |
✔ Add Virtual Networks |
✔ Add Additional Disks |
✔ Start/Reboot/Stop/Shut Down/Delete Server |
✔ Reconfigure Server Network |
✔ Access noVNC, SPICE, And Xterm.js Console |
✔ View And Manage Machine Details |
✔ View And Manage Disks |
✔ View And Manage Virtual Networks And Interfaces |
✔ Take, Manage, Schedule And Restore Snapshots |
✔ Create, Manage And Restore Backups |
✔ Restore Backups From: |
✔ Any Owned Server |
✔ Proxmox Backup Server (PBS) |
✔ Restore Backups Of: |
✔ Selected Single Files And Directories With Option To Download Them (PBS) |
✔ Full Server Backups |
✔ Schedule Automatic Backups In Defined Periods |
✔ Edit Firewall Options And Manage Its Rules |
✔ View Tasks History |
✔ View CPU/Disk/Memory/Network Graphs Usage |
✔ Reinstall Server Using: |
✔ OS Templates (KVM) |
✔ ISO Images |
✔ Choose Server Resources While Ordering And Upgrade/Downgrade Them Freely |
- Configurable Options:
✔ KVM Limits: |
✔ CPU Sockets |
✔ CPU Cores |
✔ CPU Limit |
✔ CPU Units Limit |
✔ Memory |
✔ Storage |
✔ IPv4 Addresses |
✔ IPv6 Addresses |
✔ IPv6 Subnets |
✔ Backups Size |
✔ Backups Files |
✔ Snapshots |
✔ Bandwidth |
✔ Network Rate |
✔ VCPUs |
✔ Virtual Networks |
✔ Snapshot Jobs |
✔ Storage Disk Space |
✔ LXC Limits: |
✔ CPU Limit |
✔ CPU Units Limit |
✔ Memory |
✔ SWAP |
✔ Storage |
✔ IPv4 Addresses |
✔ IPv6 Addresses |
✔ IPv6 Subnets |
✔ Backups Size |
✔ Backups Files Limit |
✔ Snapshots |
✔ Bandwidth |
✔ Network Rate |
✔ Virtual Networks |
✔ Snapshot Jobs |
✔ Storage Disk Space |
- General Info:
✔ Supports Cloud-Init (KVM) |
✔ Supports PVE And PAM Authentication |
✔ Supports KVM And LXC Virtualization |
✔ Supports Proxy For Proxmox Console Connections |
✔ Integrated With Advanced Billing For WHMCS - Actual Server Resource Usage Billing |
✔ Integrated With Proxmox VE VPS For WHMCS - Remote Provisioning And Management Of Virtual Servers |
✔ Integrated With IP Manager For WHMCS - Complete Control And Easy Assignment Of IP Subnets (LXC) |
✔ Fully Integrated With Lagom Client Theme |
✔ Multi-Language Support |
✔ Supports Proxmox VE 6.X, 7.X And 8.X |
✔ Supports IPv4 And IPv6 |
✔ Supports PHP 8.2 Back To PHP 7.4 |
✔ Supports WHMCS Themes "Six" And "Twenty-One" |
✔ Supports V8.11 Back To WHMCS V8.8 |
✔ Requires ionCube Loader V13 Or Later |
✔ Easy Module Upgrade To Open Source Version |
[edit] Installation and Configuration
This tutorial will show you how to successfully install and configure Proxmox VE Cloud VPS For WHMCS. We will guide you step by step through the whole installation and configuration process. |
[edit] Installation
1. Log in to our client area and download the module. |
2. Extract the package and upload its content into the main WHMCS directory.
The content of the package to upload should look like this. |
Warning: The next step is important, make sure you do not skip it! |
3. Open 'UploadOnProxmoxServer' and upload content of the proper version on all Proxmox Virtual Environment servers into the '/' path. You should upload these files not only during the first installation of the module but also each time you update it. Note 1: If the version of the Proxmox server you are using is not available, choose the package with the highest version number that is lower than the one you are currently using. |
4. When you install Proxmox VE Cloud VPS For WHMCS for the first time, you have to rename the 'license_RENAME.php' file. This file is located in 'modules/servers/proxmoxCloudVps/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. In the next step, set up the 'storage' folders as recursively writable. These folders are available under two locations:
|
[edit] Activation of Proxmox Addon
8. Firstly, you should activate Proxmox Addon. To do so, log in into your WHMCS and navigate to 'System Settings' → 'Addon Modules'. Find 'Proxmox Addon' and press 'Activate'. Note: The Proxmox addon version might not match the current version of the provisioning module itself. This is completely normal due to the specific structure of the product. |
9. In the next step, you need to permit access to this module. To do so, click on the 'Configure' button. Tick 'Full Administrator' and press 'Save Changes'. |
[edit] Configuration of Server
10. Now, we will show you how to configure a new product. Go to 'System Settings' → 'Servers' and press 'Add New Server'. |
11. Next, enter your server name, IP address, username and password. Choose 'Proxmox Cloud VPS' from a dropdown menu and press 'Save Changes'. |
12. After you have configured your server correctly, you will see the following screen. You can check connection with the Proxmox Virtual Environment server. To do so, simply press 'Test Connection' as shown on the screen below. |
13. It is time to create a server group. To do so, click on 'Create New Group'. |
14. Enter name, click on your previously created server, press 'Add' and afterwards 'Save Changes'. |
[edit] Configuration of Product
15. In order to create and configure a product, go to 'System Settings' → 'Products/Services'. Click on 'Create a New Group'. |
16. Enter the product group name and press 'Save Changes'. |
17. When you have a product group, you are able to create your product. To create a product, click on 'Create a New Product'. |
18. Afterward, choose your product group from dropdown menus and point its type, enter your product name and choose 'Proxmox Cloud VPS' as a module name. Press 'Continue'. 'Product Type' can be set to 'Server/VPS' but nameservers will need to be added later. |
19. Now, go to the 'Module Settings' section and choose your previously created server group from the dropdown menu. Next, click on 'Save Changes'. |
20. Firstly, choose 'Virtualization Type' from the dropdown menu. Then, proceed to the next section which is 'Main Configuration' and set proper values here. Available virtualization types:
You can also choose how often the bandwidth usage should be calculated. |
[edit] KVM Virtualization Type
21. The setting of the KVM virtualization type (skip this step if you have chosen the LXC virtualization type). There are a few sections underlined that need your attention. Please, complete carefully the 'KVM Configuration' , 'Additional Disks' , 'Client Area Features' sections. Note: If you want to allow creating VMs based on 'Installation From Archive' remember to enable and select 'Archives' for the clients to choose from. |
[edit] LXC Virtualization Type
22. Setting of the LXC virtualization type (skip this step if you have chosen the KVM virtualization type). Firstly, complete the 'General' configuration and then proceed to the 'Main Configuration' , 'LXC Configuration' , 'Network' , and 'Client Area Features' sections. |
[edit] Finalizing The Configuration
23. Private Network Management - in order to allow clients to manage their private networks, set up the 'Network' and 'Private Network' sections properly.
Note: Configure these three options for the KVM and LXC virtualization. Note2: For SDN Private Network type please refer to Tips section, point 12. |
24. The next step is setting up the configuration of backups. Define backup settings in the 'Backup' section through defining 'Storage' and enabling 'Backups Routing' . |
25. Set up server limits to control the size of created servers. |
26. The final step is generating 'Configurable Options' . Click on the 'Create Configurable Options' button. |
Now, you may decide which options should be generated for your product. Adjust configurable options to your needs and press 'Confirm' . |
27. In the end of the product configuration, you have to add a cron job that is shown below (5 minutes interval suggested).
php -q /your_whmcs/modules/addons/proxmoxAddon/cron/cron.php queue Do not forget to replace 'your_whmcs' with your WHMCS root location. The cron can be also executed every single minute in order to perform the action more often. |
Congratulations! You have just finished the installation and configuration of the module. |
[edit] Configuration of Addon
28. Proceed to 'Addons' → 'Proxmox Addon' → 'Settings' → 'General Settings' and set up cron jobs listed under the 'Cron' section. Please note that there are separate cron jobs dedicated to Proxmox VE VPS and Proxmox VE Cloud VPS modules - these jobs are the most important to assure fluent work of the modules, suggested frequency is 5 minutes.
|
29. Next, under the Cron settings, find the 'Minimum VMID' field. Fill it in with a number that will be used as an ID of the first VM, the second VM will be asigned the next ID number. Define the limit of tasks that will be executed with a single cron run, just type in the required number into the 'Tasks Limit' field. Here it is also possible to turn on 'Debug Mode' if you need to register module logs. |
30. Adding a new IP address (if you are not using IP Manager For WHMCS). In order to create a new product, you have to add 'Dedicated IP ' to the 'IP Addresses' list in 'Proxmox' addon module. |
31. Start with defining the IP address type, choose among: 'IPv4', IPv6' and 'IPv6 subnet'. Then, depending on the selected type, provide: For IPv4 and IPv6 addresses types
|
For "IPv6 Subnet" address type
Decide whether the created addresses will be private or not. |
Move to the 'Details' tab. Choose a server from the 'Server' dropdown menu and define which virtualization it should be applied to through selecting it from the 'Virtualization' dropdown menu. Remember to press 'Confirm' button when ready. |
32. You are now able to create new virtual machines at the product. The client area of a successfully created product should look similar to the one presented on the screen below. |
[edit] Proxy Installation For Console Connection
A comprehensive guide detailing the installation, update instructions, and operational flow for the Proxmox Proxy application can be found in a dedicated article accessible through the following link. We encourage you to refer to it for further insight into the Proxmox Proxy application. |
The proxy feature can be looked on as an added security boost for your infrastructure. It hides your Proxmox server so that your clients will not get to know its actual address when connecting to the server via the console in your system. |
Proxy must be connected with Proxomx server. To verify if the connection between these two is successful, you may run the following command:
curl -v https://10.10.11.48:8006 where 10.10.11.48:8006 is the node IP address. |
Before you begin the process of connecting the console to the server through a proxy, you need to download the proxy application file. The file can be found under the following link after you have logged in to your ModulesGarden account. |
1. Create a new VPS server, which you may run on a Proxmox server. It is advised to use the KVM virtualization type. Warning! The used VPS may NOT have any services running, such as: PHP, WebServer (e.g. apache, nginx) or MySQL server. |
2. Configure the network on the virtual machine, make sure the network works correctly, to do so you may use the below command:
ping modulesgarden.com If everything is fine, assure that basic server security settings have been established. |
3. Log into the machine on which you are going to set up proxy. |
4. Install the docker engine and the docker compose:
https://docs.docker.com/engine/install/ |
5. Upload the application files into a proper directory, eg: /root/proxmox-proxy (create if needed). Then unzip the files. |
6. Move to the following catalog:
cd /root/proxmox-proxy Note that the exact directory depends on the previous step where you uploaded te files. |
7. Purchase or generate your own SSL certificate, and then use the certificate to overwrite the following files: 'nginx/localhost.crt' and 'nginx/localhost.key' . |
8. Find the 'example.env' file and rename it to '.env'. Then open the just renamed '.env' file and provide a random set of signs to create the database and root passwords: DB_PASSWORD and MYSQL_ROOT_PASSWORD |
9. Run the below command:docker-compose up --build -d |
10. Move to docker container:
docker exec -it proxyphp bash and run the installation script: php -q /var/www/html/installer.php install When ready, find the API Key and keep it safe, you will need it later on when pasting the data into the Proxmox Addon, see point 12 for details. |
11. Next, copy your machine IP address to WHMCS. You may check the IP address using the below command:
ip a Note: Remember to check the IP address in your virtual machine, not in the proxyphp conatiner. |
12. Configure all the required data in the Proxomox addon in your WHMCS. Move to 'Addons' → 'Proxmox Addon' → 'Settings'. At the bottom you will find section 'Console Proxy' with 'Host' and 'API Key' fields. Note that the Host field may include either an IP address or a domain. It is extremely important that you paste here the same data as the ones used in the SSL certificate. Provide the necessary data and confirm the changes. |
13. Make sure the server works. In order to do so, please open the address: https://{vmip}:8443. Remember to replace {vmip} with a valid virtual machine IP address, for example: https://192.168.8.113:8443/ |
14. Finally, try to open the noVNC console on your WHMCS Proxmox product to check if the proxy configuration is working properly. |
Important: If your certificate expires in the meantime, you will need to buy/generate a new one and follow the below steps:
docker-compose up --build -d |
Note: If you ever encounter an iconcube error while rerunning the 'docker-compose up' command, delete all local docker images related to your docker file using the following command and try again.
$ docker rmi -f $(docker images -a -q) |
For instruction on how to react in case an update is required, please refer to the dedicated article including all details on the Proxmox Proxy application. |
[edit] Cloud-Init (KVM)
Use Cloud-Init to configure the system during installation, first-boot and package change. Cloud-Init was initially developed to provide early initialization of cloud instances. Click here to learn more about Cloud-Init configuration. Note: Cloud-Init functionality is supported for the KVM virtualization only. |
[edit] Custom Configuration In Addon
[edit] Cloud-Init Scripts
The Cloud-Init Scripts section allows adding ready scripts that will be available to choose from in the products' configuration page. The selected there script will be used while crating the virtual machine. Press 'Add New' to manually add your script. |
Name your new Cloud-Init script and type in or paste a ready configuration. The configuration must include:
Here is an exemplary configuration of a Cloud-Init script. You may alter it to fit your settings and paste into the 'Script' ' field: #cloud-config hostname: {$domain} manage_etc_hosts: true fqdn: {$domain} user: {$username} password: {$passwordHash} chpasswd: expire: False users: - default package_upgrade: true |
A full list of available variables related to a Proxmox VE Cloud VPS type of the product/service:
{$vm.id} {$vm.name} {$vm.password} {$vm.passwordHash} {$vm.ipv4Addresses} {$vm.ipv6Addresses} {$vm.ciuser} {$vm.sshkeys} Where:
Important: If you want to use a {} sign in your script that has no variable inside, you must place it inside: {literal}{/literal}, for example: '{literal}{"X": "Y"}{/literal}'. |
Manage created Cloud-Init scripts, edit/delete singe scripts or use mass action to delete numerous scripts. |
[edit] Server Details
In order to use the Cloud-Init successfully, you need to also provide SSH details to let the script send the IP addresses to the Proxmox server. Move to Servers → Servers List → Details → Settings, there you will find fields that are responsible for the correct SSH connection.
You also have to select the 'Snippet Storage' to locate the Cloud-Init script in the correct catalog. |
[edit] Configuration Of Product
To to allow you clients to use cloud-init you need to enable it in the Proxmox product configuration. Before you start we recommend learning the details about cloud-init configuration on your Proxmox server - click here for more details.
|
Among other client area features, find 'Cloud-Init Script' and select the scripts that your clinets will be allowed to choose from when creating a new virtual machine. |
[edit] Configuration Of Proxmox Server
The process of setting up Cloud-Init on the Proxmox server is described here. Additionally, you can use the following commands that can be useful for debugging.
rm -rf /var/lib/cloud/sem/* /var/lib/cloud/instance /var/lib/cloud/instances/* && cloud-init init && cloud-init modules -m final
cat /var/log/cloud-init.log cat /var/log/cloud-init-output.log |
[edit] Management
Proxmox VE Cloud VPS For WHMCS allows your customers to manage their PVE servers in the WHMCS client area. At the same time, you can monitor and handle each product from your WHMCS admin area.
|
[edit] Management of Addon
[edit] Servers Management
[edit] Servers List
In 'Addons' → 'Proxmox Addon' → 'Servers' → 'Servers List' you can find the configured Proxmox servers. RAM details:
Suspended - number of suspended accounts per size in MB E.g.: (1/500 MB) when there is only one suspended account (occupying 500MB of that account) assigned to Proxmox VE VPS server. |
Through pressing 'Edit' icon you will be moved to the server edit page - see point number 10 of Server Configuration. Press 'More Details' icon and you will get extended information on the selected server. See below for more details. |
[edit] VMs
The 'Services' tab includes a list of created virtual machines on this server. Take a quick look at information on domain, status, bandwidth and IP addresses. To view information about a VM, simply press the more info icon. |
Check the node and VMID: |
[edit] Clusters
The next tab contains the list of clusters with information on uptime, CPU as well as CPU, SWAP, memory and disk usage data. Important: Defined here node limits are strongly connected with the Load Balancer and node prioritization method used by the module to create new virtual machines. |
Press the "Edit" icon to manage the node and its limits.
Setting node limits is crucial as creating virtual machines is largely based on them, once reached, a new virtual machine cannot be created on that node. |
Press 'Node Details' and you will get all the summary and usage graphs: |
[edit] VM Cleaner
VM Cleaner allows you to track VMs existing only on your Proxmox server and that are not visible in your WHMCS. Consequently, you are allowed to sort and delete only those VMs that cannot be managed from your WHMCS. |
[edit] Templates
Under this page you can view the list of templates. You can easily convert any KVM VM on your server to a template. In order to convert a VM, press 'Create Template' button. |
Next, choose a VM to convert. Fill out 'Description' field and press 'Confirm'. |
You may also delete unused templates here. Delete single templates or use the mass action to delete templates in bulk. |
[edit] Server Settings
Here you can define the VM IDs range that will be used for newly created VMs on this server. Please note that to use this feature, you also need to enable the "Use VM Ranges" setting in the product configuration. Define ID range and save changes. Note: VM ID range allows you to sort created VMs depending on the server they were created on. |
[edit] Node Groups
Under the 'Node Groups' subsection, you can create new groups and assign nodes to them. |
Provide a name of your group and allot preferred nodes from the dropdown menu. |
Now, navigate to the 'Module Settings' of your product and find the 'Load Balancer' section. Here you can select one or more of the previously created groups. |
[edit] Services List
In 'Addons' → 'Proxmox Addon' → 'Servers' → 'Services List' you can find details of any Proxmox product. |
Press 'More Details' button to get the node and VMID information. |
[edit] Recovery VM Lists
In 'Addons' → 'Proxmox Addon' → 'Servers' → 'Recovery VM List' you can details on the created VM. Run the 'VM recovery synchronization' cron job to create and store full backups of VMs configuration, you can find it at point no 26 of the configuration instructions. |
On pressing the 'Details' icon, you will get any information on Configuration, Status and DNS: |
[edit] Tasks History
Tasks History includes a list o all module tasks with the most crucial details on them. You may delete single tasks or use mass action button to remove them in bulk. Run the 'Tasks synchronization' cron job to synchronize the tasks and view all tasks from the server, you can find it at point no 26 of the configuration instructions. |
[edit] IP Management
In the 'IP Management' tab you can manage the IP addresses of Proxmox products. You can create both single IP addresses (IPv4 and IPv6 are supported) and IP pools which then can be assigned to created VMs. Important!: In order to create a virtual machine, you must previously add public IP addresses. |
When you are creating a new IP address or a pool, you may define:
Note: please go back to point 31 of the addon configuration to learn more details about adding IP addresses. |
[edit] IP Logs
The 'IP Logs' includes the history of the IP addresses that were removed by the admin and which are again available in the proxmox addon IP Management pool. Keep in mind that only addresses that were automatically added when creating the VM. Removed IP addresses, that were the manually assigned, are not logged here. |
[edit] IP Manager Integration
Owing to the integration with IP Manager For WHMCS, you are able to easily create subnets with IP addresses, and assign them to the desired products. By activating the IP Manager submodule, settings concerning IP addresses such as 'Configurable Options' and 'Default Options' will be ignored by Proxmox VPS. |
3. Afterward, create a new configuration, and assign the previously created subnet to it. Note: Multiple subnets can be assigned to a single configuration. 4. Now, link the configuration with Proxmox VPS product via a product, server or configurable option. |
4. When Proxmox starts creating a virtual machine, it retrieves the assigned IP address to the service and assigns it directly to the virtual machine. It is possible to add VLAN Tag Custom Filed in the very same way as the "MAC Address" field. |
[edit] General Settings
[edit] Load Balancer
Load Balancer is an advanced tool that allows smooth rotation between nodes to find the most preferable one and create virtual machine on it. Set the weight of the resource that will prioritize its selection when sorting the Nodes according to the free resources. To learn more about nodes and their allowed limits please go back to the Clusters section of this documentation. |
In order to use Load Balancer you must previously enable it in the product's configuration: Define the behavior of the tool:
|
[edit] Node Prioritization Method
Let us take a look at how the sorting process works and the rules that it obeys. Let's take exemplary weights for each resource just like presented on the screen above. VMs Number Weight: 1,5 Disk Weight with the highest weight which means it has the highest priority and VMs Number Weight as the least crucial factor on a given node.
Node A (Free Ram: 60%, Free CPU: 20%, Free Disk Space: 50%, Number of VMs: 5) The next step is sorting the nodes according to each resource, by assigning them corresponding priorities from 1 to 4. |
Priority | Free Ram | Free CPU | Free Disk Space | Number of VMs |
---|---|---|---|---|
4 | Node C | Node B | Node D | Node A |
3 | Node D | Node D | Node A | Node B |
2 | Node A | Node C | Node B | Node D |
1 | Node B | Node A | Node C | Node C |
Now, the final calculation to sort nodes according to free resources, taking into account previously defined weights, is performed Sorting nodes is based on the following calculation method: Final Node Priority = (RAM Priority x RAM Weight) + (CPU Priority x CPU Weight) + (Free Disk Priority x Disk Weight) + (No. VMs Priority x VMs Weight) The results for nodes A, B, C and D (with weights and sorting priority) are following: Node A: (2 x 2,5) + ( 1 x 2 ) + ( 3 x 4 ) + ( 4 x 1,5 ) = 25 Node B: (1 x 2,5) + ( 4 x 2 ) + ( 2 x 4 ) + ( 3 x 1,5 ) = 23 Node C: (4 x 2,5) + ( 2 x 2 ) + ( 1 x 4 ) + ( 1 x 1,5 ) = 19,5 Node D: (3 x 2,5) + ( 3 x 2 ) + ( 4 x 4 ) + ( 2 x 1,5 ) = 32,5 As you can see, Node D has got the highest priority value with a result: 32,5. The above described calculations are performed every time, a 'Create' or 'Upgrade' actions are executed based on the current usage of resources on available nodes. Important: In case a given client already has an existing VM on a node, this very node will NOT be taken into account during the prioritization of resources process. If you decide to use the 'Load Balancer' tool, define the resource weights to adjust their prioritization of nodes according to your needs. |
[edit] Global Limitations
|
[edit] Task Settings
This setting can help you stay informed about failed tasks. When a threshold of task retries is reached a notification email message will be sent out. You can set up a three-tier notification system with separate email contents. |
The default email templates include:
You can pick different email templates from the dropdown fields in the tasks settings or edit the default templates by navigating to 'System Settings' → 'Email Templates'. |
[edit] Admin Area Features
The 'Admin area Features' section includes a list of all possible features that can be activated and then available or not for the admin under the product's details. Below you can find a list of features dedicated to:
|
[edit] Tasks
Under the 'Tasks' tab, you can check a list of performed tasks along with their status. Moreover, you are granted the possibility to check 'Info' for a particular task, run the task again by clicking the 'Run Task' button, or delete it. |
[edit] Widget
Proxmox VE VPS For WHMCS features a dedicated widget that displays crucial information about the module right in the WHMCS dashboard. The information displayed includes:
Each list can be hidden by disabling it in the addon's general settings. |
You can change the height of the widget by editing the 'widget.tpl' file located in '/whmcs/modules/widgets/ModulesGardenProxmoxAddon/templates'. Find this code fragment:
<style> #MGProxmoxAddonWidget{ height: 300px; } </style>
and change it to include <style> #MGProxmoxAddonWidget{ height: 300px; max-height: none !important; } </style>
Now you will be able to adjust the widget's height by editing the |
[edit] Client Area
Client area interface of Proxmox VE Cloud VPS For WHMCS allows your clients to create their own virtual servers. They can also view resources used and manage existing virtual machines. |
[edit] New Virtual Machine
In order to add a new virtual machine, press the 'Add New Virtual Machine' button. |
Now, provide a name of your new virtual machine and choose a proper type from the dropdown menu. Moreover, you can add 'New Virtual Network' and 'New Additional Disk' here.
Confirm creation through pressing 'Confirm'. |
You can now easily 'Edit' (1) or 'Delete' (2) your virtual machine.
You can find information about managing your virtual servers in next section. |
[edit] Virtual Network Management
Move to 'Virtual Networks' section to add, delete and edit your virtual networks. Please keep in mind that this option must be enabled by administrator in your product's 'Module Settings' previously and a private IP address must be added in the Proxmox Addon. |
[edit] Templates Management (KVM Only)
Once you press 'Templates', you will be redirected to a site where you will find the list of currently created templates along with their details and access to basic actions. |
You may edit or delete existing templates. To add a new one, simply press 'Add Template' button. OS templates do not consume any resources such as CPU sockets, memory etc. |
Select server from dropdown menu and type in its short description. Save changes when ready. |
[edit] Client Area - VM Management
The client area interface of your virtual machine should look like the one on the screen below. As you can see, the control panel contains useful options needed for managing VPS. |
[edit] noVNC Console
noVNC console allows your clients to connect with their server in the easiest possible way. |
[edit] SPICE Console
Spice console enables you to connect with virtual machine using SPICE. Note: Your client needs to download and install client side SPICE application in order to connect with VM. |
[edit] Xterm.js Console
Xterm.js console enables you to connect to virtual machine using Xterm.js. You must update the scripts on Proxmox v2.6.0. To do so open folder: UploadOnProxmoxServer/5.2-10 and upload content on all your proxmox servers. |
[edit] Client Area - Additional Tools
[edit] Reinstall
The 'Reinstall' section is divided into two parts. There are 'OS Template' and 'ISO Images' subsections. Note: The ISO images can only be used for the KVM virtualization type, while VM templates can be used either for KVM or LXC. |
Remember to gain your clients access to selected reinstallation types in the 'Client Area Features' of the product's configuration. |
[edit] Backups
[edit] Backups List
To create a single backup, proceed to 'Backups List' section and click 'Add Backup' . |
Now choose 'Compress' and 'Mode' from dropdown menus. Afterwards, press 'Confirm' button. |
To restore VM from a backup simply press 'Restore' and then click 'OK' button in a popup window to confirm. |
[edit] Backup Jobs
By pressing 'Backup Jobs' in the client area, you will be carried to a backup jobs management page. To add a new backup job press 'Add Backup Job' . |
Now, define backup time, mark days to run it and choose 'Compression' and 'Mode' from dropdown menus. Next, press 'Confirm' button. You may also enable email notifications here. |
[edit] Available Resources
NExt to the 'Backup Jobs', there is a table with information on 'Available Resources'. You will find there data on limits put on backups:
Next to the statistics there is a comfortable and easy to read progressive chart to illustrate the usage. If size is set to 'Unlimited', the chart does not show any progress. |
[edit] Graphs
Under 'Graphs' page, a client can find graph with CPU usage, memory usage, network traffic and disc I/O. They can also switch the timeline of the graphs by choosing it from a dropdown menu pointed on the following screen. |
[edit] Tasks
All changes of VM status are listed in the 'Tasks' section. Additionally, each access to the VM through SPICE console is shown here. |
[edit] Network
Under the 'Network' section, you will find 'Virtual Network' and 'Interfaces' subsections. Depending on the settings of the product (private network is used), they can also create/remove them. This feature is optional. |
[edit] Snapshots
Use snapshots to remember the contents of virtual machine memory current state. You may use them later to restore the VM settings. |
It is also possible to set up 'Snapshot Jobs' where snapshots can be created according to your preferences (daily or hourly). Click on 'New Job' in order to add a new snapshot job. |
As you complete the form, remember to fill in the 'Name' field without spaces or special characters- only capital letters and numbers are allowed here. |
[edit] Firewall
[edit] Firewall Rules
Owing to 'Firewall' page, your clients can set up firewall rules and enable security group for theirs servers from your WHMCS client area. As you can see, you can easily modify and remove previously added rules and security groups. |
You can add a firewall rule in two ways. Both of them require choosing direction, action, interface, source and destination. The first way (red) is by choosing macro from a 'Macro' dropdown field. |
Inserting a security group consists of choosing security group and interface on which group has to be used. Additionally, you can enable security group and add a comment to it. |
Additional Actions:
|
You may manage the hierarchy of rules on the list. In front of each rule, you can find its 'Position' marker. The higher the rule is on the list, the higher priority the rule has assigned.You may change the rule position using the 'Move up/down' arrows. |
[edit] Firewall Options
Under this subsection, you can easily view and edit firewall options. |
[edit] Disks (KVM only)
View and manage hard disk within defined limits, add new one or remove additional disks if you wish. |
[edit] IP Manager Integration
Owing to the integration with IP Manager For WHMCS, you are able to easily create subnets with IP addresses, and assign them to the desired products. By activating the IP Manager submodule, settings concerning IP addresses such as 'Configurable Options' and 'Default Options' will be ignored by Proxmox VPS. |
3. Afterward, create a new configuration, and assign the previously created subnet to it. Note: Multiple subnets can be assigned to a single configuration. 4. Now, link the configuration with Proxmox VPS product via a product, server or configurable option. |
4. When Proxmox starts creating a virtual machine, it retrieves the assigned IP address to the service and assigns it directly to the virtual machine. It is possible to add VLAN Tag Custom Filed in the very same way as the "MAC Address" field. |
[edit] Importing VM
Our module allows you to easily import VM into your cloud product. To do so, press 'Import Virtual Machine' as shown on the following screen. |
Afterwards, choose the preferred virtual machine from the dropdown menu and complete the 'Password' field.. Confirm importing through pressing 'Confirm' button. |
[edit] Configurable Options
When you successfully set up a product, your clients can order it by choosing from the default configurable options. Note! If automatically generated configurable options do not seem to fulfill your clients needs, you can edit them using this guide. |
[edit] Management of Billing
When you combine Proxmox Cloud VPS For WHMCS with Advanced Billing For WHMCS, you will be able to set up additional billing options. Module allows you to charge your customers basing on the server resources used by them. |
With Advanced Billing For WHMCS module, you can also display your customers current server resource usage and their cost. |
[edit] Tips
1. Operations performed on the virtual servers are not executed immediately. Give your Proxmox Virtual Environment some time for processing the request and execution of operation. |
2. Multiple physical Proxmox servers can be joined into one cluster. When they are joined into one cluster, you can access all of them by connecting to any of them. |
3. OS Templates are not automatically downloaded while configuring a product. For each virtualization type, templates are downloaded from the Proxmox server depending on which one of them they are generated for. |
4. To name the location accordingly to your needs, within the module change the lang into:
$_LANG['node_X']='Your friendly name for node_X'; |
5. When PAM authentication is used it is necessary to create a client first in order to change the password correctly. Read more about it here. |
6. As this module supports templates system, any changes made in the module's templates files will be saved after the upgrade process. |
7. If you currently use the module in the 2.3.2 version or previous, and would like to migrate to Proxmox VE V5.X, you need to update the files on your Proxmox server to the new version from the 'UploadOnProxmoxServer' folder. |
8. You can use the 'IPSet IP Filter' option for firewall to prevent IP spoofing. Click here to read more about IP Sets. |
9. 'Minimum Network Rate Limit' option allows you to change the previously entered 'Network Rate Limit' value to a new one if the current 'Bandwidth Limit' is already exceeded. Note that the 'Bandwidth Limit' can also be used for WHMCS overage billing calculation as described here. |
10. Configuring 'Default User' per template. Move to 'Proxmox Addon' → 'Servers' → 'Server Details' → 'Templates' → 'Create/Edit Template'. You may assign a default user to a single template, that user will be automatically assigned to the newly created VM. |
11. Creating a VM without any CPU limits. In the module settings, under 'Server Limits', set up 'CPU Limit' to: 0-1. Next, make sure that all values under 'CPU Priority' section are cleared. |
12. SDN Support: The module supports SDN private network type. It is possible to create virtual networks (vnets) at datacenter level thanks to the Software Defined Network (SDN). In the module, the whole configuration of SDN is located in 'Module Settings' → 'Private Network' section. There you will find dedicated options, these are:
|
13. Some sections of the Proxmox Addon, such as 'Scheduled Backup Templates', 'Firewall Templates' and 'Operating Systems Groups' are only applicable for Proxmox VE VPS For WHMCS. Those features do not provide any functionality for Proxmox VE Cloud VPS For WHMCS. |
[edit] Update Instructions
1. Essential guidance through the process of updating the module is offered here. Ensure successful completion of the module update by carefully following each step, thereby preventing data loss or any unforeseen issues. |
2. To upgrade the module from Proxmox Cloud For WHMCS to Proxmox VE Cloud VPS For WHMCS correctly, you need to follow these steps:
your_whmcs/modules/servers/proxmoxCloud
your_whmcs/modules/servers/proxmoxCloud/cron/cron.php
5-minute interval suggested for: php -q your_whmcs/modules/addons/proxmoxAddon/cron/cron.php queue php -q your_whmcs/modules/addons/proxmoxAddon/cron/cron.php update-server-usage 1-hour interval suggested for: php -q your_whmcs/modules/addons/proxmoxAddon/cron/cron.php rrddata
Important! Please remember to reissue the licence in the client area after uploading new files to the main WHMCS directory.
|
[edit] Upgrade Guide
Seeking a solution that offers greater flexibility, customization tailored to your precise needs, and unrestricted availability? There is an option that not only proves to be cost-effective in the long run but also includes prioritized support services, making it a truly valuable investment. Opt for the Open Source version of your Proxmox VE Cloud VPS For WHMCS module to unlock these benefits. Follow a comprehensive guide covering the transition process, the advantages it brings, and step-by-step instructions on what to do next after the order has been successfully finalized. |
[edit] Common Problems
1. When you have problems with connection, check whether your SELinux or firewall does not block ports. |
2. Error 'Could not create PVE2_API object' during connecting via noVNC console. Reason: User account does not have permission to access noVNC console. |
3. Error 'This connection is untrusted' during connecting via noVNC console. Reason: Your certificate is not valid. |
4. Blank page during connecting via noVNC console. Reason: You have not uploaded the additional files on the Proxmox server. |
5. Error 'Function "ssh2_connect" does not exist. Please Install SSH2 PECL before you start using the script.' Reason: You have not updated php.ini file |
6. After you have updated your Proxmox Cloud For WHMCS to Proxmox Cloud For WHMCS V2.0.0, it is always required to save your product configuration in module settings again. |
7. If you see an error: 'Invalid VLAN TAG Range' configuration or other when trying to add a new private network, please make sure you have completed all required options in Module Settings. These are: 'Network Device' → 'Private Bridge', 'VLAN TAG Range From' and 'VLAN TAG Range To'. |
8. 'OS Architecture Type ' option for LXC virtualization type is currently not supported as it not implemented in Proxmox itself. We are sorry for inconvenience. |
9. Error: "Only root can set 'serial0' config". Solution: Turn off the Xterms.js console in the product configuration. |
10. Error "Parameter verification failed. ([maxfiles] - Only root may set this option.)" Reason: User is other than "root" or server authentication is set to Proxmox VE |