This page only show history update item Proxmox VPS For WHMCS.
Total
16/11/2024 : We've added a wallet feature that saves you up to 25% >> See detail
Changelog
Support
Blog
Membership
Login/Register
![]()
Check-out
({{ cartItems }})
Cart
{{ product.name }}
USD {{ product.price }}
Language
Log Update Item Proxmox VPS For WHMCS
Fix license.
v3.1.0Released: Apr 1st, 2021
NEW FEATURE
- Custom Cloud-Init support - add your scripts within the addon module and select them in the product configuration as well as configurable options (KVM virtualization type)
- Option to "Create Network" when adding a new IP Address so it can be assigned directly to the ProxmoxVE "IP Config" configuration (KVM virtualization type)
- Added "Quemu Machine Type" setting to "Additional KVM Configuration" - case #1013
v3.0.1Released: Dec 18th, 2020
NEW FEATURE
- Support for Proxmox VE 6.3
- Support for the "Twenty-One" theme in WHMCS V8.1
IMPROVEMENT
- VLAN tags will be based on the subnet level when using IP Manager For WHMCS to assign IP pools - case #980
BUG FIX
- Resolved problem with creating multiple additional disks when the "Additional Disk" and "Backups On Additional Disks" options were enabled at the same time - case #959
- Solved issue with "Invalid virtualization type" errors on the list of server in Proxmox Addon that might have occurred after the module upgrade - case #960
- Fixed issues with enabling the "KVM Hardware Virtualization" setting properly - case #965
- Corrected issues with the upgrade/downgrade functionality that might have caused the "invalid format - value does not look like a valid node name" error when cloning a KVM - case #975
- Cloud-init password provided to the custom field during the order will no longer be incorrectly encoded - case #976
- A large number of selected items from the configuration of dropdowns will no longer obscure other options in WHMCS V8.0 and later - case #978
- Eliminated problems that might have caused instances being delivered to the wrong host nodes - case #973
- Fixed problem with the "Configuration file does not exist" 500 error that may have occurred in the HTTP header - case #982
- Solved issue where the IP from the incorrect node might have been assigned to the created VM by "IP Management" in Proxmox Addon - case #974
- Other minor code corrections and improvements