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.
The module supports Cloud-Init for the KVM virtualization type, and features Proxmox Addon allowing you to easily manage servers, IP addresses and clusters.

ModulesGarden is official Proxmox Solution Partner and this module is recommended by Proxmox Server Solutions GmbH.

We will guide you step by step through the whole installation and configuration process.

Note: If you are still using any of the module's previous versions prior to v3.0, follow these instructions.

The content of the package to upload should look like this.

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.
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.'
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.

This file is located in 'modules/servers/proxmoxCloudVps/license_RENAME.php'. Rename it from 'license_RENAME.php' to 'license.php'.

Enter your license key between quotation marks as presented on the following screen.
You can find your license key in our client area → 'My Products'.

These folders are available under two locations:

• your_whmcs/modules/addons/proxmoxAddon/
• your_whmcs/modules/servers/ProxmoxCloudVps/

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.

To do so, click on the 'Configure' button. Tick 'Full Administrator' and press 'Save Changes'.

Go to 'System Settings' → 'Servers' and press 'Add New Server'.

Choose 'Proxmox Cloud VPS' from a dropdown menu and press 'Save Changes'.
The last step is choosing authentication from the 'Authentication' dropdown menu.
Note: Authentication depends on the realm used by the user on a Proxmox VE server.

You can check connection with the Proxmox Virtual Environment server. To do so, simply press 'Test Connection' as shown on the screen below.

Click on 'Create a New Group'.

To create a product, click on 'Create a New Product'.

'Product Type' can be set to 'Server/VPS' but nameservers will need to be added later.
If you do not want to fill out nameservers, please select 'Shared Hosting' .

Next, click on 'Save Changes'.

Available virtualization types:

• KVM
  
• LXC
  

You can also choose how often the bandwidth usage should be calculated.
Afterwards, press 'Save Changes'.
Note: If you choose 'Auto-Node' as 'Default Node', new virtual servers will be created on the least used node.
Note 2: An advanced tool is available for you to automatically manage a node selection with the best count of resources. Read more about Load Balancer.

There are a few sections underlined that need your attention. Please, complete carefully the 'KVM Configuration' , 'Additional Disks' , 'Client Area Features' sections.
As you can see, there are more options available. Look through them and decide which ones you want to modify and adjust to your and your clients' needs.
Do not forget about the 'Network' section where you can determine a model, bridge, and rate limits of the network.
If you are going to allow your clients to manage their private networks, you have to select 'Private Bridge' and set up VLAN TAG Range.
Once you make sure that the configuration is completed, click 'Save Changes'.
Important: Keep in mind that the root password is generated automatically for KVM virtualization upon its creation and reset.
'If you want to set your own password on KVM virtualization, use the 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.
List of 'Archives' to select from can be found under 'Client Area Features'.

Firstly, complete the 'General' configuration and then proceed to the 'Main Configuration' , 'LXC Configuration' , 'Network' , and 'Client Area Features' sections.
There are more options available so you may easily modify the configuration of your products. Once you complete everything, click on the 'Save Changes' button.

Remember! This virtualization type is supported only by Proxmox VE 4.0. and later.
If you are using the previous version of a Proxmox server, you will not be able to start this virtualization.

• Define 'Private Network Model'
• Select 'Bridge' as well as 'Private Bridge' from the dropdown menus.
• Enter ranges for VLAN TAG
  

Note: Configure these three options for the KVM and LXC virtualization.
If you skip this step, clients will not be allowed to add private networks.

Note2: For SDN Private Network type please refer to Tips section, point 12.

Define backup settings in the 'Backup' section through defining 'Storage' and enabling 'Backups Routing' .
Backups routing automatically removes the oldest backup when a new backup is created and the established backup limit is reached.
Additionally, you can limit the time period for storing backups by providing the number of days into the 'Backups Storing Period' field.
Furthermore, you can define the limit of firewall rules and the interface to apply the rules to.
Finish the configuration in the 'Module Settings' tab through pressing 'Save Changes'.

Click on the 'Create Configurable Options' button.
Note: While generating 'Configurable Options', it is advisable to delete the ones you do not use, e.g. the swap option or IPv6 for the KVM virtualization.

Adjust configurable options to your needs and press 'Confirm' .
Note: Please remember that 'Custom Fields' can be edited in the next tab of the product's configuration.

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.
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.

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.
If you are using only Proxmox VE VPS, there is no need to set up the second one and the other way round.
The other ones are responsible for:

• Users synchronization - run only once
• VM recovery synchronization - optionally run every 24 hours
• VM migration synchronization - optionally run every 24 hours or just after the VM migration
• Tasks synchronization - optionally run every one hour
• VM names synchronization - run only once

Here it is also possible to turn on 'Debug Mode' if you need to register module logs.

In order to create a new product, you have to add 'Dedicated IP ' to the 'IP Addresses' list in 'Proxmox' addon module.
To do so, go to 'IP Management' and press 'New IP Addresses'.
Note: You can add IPv4, IPv6 addresses and IPv6 subnets. The process is the same for all types.

Then, depending on the selected type, provide:

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)

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.

Remember to press 'Confirm' button when ready.

The client area of a successfully created product should look similar to the one presented on the screen below.

We encourage you to refer to it for further insight into the Proxmox Proxy application.

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.
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.

curl -v https://10.10.11.48:8006

where 10.10.11.48:8006 is the node IP address.

The file can be found under the following link after you have logged in to your ModulesGarden account.

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.

ping modulesgarden.com

If everything is fine, assure that basic server security settings have been established.
You may turn off login with a password and turn on login with a key, change the SSH port, set up firewalls etc.

https://docs.docker.com/engine/install/
https://docs.docker.com/compose/install/

Then unzip the files.

cd /root/proxmox-proxy  

Note that the exact directory depends on the previous step where you uploaded te files.

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
These data will be automatically used when creating the database.

docker-compose up --build -d

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.

ip a

Note: Remember to check the IP address in your virtual machine, not in the proxyphp conatiner.

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.
The below screen shows an example with an IP address which is not the only correct possible option here.

Provide the necessary data and confirm the changes.

Remember to replace {vmip} with a valid virtual machine IP address, for example: https://192.168.8.113:8443/
When you see {"errors":["Invalid API Endpoint"]} it means that the servers correctly responds.

• 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

$ docker rmi -f $(docker images -a -q)

Press 'Add New' to manually add your script.

• Username
• Hostname
• Password

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

{$vm.id} {$vm.name} {$vm.password} {$vm.passwordHash} {$vm.ipv4Addresses} {$vm.ipv6Addresses} {$vm.ciuser} {$vm.sshkeys}

Where:

• $model variables - stands for following 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}'.
Otherwise, errors will occur.

Move to Servers → Servers List → Details → Settings, there you will find fields that are responsible for the correct SSH connection.

• SSH Host
• SSH Port
• SSH User
• SSH Password or SSH Private Key
  

You also have to select the 'Snippet Storage' to locate the Cloud-Init script in the correct catalog.

Before you start we recommend learning the details about cloud-init configuration on your Proxmox server - click here for more details.
Once you get familiar with Proxmox cloud-init proceed to the Cloud-Init group of your KVM configuration where you can enable it and set the following:

• Enable Cloud-Init
  
• 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.
  
• 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

Additionally, you can use the following commands that can be useful for debugging.

• Re-run cloud init scripts

rm -rf /var/lib/cloud/sem/* /var/lib/cloud/instance /var/lib/cloud/instances/* &&
cloud-init init  &&
cloud-init modules -m final

• Logs

cat /var/log/cloud-init.log
cat /var/log/cloud-init-output.log

At the same time, you can monitor and handle each product from your WHMCS admin area.
You can find here:

• Module Commands
• Available Resources
• Virtual Machines:
  • Import VM
  • Delete VM
  • Migrate VM
    You may enable 'Online' migration (no need to shut down the server before migration) and toggle 'Migration With Local Disks'.
• IP Addresses
• User Details

RAM details:

Assigned - RAM assigned to the server (hosting services only)

Total - full server 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 VE VPS server.

Press 'More Details' icon and you will get extended information on the selected server. See below for more details.

To view information about a VM, simply press the more info icon.

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.

• 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
  

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.

In order to convert a VM, press 'Create Template' button.

Fill out 'Description' field and press 'Confirm'.
Important: Selected VM will be destroyed in the process.

Note: VM ID range allows you to sort created VMs depending on the server they were created on.
SSH Data - fill out the SSH connection details (Host, User, Posrt, Password or Private Key) to allow to locate the IP addresses on the Proxmox server (Cloud-Init)
Snippet Storage - select the catalog where the file will be uploaded (Cloud-Init)

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.
Use the 'Export to File' button to save information in a TXT copy file.

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.

Important!: In order to create a virtual machine, you must previously add public IP addresses.
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.

• private/public address
• servers or nodes that will use them
• virtualization types (different VMs will use different IP pools)

Note: please go back to point 31 of the addon configuration to learn more details about adding IP addresses.

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.

By activating the IP Manager submodule, settings concerning IP addresses such as 'Configurable Options' and 'Default Options' will be ignored by Proxmox VPS.
Note: This integration works for LXC and KVM virtualization types.

1. Proceed to the IP Manager For WHMCS → Subnets tab in order to prepare the IP addresses subnet for Proxmox VPS For WHMCS.
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.
Note: Setting up the MAC address is optional and can be skipped.
More details about creating custom fields can be found here.

4. Now, link the configuration with Proxmox VPS product via a product, server or configurable option.
On the following screen, we have carried out the linking via a product.

It is possible to add VLAN Tag Custom Filed in the very same way as the "MAC Address" field.
The only element you need to change is the custom field name, which should be 'Tag' in this case.

Set the weight of the resource that will prioritize its selection when sorting the Nodes according to the free resources.
Note: The lowest possible weight is 1. You cannot set for example 0,5.

To learn more about nodes and their allowed limits please go back to the Clusters section of this documentation.

Define the behavior of the tool:

• On Upgrade - select action to perform:
  • None - if selected, no action will be triggered
  • Block - the upgrade process will be blocked as there are insufficient resources on the node
  • Migrate - the upgrade process will be performed after the previous migration of the VM to a server with sufficient free space
• Shutdown VM on Upgrade
• Stop VM If Shutdown Fails

Let's take exemplary weights for each resource just like presented on the screen above.

VMs Number Weight: 1,5

CPU Weight: 2 

Disk Weight: 4

RAM Weight: 2,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.

In our situation, there are four nodes created, named A, B, C, D with current resources as shown below:

Node A (Free Ram: 60%, Free CPU: 20%, Free Disk Space: 50%, Number of VMs: 5) 

Node B (Free Ram: 30%, Free CPU: 70%, Free Disk Space: 40%, Number of VMs: 10) 

Node C (Free Ram: 90%, Free CPU: 50%, Free Disk Space: 20%, Number of VMs: 20) 

Node D (Free Ram: 80%, Free CPU: 60%, Free Disk Space: 70%, Number of VMs: 15)

The next step is sorting the nodes according to each resource, by assigning them corresponding priorities from 1 to 4.
The higher the priority, the more free resources available.

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.
It will be selected by Load Balancer to create a new VM there, to migrate or upgrade an existing VM if its current node does not have sufficient resources.

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.
This is due to security measures to make sure, that in case of failure of this node, the client will still have access to the other VM server, created on another, working node.
However, if this client has VMs on every node already, all of them will be taken into account during the selection prioritization process again.

If you decide to use the 'Load Balancer' tool, define the resource weights to adjust their prioritization of nodes according to your needs.

• '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.
  This general limit may be overwritten per single node in the 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.

You can set up a three-tier notification system with separate email contents.

• Task name
• Task ID
• Client ID
• Service ID
• Product/Service information
• Domain
• Error Message
  

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'.

• 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

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.
Make sure to enable the widget in the 'Show/Hide Widgets' menu.

Find this code fragment:

<style>
    #MGProxmoxAddonWidget{
        height: 300px;
    }
</style>

and change it to include max-height: none !important;, like this:

<style>
    #MGProxmoxAddonWidget{
        height: 300px;
        max-height: none !important;
    }
</style>

Now you will be able to adjust the widget's height by editing the height: value; from the default '300px' to any value that fits your needs.

They can also view resources used and manage existing virtual machines.

Moreover, you can add 'New Virtual Network' and 'New Additional Disk' here. Confirm creation through pressing 'Confirm'.
Note: Data to be filled in may differ according to which type LXC or KVM you have chosen.

You can find information about managing your virtual servers in next section.

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.
Otherwise you will not be able to add any virtual network successfully.
If you have reached the set by the admin limit of allowed networks, the button will not be active either.
Moreover, you can also 'Edit' (1) or 'Delete' (2) existing private networks.

OS templates do not consume any resources such as CPU sockets, memory etc.
Important! When you convert server into a template, it is consumed in the process! There is no possibility to revert it back.

As you can see, the control panel contains useful options needed for managing VPS.
The module allows your customers to easily boot, stop, reboot, and shut down their VM by pressing a specific button.
Clients can also upgrade servers and access VNC, SPICE, and noVNC consoles.
Any additional tools are described in detail below.

Note: Your client needs to download and install client side SPICE application in order to connect with VM.

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.

Note: The ISO images can only be used for the KVM virtualization type, while VM templates can be used either for KVM or LXC.
Additionally the new OS password for the KVM OS reinstallation will be set based on the previous service password while for the LXC user can define it before the new installation.

Afterwards, press 'Confirm' button.

To add a new backup job press 'Add Backup Job' .

Next, press 'Confirm' button. You may also enable email notifications here.

• Backup Size: used/allowed
• Backup Files: used/allowed
  

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.
Once you have reached the limits, the option to create new backups is blocked. .

They can also switch the timeline of the graphs by choosing it from a dropdown menu pointed on the following screen.

Additionally, each access to the VM through SPICE console is shown here.

Depending on the settings of the product (private network is used), they can also create/remove them. This feature is optional.

As you can see, you can easily modify and remove previously added rules and security groups.

The first way (red) is by choosing macro from a 'Macro' dropdown field.
The second way (blue) consist of choosing protocol and filling source and destination ports out.
Additionally, you can enable rule and add a comment to it.
Press 'Confirm' to create a rule.

Additionally, you can enable security group and add a comment to it.
Click 'Confirm' to use the security group.

• 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

By activating the IP Manager submodule, settings concerning IP addresses such as 'Configurable Options' and 'Default Options' will be ignored by Proxmox VPS.
Note: This integration works for LXC and KVM virtualization types.

1. Proceed to the IP Manager For WHMCS → Subnets tab in order to prepare the IP addresses subnet for Proxmox VPS For WHMCS.
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.
Note: Setting up the MAC address is optional and can be skipped.
More details about creating custom fields can be found here.

4. Now, link the configuration with Proxmox VPS product via a product, server or configurable option.
On the following screen, we have carried out the linking via a product.

It is possible to add VLAN Tag Custom Filed in the very same way as the "MAC Address" field.
The only element you need to change is the custom field name, which should be 'Tag' in this case.

To do so, press 'Import Virtual Machine' as shown on the following screen.

Confirm importing through pressing 'Confirm' button.

Note! If automatically generated configurable options do not seem to fulfill your clients needs, you can edit them using this guide.
If you decide to set up pricing per server resource ordered, you can find instruction to proceed here.

Module allows you to charge your customers basing on the server resources used by them.

When they are joined into one cluster, you can access all of them by connecting to any of them.
While auto-node creates new VM on the server(node) with the most free resources, server-node creates VM on the server(node) which IP address it has (WHMCS's server configuration).

$_LANG['node_X']='Your friendly name for node_X';

You may assign a default user to a single template, that user will be automatically assigned to the newly created VM.

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).
To learn all the details on SDN in proxmox, please navigate to the official proxmox documentation.

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

Those features do not provide any functionality for Proxmox VE Cloud VPS For WHMCS.

Ensure successful completion of the module update by carefully following each step, thereby preventing data loss or any unforeseen issues.
Additionally, you will find a current list of supplementary actions necessary for a smooth update process there.

• Delete all old files of 'Proxmox VE Cloud For WHMCS' from:

 your_whmcs/modules/servers/proxmoxCloud 

• Delete the previous cron job:

 your_whmcs/modules/servers/proxmoxCloud/cron/cron.php 

• Add new cron jobs (A full list of cron jobs can be found here):
  

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 

• Now, upload new files of 'Proxmox Cloud VPS For WHMCS' to the main WHMCS directory.
  

Important! Please remember to reissue the licence in the client area after uploading new files to the main WHMCS directory.
If you do not do this, you will get a notification about the wrong licence, and the upgrade process will not succeed.

• Finally, proceed to the configuration of your server and change the module type to Proxmox Cloud VPS
  and the 'Module Name' to Proxmox VE Cloud VPS in the 'Module Settings' tab of your product configuration.

Opt for the Open Source version of your Proxmox VE Cloud VPS For WHMCS module to unlock these benefits.
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.

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.

Reason: User account does not have permission to access noVNC console.
Solution: Proceed to product's 'Module Settings' tab and check whether selected user permission grant right for noVNC console.
Afterwards, proceed to client's hosting and run 'Change User Role' on it.

Reason: Your certificate is not valid.
Quick Solution: Your client needs to add Proxmox address to certificate exception list.
Best Solution: Configure valid certificate.

Reason: You have not uploaded the additional files on the Proxmox server.
Solution: Open 'UploadOnProxmoxServer' and upload content of proper version on all Proxmox servers into the '/' path.

Reason: You have not updated php.ini file
Solution: After SSH2 PECL installation be sure that you have updated php.ini files for CLI and webserver.