Softaculous <![CDATA[Disable Terminate module command WHMCS ?]]>
Would be a good suggestion to implement configuration about what the user can do inside the module.
Mon, 27 Apr 2015 07:09:13 GMT
<![CDATA[Hello to Everyone]]> Mon, 27 Apr 2015 06:37:32 GMT <![CDATA[Webuzo You cannot use System UserName]]>
i don't have any basic knowledge about vps before, so i just instal webuzo again and on the process i have to enter username again, but when i use my old username its said 'You cannot use System UserName', so i use another username, once installation done i logged in and found out that my files not there

i checked my files via putty and my files still there but it cannot be appeared in file manager in this new webuzo, i think its because my webuzo username is different... so how can i access my files again? how can i use my old username for login to webuzo? because with this new installation i can't gain my access to my files, please need your help. thanks  :angel:
Sun, 26 Apr 2015 22:32:35 GMT
<![CDATA[Guide - How to setup DKIM and SPF with Exim]]> 7) In Webuzo, go to "Advance DNS Setting" and for the domain you wish to send email from add a txt record exactly as you did in step 6.3.
Sun, 26 Apr 2015 20:34:41 GMT
<![CDATA[Guide - How to setup DKIM and SPF with Exim]]> - Webuzo 2.3.4
- Centos 6.5 64bit
- Exim 4.72
- A dedicated server having its own IP
(*) It should work for different setups with minor adjustments.

Detail: I couldn't find a guide detailing steps to do it and had to spend 2-3 hours on how to do it. I didn't even know what "DKIM" or "SPF" meant before my email started being rejected by GMail and I stopped receiving emails from my WordPress without me changing anything.

Please note that I'm a novice in linux and that there may surely be an easier method to do this. I'm sharing as I really like Webuzo and I believe it may help others.


1) Start an ssh session and go to /etc/exim/
(*) It's not required, but it'll help in the next few steps.

2) Generate a private and public key to sign your messages with openssl:
#openssl genrsa -out dkim.private.key 1024
(*) It works well if you get "Returned error code 0" and you see a file named "dkim.private.key" in that directory.

3) Extract the public key from the private key
#openssl rsa -in dkim.private.key -out dkim.public.key -pubout -outform PEM
(*) A new file named "dkim.private.key" will be created in this directory.

4) Open exim.conf to modify it:
    driver = smtp
    driver = smtp
    dkim_domain = ${lc:${domain:$h_from:}}
    dkim_selector = x
    dkim_private_key = /etc/exim/dkim.private.key
    dkim_canon = relaxed
(*) It allows all domains linked to this server to use DKIM and use the private key you just created. if you opt to change "dkim_selector" it'll need to be adjusted in later steps.

5) Restart Exim
(*) I go to "services" in Webuzo, but there are other options.

6) Adjust your DNS settings

6.1) If you don't have a mx record, create one:
Priority: 1
Host: @
Points to: @

6.2) Create a TXT setting specifying your SPF settings:
Host: @
txt value: v=spf1 a mx ip4:999.999.9.99 ip6:9999:9999:99:3a32:: ~all
(*) Adjust to your IPs. It's the only thing required for SPF to work.

6.3) Create a TXT setting specifying your DKIM:
Host: x._domainkey
txt value: v=DKIM1; p=<your public key>
(*) If you changed "dkim_selector" under "Host", "x" will need to be adjusted accordingly.

How to test:

Then: send an email from this address to an external email and check if both SPF and DKIM are specified correctly in the header. You should see "spf=pass" and "dkim=pass" as well as other configurations depending on which email provider you send to. Hotmail and GMail are both good to confirm these settings.
Sun, 26 Apr 2015 20:12:28 GMT
<![CDATA[There are insufficient IPs on the server]]>
still would be nice to have module debug info brought into WHMCS, and doco on logging levels :)]]>
Sun, 26 Apr 2015 18:06:00 GMT
<![CDATA[Virtualizor 2.7.2 (Multi Virtualization) Launched]]>
The Virtualizor Team has released Virtualizor 2.7.2
This version has some cool new features and some bug fixes.
The following is a list of changes in this version:

1) [Feature] With this version, Virtualizor now supports Multi Virtualization i.e. OpenVZ and KVM VMs can be created on the same node. Enabling Multi Virtualization is very simple and Virtualizor has a wizard to enable the same. Also the new WHMCS module has been launched for the same. You can read the wiki for more details :

2) [Feature] We have added new settings for KVM VPS I/O limit which can be used on VPS having a file storage. At the moment its supported only for CentOS 7 and Ubuntu 12+ Nodes.

3) [Feature] From this version onwards, the Master server will assign VPS names to VPS(s) on different slaves in a continous order. Before this version, the VPS Name would be assigned by each slave. This feature can be disabled from the Virtualizor Admin Panel -> Configuration -> Master Settings -> Disable Master VPS Name

4) [Feature] Added a setting to Enable/Disable the showing of Search forms in the Admin Panel. If enabled then the search form will be shown by default on all the pages. If disabled, the admin will need to click on the search icon to show the search form.

5) [Feature] Added a new "Site Domain" name setting. If set then email template will use the site domain instead of IP.

6) [Feature] Added the Multi Action feature in many Admin side utilities.

7) [Feature] Pagination options will now show at the top of the table as well as the bottom of the pages.

8) [Feature] We have enabled Thin LVM while adding a storage. However please do so at your own risk.

9) [Task] Added or improved Search on Login Logs, User logs, Admin Logs and IP logs wizard.

10) [Task] The API responses have been improved for the Power DNS wizard.

11) [Task] Raw Logging has been improved for migration.

12) [Task] Now Master node will sync on an hourly basis with the slave nodes to improve the syncing with Slave nodes.

13) [Task] Nginx server tokens has been turned off.

14) [Bugfix] On the List Backup Server page, search was not working. This is fixed.

15) [Bugfix] On DNS Plans page in the Admin Panel, search was not working. This is fixed.

16) [Bugfix] While migrating a XEN PV VPS, the SWAP disk was not created properly on the new migrated VPS. This is fixed now.

17) [Bugfix] The OS Template creation wizard did not work sometimes while creating a XenServer PV template. This is fixed now.

18) [Bugfix] While using XL on xen, sound hardware was set as hda causing the VPS to fail to boot. This is fixed now.

Virtualizor supports OpenVZ, Xen, XenServer and Linux-KVM on CentOS and Ubuntu and they all can be managed from the Master. We are adding more features and if you have any suggestions, do let us know. We hope you enjoy this version of Virtualizor.

The Virtualizor Team]]>
Sun, 26 Apr 2015 11:34:41 GMT
<![CDATA[There are insufficient IPs on the server]]> Sun, 26 Apr 2015 08:21:57 GMT <![CDATA[There are insufficient IPs on the server]]>
Creating VMs inside Virtualizor is fine, so I don't understand why I get this error.

How do I debug this? I've enabled module debug in WHMCS, but nothing is recorded.

What are the options for setting loglevel ? where is the logging output saved?

Suggestion for next version - add some more info to these lines:

// Log Level
$virtualizor_conf['loglevel'] = 0;  // no logging
//$virtualizor_conf['loglevel'] = 1;  // log what?
//$virtualizor_conf['loglevel'] = 2;  // log what?
//$virtualizor_conf['loglevel'] = 3;  // log what?
//$virtualizor_conf['loglevel'] = 4;  // log what?
//$virtualizor_conf['loglevel'] = 5;  // log what?

Sat, 25 Apr 2015 20:03:24 GMT
<![CDATA[Bug when switching php version]]> Sat, 25 Apr 2015 20:02:01 GMT