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 :

Webuzo 2.2.0 Launched

Webuzo Team is glad to announce a new version 2.2.0 which has some cool new features and bug fixes


The Webuzo Team has released Webuzo 2.2.0
This version has some new features, minor bug fixes and API changes.

A complete list of changes:

1) Directory Privacy: Users can now password protect their directories from a simple and easy-to-use interface.Only available when Apache is the default web-server.Guide
Password Protected Directory

2) Social Media : Users can now tweet after installing, upgrading or cloning their site via Webuzo. This feature can be disabled or the default tweet text can be edited from the Webuzo Admin panel -> Settings

3) Edit Installation : Users can now Start / Stop / Restart Node.js service for their Ghost installations from Edit Installation page of that installation.

4) Added an option in Webuzo Admin Panel to enable Pre Download for all the scripts. The settings can be changed from Webuzo Admin Panel -> Settings

5) Bug Fix : On changing the License Key from the Webuzo Admin Panel, the list of scripts and categories was not updated. This is fixed now.

6) Bug Fix : Scripts added in the Top Scripts from the Webuzo Admin Panel were shown in the Enduser Panel even when those scripts were disabled. This is now fixed.

Hope you enjoy this version of Webuzo !!!

Password Protecting Directory with Webuzo

Protecting files on your website from unauthorized users can add a layer of security to your website. This can be done in various ways, one of them is using the .htaccess and .htpasswd files to accomplish the task.

Password protecting a directory on your site is actually fairly easy. Webmasters typically want to protect a directory if they have information that they want to make available only to a selected number of people.

This guide will help you to password protect your directories over the web.
Since, this feature is not available by default in Webuzo, a few tweaks and you should be all set to implement this functionality.

Oh!! it’s easy too!

The system requires two files
1) the .htaccess file
2) the .htpasswd file

Getting Started

Step 1) Enable the required modules in Apache (disabled by default in Webuzo)

Edit the file /usr/local/apps/apache/etc/httpd.conf and uncomment the following lines

LoadModule authz_user_module modules/

LoadModule authn_file_module modules/

LoadModule auth_basic_module modules/

Restart the Apache service for the changes to take effect
Root > service httpd restart

Step 2) The .htaccess file
Add the .htaccess file to the directory you wish to protect

AuthType Basic
AuthName "restricted area"
AuthUserFile /home/soft/public_html/dir_to_protect/.htpasswd
require valid-user

Replace the line /home/soft/public_html/dir_to_protect/ with the path to the directory you wish to password protect

Save the .htaccess file

Step 3) The .htpasswd file
This file is required to hold the username:password combination for the directories to be accessible.

Execute the following command to create the name:value password pair.

Root > /usr/local/apps/apache/bin/htpasswd -c /home/soft/public_html/dir_to_protect/.htpasswd testuser

Follow instructions to set the password for the same.

Access the directory from the browser and you should be prompted for a username and password.

That’s it !!! Simple eh ?

View the logs for other issues:

Support :

Demo :
Admin Panel :
Enduser Panel :