By default, cPanel’s and WHM’s ports are closed for Virtuozzo. We will need to open them using SSH.

As root, run the following commands:

This will opens cPanel with and without SSL, and WHM with and without SSL and webmail ports.

To save the firewall changes, use the following:

To see the firewall rules, type

Problem to create a new account on cPanel VPS server.

We need to find out what Cpanel error logs shows

To resolve this: We need to raise the quotagidlimit from the resource tab on the hardware node.

The build process begins by distilling and recording Apache’s current configuration. The build time options you configured during the EasyApache setup are used to begin building the configuration.

Option modules such as mod_security are installed, and their corresponding modifications are made to the new Apache configuration file.
A new, assumedly valid Apache configuration file will exist in the configuration directory.
Directives added to the final Apache configuration file as defaults have been removed at this point.
No VirtualHost entries exist in the configuration file at this point.

The new configuration is distilled in much the same way as before; however, this time the configuration is used as the basis for creating the server’s main Apache configuration template.
New directives and values are stored.

Any directives and values held over from the previous configuration will retain their values from that configuration.
The combination of the main template and data stores will be the basis for regenerating the final configuration file.

Finally, the new Apache configuration file is generated from the template and data stores and checked for syntactical correctness.
If the new file passes the test, the process is complete.
If the file fails the syntax check, the previous Apache configuration is restored.

Reference: http://cpanel.net

SuExec is an Apache feature that gives users the ability to run CGI and SSI programs using user IDs that are different from the user ID of the calling web server. This effectively means that CGI and SSI programs will not have access to the root account or have root permissions.

To enable or disable SuExec:

1.Click on the Enable/Disable SuExec link in the Server Setup menu.
2.Click on the Enable button to enable SuExec or click on the Disable button to disable SuExec.

suEXEC is based on a setuid “wrapper” program that is called by the main Apache web server. This wrapper is called when an HTTP request is made for a CGI or SSI program that the administrator has designated to run as a userid other than that of the main server. When such a request is made, Apache provides the suEXEC wrapper with the program’s name and the user and group IDs under which the program is to execute.

WebHost Manager automatically saves a backup version of the following three files whenever they are changed:

*httpd.conf
*named.conf
*proftpd.conf or pure-ftpd.conf

You can revert to any of the previously saved versions whenever required. The restored version becomes the latest version, and does not delete other versions.

To roll back a file:

Please select a file to rollback:

Click on the Configuration File Rollback link in the Backup menu.

Click on the Back button button to review previous versions. As you change files, the Date field will update and the display area will update with the contents of the different file.
Click on the Restore button to roll back to the displayed version of the file.

WebHost Manager enables you to change your CPanel and WebHost Manager certificate automatically, without having to manually find and replace the certificate files.

Note: The CPanel certificate is used in the https://www.yourdomain.com:2083 address and the WebHost Manager certificate is used in the https://www.yourdomain.com:2087 address.

To change a certificate:

1.Click on the Change CPanel/WHM Certificate link in the SSL/TLS menu.
2.Enter the domain for the certificate in the Domain this CRT is for field.
3.Click on the Fetch button to paste the .key and .crt files for the domain into the available display spaces, if they are currently on your server. Otherwise, copy and paste the .key and .crt files into the available display areas.

Note: If you generated the certificate using WebHost Manager, the certificate files will be available.

mod_userdir Protection

Apache’s mod_userdir allows users to view their sites by entering a tilde(~) and their username as the uri on a specific host.

For example http://test.serverbuddies.com/~bud/ will bring up the user bud’s domain.

The disadvantage of this feature is that any bandwidth usage used by this site will be put on the domain it is accessed under (in this case test.serverbuddies.com). mod_userdir protection prevents this from happening.

We can disable it on specific virtual hosts (generally shared ssl hosts).

You can attempt to repair MySQL databases using WebHost Manager.

Then function checks each table for errors and tempts to fix them.

To repair a database:

Click on the Repair a Database link in the MySQL menu.
Click on the database that you want to repair in the displayed list and click on the Repair Database button.

A status list is displayed, stating which tables have been checked and the result.

To install a Port: (ImageMagick as an example)

If you do not have a source of local packages (such as a FreeBSD CD-ROM set) then it will probably be easier to use the -r option to pkg_add(1). This will cause the utility to automatically determine the correct object format and release and then fetch and install the package from an FTP site.

The example above would download the correct package and add it without any further user intervention.

pkg_info(1) is a utility that lists and describes the various packages installed.

To remove a previously installed software package, use the pkg_delete(1) utility.

We can establish a master/primary nameserver relationship at server setup level. If you do set up a primary nameserver, we need to establish a trust relationship between the two servers so that you can add all DNS entries from the primary nameserver. This saves you having to log on to multiple servers to set up various DNS entries.

To establish a trust relationship with a primary nameserver.

1.Click on the Establish A Trust Relationship With a Primary Nameserver link in the DNS Functions menu.
2.Enter the root password for the trusted nameserver in the Master Server Root Password field.

Once you have established a trust relationship with a primary nameserver, you will need to synchronize the DNS records between the primary and secondary nameservers after you have added new DNS entries.

To synchronize DNS records with the primary nameserver:

1.Click on the Synchronize DNS Records with Primary Nameserver link in the DNS Functions menu.