Fix : Internal Server Error – Webuzo

Webuzo is a Single User Control Panel which helps users deploy Web Apps (WordPress, Joomla, Drupal, etc) or System Apps (Apache, NGINX, PHP, Java, MongoDB, etc) on their virtual machines or in the cloud.

Deploy a wide range of web applications as well as system applications from the Webuzo Library by just a click of a button or manually deploy your sites to your domains.

Users usually face the “Internal Server Error” due to negligence of permissions to the files/folders and similar issues.
Internal Server Error

Some of the solutions to fix this issue on Webuzo are as follows

Sol #1

Assumption : Webuzo User (soft) has a domain with the path “home/soft/www/public_html

In the above scenario, files/folders with the home/soft/www/public_html directory should have the owner and group set to the webuzo username i.e soft instead of root.

Execute the follow command from the terminal to fix the issues related to the permissions
Root > chown -R soft:soft /home/soft/public_html

Note : Replace “soft” by your Webuzo Username and “/home/soft/public_html” with the path to your files.

Sol #2

Webuzo requires to be installed on a minimal CentOS 5.x / 6.x or Red Hat Enterprise Linux 5.x / 6.x or Scientific Linux 5.x / 6.x (x86 or x86_64) / Ubuntu LTS machine.

Important !!!

Note : There should be no third-party tools like PHP, Apache, MySQL,etc installed on the server.

Usually, Apache installed by default on the server conflicts with Webuzo’s Apache Binary located at /usr/local/apps/apache resulting in the “Internal Server Error”.

Fix for the same will be to remove the default installation of Apache from the server and remove/install Apache using Webuzo.

Step 1) Remove default Apache service from the server
Root > yum -y remove httpd

Step 2) Remove and Install Apache by a click using Webuzo
Navigate to Webuzo Enduser Panel >> Apps >> WebServers >> Apache

Click on the “Remove” button to remove Apache >> “Return to Overview” >> Click on the “Install” button to install Apache.

Guide :

Video Tutorial :

Step 3) Restart the Apache service from the terminal for once.
Root > service httpd restart

Rare Case Scenario:
If at all your face an error like “ could not be located” while restarting the Apache service, simply remove and install Python2 from the Webuzo Enduser Panel >> Server Side Scripting >> Python2

Restart the Apache Service !!!
Root > service httpd restart

That’s It !!!

Other Issues
Invalid contents in the file .htaccess on your server can lead to Internal Server Error as well.

Check for the error logs for the particular domain in the Apache Logs directory to learn about the cause for the error!!!

Apache Logs Path : /usr/local/apps/apache/logs/

Hope this information was useful !!!

Webuzo Demo
Admin Panel :
Enduser Panel :

Webuzo Support
Support :

Heartbleed Vulnerability fix on Webuzo

Heartbleed LogoThe Heartbleed Bug is a serious vulnerability in the popular OpenSSL cryptographic software library. This weakness allows stealing the information protected, under normal conditions, by the SSL/TLS encryption used to secure the Internet. SSL/TLS provides communication security and privacy over the Internet for applications such as web, email, instant messaging (IM) and some virtual private networks (VPNs).

The Heartbleed bug allows anyone on the Internet to read the memory of the systems protected by the vulnerable versions of the OpenSSL software. This compromises the secret keys used to identify the service providers and to encrypt the traffic, the names and passwords of the users and the actual content. This allows attackers to eavesdrop on communications, steal data directly from the services and users and to impersonate services and users.

This tutorial guide users to manually upgrade their OpenSSL installation.

Step 1) Find the architecture of your server
Root > uname -i

Step 2) Stop your webserver (Apache/Nginx/Lighttpd)
For Apache
Root > service httpd stop

Step 3) Remove and Create the OpenSSL directory to download the latest packages.
Root > rm -rf /var/softaculous/apps/openssl/
Root > mkdir /var/softaculous/apps/openssl/
Root > cd /var/softaculous/apps/openssl/

Download the openssl package as per your architecture.
For 32 bit machine (x86)
Root > wget

For 64 bit machine (x86_64)
Root > wget

Step 4) Unzip the archive
For 32 bit machine (x86)
Root > unzip
Root > rm -rf

For 64 bit machine (x86_64)
Root > unzip
Root > rm -rf

Step 5) Extract the archive on the existing openssl location
Root > cd /usr/local/apps
For 32 bit machine (x86)
Root > tar -zxvf /var/softaculous/apps/openssl/openssl-x86.tar.gz

For 64 bit machine (x86_64)
Root > tar -zxvf /var/softaculous/apps/openssl/openssl-x86_64.tar.gz

Step 6) Start the webserver(Apache/Nginx/Lighttpd)
For Apache
Root > service httpd start

Step 7) Confirm your OpenSSL version
Root > /usr/local/apps/bin/openssl version

Test your server for CVE-2014-0160 !!!

We will be launching a New version of Webuzo soon which will automatically fix this issue !!!

If you still face any issues, please open a support ticket with the root details of your server and access to your Webuzo Enduser Panel, we will resolve your issues.

Support :

Source :

Get Email from your Domain to Gmail

Webuzo LogoWebuzo allows users to create email account for their domains by deploying the Email Server (Exim + Dovecot) by a click of a button. Exim and Dovecot can be installed from the Webuzo Enduser Panel >> Apps >> Utilities Category.

Quick Guide:

Users can freely create as many email accounts required for the domains added to their Webuzo Panel.

Quick Guide :

Webuzo provides SquirrelMail as the default Webmail to access emails of the accounts created from the Webuzo Enduser Panel.

Quick Guide :

Once you have created Email Accounts using the tutorials mentioned above, here is a step-wise guide to use Gmail to retrieve it via the web.

Patch For Email Issues on CentOS 6:

Step 1) Login to your Gmail account. If you don’t have a Gmail account, you can set one up here.

Step 2) Hit Settings to Add your domain email to GMAIL.
Gmail Settings

Step 3) Click on the “Account” Tab >> “Add a POP3 mail account you own.”
Add a POP3 mail account you own

Step 4) Add your email address to the popup window and click “Next Step.”
Add Email address to GMAIL

Step 5) Fill in your Username, Password, and POP Server to configure your mail box and Click “Add Account”
Configure Email Box to GMAIL

Step 6) Your decision on whether to leave a copy of retrieved message on the server will primarily depend on where you want to receive your mail. If you’re going to use Gmail as your exclusive source for email, uncheck the leave on server box.

Step 7) Confirm the settings and Hit “Finish” or “Next Step” is “Yes” is selected.
Confirm the settings to GMAIL

Simple Eh ?

Demo :
Admin Panel :
Enduser Panel :

Support :

Fixing the “Bad request: The IMAP server is reporting that plain text logins are disabled. ” error in Webuzo SquirrelMail

Squirrel MailWebuzo is ported with SquirrelMail as the default web-client to access emails.
SquirrelMail is a standards-based webmail package written in PHP. It includes built-in pure PHP support for the IMAP and SMTP protocols, and all pages render in pure HTML 4.0 (with no JavaScript required) for maximum compatibility across browsers. It has very few requirements and is very easy to configure and install. SquirrelMail has all the functionality you would want from an email client, including strong MIME support, address books, and folder manipulation.

It is deployed along with Exim – the SMTP Email Server, which can be installed by a click from the Webuzo Enduser Panel >> Apps >> Utilities Category

Guide :

Accessing SquirrelMail is as simple as a pie with Webuzo.
Guide :

Issue # 1
Error : Bad request: The IMAP server is reporting that plain text logins are disabled.
For instance you may face an error as follows while logging in to the web-client, which is forced SSL authentication.

Squirrel Mail Error

Fix for the above issue

Step 1)
Open the Dovecot Auth configuration using your favorite editor
1) SSL

vi /etc/dovecot/conf.d/10-auth.conf

Replace the line (Comment the line !!!)
ssl = yes


#ssl = yes

Save the above file !!!

Step 2)

Open the Dovecot SSL configuration using your favorite editor
1) Turn OFF SSL

vi /etc/dovecot/conf.d/10-ssl.conf

Replace the line
ssl = required


ssl = no

Save the above file !!!

Step 3)
Restart the Dovecot Service

service dovecot restart

That’s it !!! Simple enough !!!

Similar SquirrelMail issues :

Demo :
Admin Panel :
Enduser Panel :

Support :

Webuzo Email Server Fix for Mozilla Thunderbird and Outlook

Mozilla Thunderbird is a free, open source, cross-platform email, news, and chat client developed by the Mozilla Foundation and Microsoft Outlook is a personal information manager from Microsoft, available as a part of the Microsoft Office suite.

Follow the guides below to configure your email account created using Webuzo :

1) Mozilla Thunderbird

2) Microsoft Outlook

If at all you face a “550 Relay not permitted error” or “Authentication Error”, the steps below will fix them all.

Note : This Fix is applicable for CentOS 6.x

Exim Configurations
Open the Exim configuration using your favorite editor

1) auth_advertise_hosts
vi /etc/exim/exim.conf

Replace the line
auth_advertise_hosts =


auth_advertise_hosts = *

2) Enable Authenticators

Add the following right after “begin authenticators”

begin authenticators

driver = dovecot
public_name = LOGIN
server_socket = /var/run/dovecot/auth-client
# server_set_id = $auth1
server_mail_auth_condition = false

driver = dovecot
public_name = PLAIN
server_socket = /var/run/dovecot/auth-client
# server_set_id = $auth1
server_mail_auth_condition = false

Save and file and Exim is all ready to be used.

Dovecot Configurations

1) Edit the file 10-auth.conf using your favorite editor.
vi /etc/dovecot/conf.d/10-auth.conf

Replace the line
auth_mechanisms = plain


auth_mechanisms = plain login

Save the file.

2) Edit the file 10-master.conf using your favorite editor.
vi /etc/dovecot/conf.d/10-master.conf

Replace the following
unix_listener auth-userdb {
#mode = 0600
#user =
#group =


#unix_listener auth-userdb {
#mode = 0600
#user =
#group =

unix_listener auth-client {
mode = 0666

Save the file. That’s it !!!

Restart the Exim and Dovecot services

root > service dovecot restart
root > service exim restart

Support :