Hi,

The Virtualizor Team has released Virtualizor 3.2.0 (Release Candidate)
In this version, we have some New Professional features and fixes.

Here is the complete change list:

1. [Feature]  Added Firewall for Enduser panel. Endusers can apply the firewall rules for their machines from enduser panel

2. [Feature] Added Sorting on the List Servers Page on the admin panel

3. [Feature] A New theme has been added as 2024 for Enduser panel. This theme is in Beta.

4. [Feature] Now enduser can add their recipes from enduser panel

5. [Feature] Added option to add SRV record in PDNS management

6. [Bugfix] While adding a user from an API call allowed virtualizations were not assigned properly. This is fixed.

7. [Bugfix] Reducing SWAP to 0 was causing issues. Now an error will be shown saying that SWAP can not be reduced to 0.

8. [Bugfix] Unsuspension calls from WHMCS were failing because a proper response was not coming from the API call. This is fixed.

9. [Bugfix] On rebuilding the VM, VM password was not saved properly. This is fixed.

10. [Bugfix] On reboot of Node having proxmox 8 as base node OS, VNC was not working for VMs. This is fixed.

11. [Bugfix] RTC setting was not working for proxmox KVM machines. This is fixed.

12. [Bugfix] For KVM guests if guest-agent was enabled, at that time disk usage was showing 0 in enduser panel. This is fixed.

13. [Bugfix] Backup disks were showing as orphaned disk(s). Now backup disks will not be shown in the Orphan disk list.

14. [Bugfix] In the cloud user panel (Billing enabled) after making a payment suspension notice was still shown. This is fixed.

15. [Bugfix] While migrating the VM having more than 250 IPs it resulted in failed Migration. This is fixed.

16. [Bugfix] While adding user(s) from API if the user plan ID was posted, at that time user resources were not getting applied. This is fixed.

17. [Task] Now Cloud users can select recipes while creating VM(s).

18. [Task] Improved listvs API response.

19. [Task] If a VPS plan was created for a load balancer and the destination server did not have a Professional license, at that time it was creating a VM as a normal VM. Added error check for a professional license for such a scenario.
Please let us know if you face any issues / have any suggestions. We are available on Virtualizor live chat at https://virtualizor.com

Regards,
Virtualizor Team