Virtualizor Blog

Hi,

We have updated WHMCS module.

[Fix] On some server having latest jquery was causing issue for loading Virtualizor enduser panel on WHMCS client area. This is fixed.

Please update the module from the following link :

https://www.virtualizor.com/docs/billing/whmcs-module/

Let us know if you find any issues/bug. We will be happy to help you.

Regards,
Virtualizor Team

Hi,

We have updated WHMCS module to create Reseller Account.

[Fix] Cloud account was not getting created with custom reseller name. This is fixed.

[Feature] Now Cloud users create using Reseller Account module will be able to create / Manage the VMs from WHMCS client area.

Please update the module from the following link :

https://www.virtualizor.com/docs/billing/whmcs-module-to-create-reseller-accounts

Let us know if you find any issues/bug. We will be happy to help you.

Regard,
Virtualizor Team.

Hi,

We have updated the Blesta module.

[Fix] Module was giving warning on PHP 7+, this is fixed now.

We recommend all Virtualizor Blesta module users to update the module.

Here is the link for download the latest version of Blesta module :

https://www.virtualizor.com/docs/billing/blesta-module-v2/#download

Regards,
Virtualizor Team

Hi,

The Virtualizor Team has released Virtualizor 3.0.0 (Patch 6) (Stable)

[Bugfix] Backups from enduser was not getting deleted. This is fixed.

[Bugfix] Backup was listed even if the backup for that VM/CT was not present in the directory. This is fixed.

To check complete list of change log please go through the following link :

Virtualizor 3.0.0 Launched

Regards,
Virtualizor Team

Hi,

The Virtualizor Team has released Virtualizor 3.0.0 (Patch 6) (Release Candidate)

[Bugfix] Backups from enduser was not getting deleted. This is fixed.

[Bugfix] Backup was listed even if the backup for that VM/CT was not present in the directory. This is fixed.

To check complete list of change log please go through the following link :

Virtualizor 3.0.0 Launched

Regards,
Virtualizor Team

Over the years, We’ve encountered many questions on how to correctly configure our Linux hosts to sync time to our enterprise NTP Servers.

So, We thought why not create an article that outlines in the simplest form possible the correct way to configure the NTP Client to synchronize with NTP Servers.

Sync CentOS with NTP Time Servers

First of all, we need to install the ntpd and ntpdate clients on our Linux host. I’m using CentOS, but it’s the same in Ubuntu and so forth.

# yum install ntp ntpdate

# systemctl start ntpd

# systemctl enable ntpd

# systemctl status ntpd

Now let’s run the following command to configure the NTP Servers.

# ntpdate -u -s 0.centos.pool.ntp.org 1.centos.pool.ntp.org 2.centos.pool.ntp.org

What we’re doing is telling the ntpdate to use an unprivileged port for outgoing packets with the -u switch and to write logging output to the system syslog facility using the -s switch.

Next let’s restart the ntpd daemon.

# systemctl restart ntpd

Now let’s check if NTP synchronization is enabled and running.

# timedatectl

And for the last, we will set the hardware clock to the current system time using the -w switch.

# hwclock -w

Congratulations! You’ve now successfully set your NTP client on CentOS.

Hi,

The Virtualizor Team has released Virtualizor 3.0.0 (Patch 5) (Release Candidate)

[Bugfix] On Xenserver minutely cron was not updating the bandwidth. This is fixed.

To check complete list of change log please go through the following link :

Virtualizor 3.0.0 Launched

Regards,
Virtualizor Team

Hi,

The Virtualizor Team has released Virtualizor 3.0.0 (Patch 3) (Release Candidate)

This version includes minor fixes.

Regards,
Virtualizor Team.

Hi,

The Virtualizor Team has released Virtualizor 3.0.0 (Patch 2) (Stable candidate)

Fixes in this version are listed below :

[Bugfix] On some KVM nodes, VM(s) were not able to start if cpu model was set as host-passthrough. It was giving error while starting the VM ” ERROR – unrecognized feature host-cache-info”. This is fixed.
NOTE: To start the VM which faced this issue, please edit the VM and start it.

To check complete list of change log please go through the following link :

Virtualizor 3.0.0 Launched

Regards,
Virtualizor Team.

Hi,

The Virtualizor Team has released Virtualizor 3.0.0 (Patch 1) (Stable candidate)

1. [Bugfix] On LXC servers, user were able to reboot the node from LXC container. This is fixed.
2. [Bigfix] Backup rotation was not deleting the old backups. This is fixed. This issue was introduced in 3.0.0
3. [Bugfix] When user login to enduser panel they were getting emails for unsuspension. This is fixed. This issue was introduced in 3.0.0

For more details please go through the following link:

Virtualizor 3.0.0 Launched

Regards,
Virtualizor Team.