You can correct these IP’s simple with following:

1 ) Check the file /etc/nameserverips. It should show you something as follows:

10.1.1.1=ns1.domain.com

10.1.1.2=ns2.domain.com

Correct the entries here if the entries are not as per expectation.

2)Now open the file /var/cpanel/nameserverips.yaml.

It should display you settings as follows

—

ns1.domain.com: “10.1.1.1″: 1
count: ’1′ zones:
domain.com
ns2.domain.com: “10.1.1.2″: 1
count: ’1′
zones: domain.com

Edit the settings here as well if they are incorrect. Once done restart the cPanel service .

Now check the nameserver IP’s from WHM>> Main >> DNS Functions >> Nameserver IPs.  It should now be corrected.

1) Open the file /etc/hosts and edit the hostname entry as follows in the file (Eg: hostname= server.example.com)

# Auto-generated hostname. Please do not remove this comment.

127.0.0.1 localhost.localdomain localhost
XX.XX.XX.XX server.example.com server

XX.XX.XX.XX — servers IP.

2) Now open the file /etc/sysconfig/network and edit the hostname entry in this file:

NETWORKING=”yes”
HOSTNAME=”server.example.com”
GATEWAY=”xx.xx.xx.xx”
GATEWAYDEV=”eth0″
FORWARD_IPV4=”yes”

3) Now open the file /var/qmail/control/me  which contains the old hostname. Alter it to new hostname to make qmail identify itself  with  the new hostname.

server.example.com

4)Set the servers hostname in the plesk database with the following commands:

# mysql -u admin -p

Enter password:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 181
Server version: 5.1.50 Source distribution

Copyright (c) 2000, 2010, Oracle and/or its affiliates. All rights reserved.
This software comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to modify and redistribute it under the GPL v2 license

Type ‘help;’ or ‘\h’ for help. Type ‘\c’ to clear the current input statement.

mysql> use psa;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
mysql> update misc set val=’server.example.com’ where param=’FullHostName’;
Query OK, 0 rows affected (0.00 sec)
Rows matched: 1  Changed: 1  Warnings: 0

mysql> quit

5) Now restart Plesk  service to activate the changes:

# /etc/init.d/psa stopall

# /etc/init.d/psa stop

# /etc/init.d/psa start

Now check the servers hostname. It should now be configured with the new hostname.

DBI
connect(‘modsec:localhost’,'modsec’,…) failed: Access denied for user href=”mhtml:{CA6DED19-950C-4C5A-97F2-5C8634CBD55B}mid://00000086/!x-usc:mailto:’modsec’@'localhost’”>’modsec’@'localhost’
(using password: YES) at /etc/cron.hourly/modsecparse.pl line 19
Unable to connect to mysql database at /etc/cron.hourly/modsecparse.pl line 19.

The error occurs due to the password being mis configured in the file /etc/cron.hourly/modsecparse.pl .

You can use the following steps to sort the issue.

1) open the file /etc/cron.hourly/modsecparse.pl. You can find the following details in the file :

my $dbhost     = ‘localhost’;
my $dbuser     = ‘modsec’;
my $dbpassword = ‘somepassword’;      
my $dbname     = ‘modsec’;
my $tblname    = ‘modsec’;

check the password in the actual database for modsec.

server@root# mysql
mysql >\u mysql
mysql> select password from user where user=’modsec’;
mysql> select password(‘dbpassword’);

ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect…
Connection id:    4797
Current database: mysql

+——————————————-+
| password               |
+——————————————-+
| *8810994AD1910DDF9B31CB0DBF699C984CCFFEDC |
+——————————————-+
1 row in set (0.00 sec)

Replace the dbpassword with actual password from the file /etc/cron.hourly/modsecparse.pl .

mysql> UPDATE user SET Password=PASSWORD(‘somepassword’) WHERE User=’modsec’;

This will reset the password for the DB modsec to the original password  somepassword in the file /etc/cron.hourly/modsecparse.pl .

Once done you can just run the following command to ensure the DB is fixed !

server@root # perl -w /etc/cron.hourly/modsecparse.pl

If it runs without error the problem is sorted. :)

“There currently are no publicly-advertised Mailman mailing lists
on XX.XX.XX.XX.To visit the administrators configuration page for
an unadvertised list, open a URL similar to this one, but with a ‘/’
and the right list name appended. If you have the proper authority,
you can also create a new mailing list.”

Use the following simple fix for this:

1) Navigate to the folder /usr/local/cpanel/3rdparty/mailman/bin

root@server # cd /usr/local/cpanel/3rdparty/mailman/bin

Following command will check the permissions for the mailing lists

root@server [/usr/local/cpanel/3rdparty/mailman/bin]# ./check_perms 

It will display something as follows:

directory permissions must be 02775: /usr/local/cpanel/3rdparty/mailman/archives/private/XX_domain.com/attachments/20101005/59ebfce0
Problems found: 1499
XX_domain.com : mailing list name

Either manually you can assign the permission as 02775 for the respective contents or simply fire following command to fix the errors:

root@server [/usr/local/cpanel/3rdparty/mailman/bin]# ./check_perms -f

This should now fix all the permissions. The mailing lists will again be functional on the new server.

Following are the steps to install SSL for a domain on ubuntu server.

A) Create CSR and Key files:

1) Navigate to the folder/etc/ssl/private

# cd /etc/ssl/private

2) Let us create a private key for the SSL specifically of 2048 bits.

# openssl genrsa -des3 -out dns.server.com.key 2048     [OR openssl genrsa -out dns.server.com.key 2048 (without des3 encryption)]

3)Lets create CSR (Certificate Signing Request ) with the above created key.

# openssl req -new -key dns.server.com.key -out /etc/ssl/certs/dns.server.com.csr

Use the above CSR to get the cert from the CA.

Once you get the certificate from the CA follow the following steps to install the SSL for the domain on the server.

B) Enabling the certificate for the domain:

1)Add the CA bundle for the domain in the file /etc/ssl/certs/ca-certificates.crt .

2)Open the file  /etc/apache2/sites-available/default. Check all the configurations are correct.

3)Open the file  /etc/apache2/sites-available/default-ssl add the entries for the .crt and .key file:

SSLEngine on
SSLCertificateFile    /etc/ssl/certs/dns.server.com.crt
SSLCertificateKeyFile /etc/ssl/private/dns.server.com.key

4) Now issue following command to enable SSL module on the server

# a2ensite ssl OR  a2ensite default- ssl

5)Once done restart the apache service on the server.

#/etc/init.d/apache2 restart

You should now be able to access the domain with https.

Check if the following files are existing on the server:

/etc/binddisable
/etc/nameddisable
/etc/dnsdisable

If all the above files or any of them exists on the server , please remove the files. Once done run the following command on the server.

[root@server~]# /scripts/fixndc

Once done should sort the problem on the server .

Issue following command to rebuild the file on the server:

[root@server~]# /scripts/updateuserdomains

That’s it. You can now view the list of domains in this file.

1) Login to the server as root.

2) Navigate to the folder /usr/share/fonts/.

[root@server~] # cd /usr/share/fonts/

3)Now add a new folder for the TTF fonts.

[root@server fonts]# mkdir TTF-Fonts

4) If you have the fonts located on the server you can copy them to this TTF-Fonts Folder or you can simply download them in this folder via wget.

5)Now run following commands on the server for making the fonts available on the server.

[root@server~]# mkfontdir  /usr/share/fonts/TTF-fonts

Above command will add the file fonts.dir to the new fonts folder.

Issue following command to add the new fonts path on the server.

[root@server~]# chkfontpath -a /usr/share/fonts/TTF-fonts

Thats it! You can now use the newly added fonts on the server.

Data in MySQL is stored in files (or memory) using a variety of different techniques. Each of these techniques employ different storage mechanisms, indexing facilities, locking levels and ultimately provide a range of different functions and capabilities. By choosing a different technique you can gain additional speed or functionality benefits that will improve the overall functionality of your application.

You can configure the mysql database to use Innodb Storage engine . Just follow following simple steps for this.

1) Open your file /etc/my.cnf.

2) Comment the line

skip-inndob

3)Add:

default-table-type=innodb

4)Now save the file and restart the mysql service on the server.

5) Now check if the engine has changed with the command:

[root@server~]# mysql

Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 1
Server version: 5.0.92-community MySQL Community Edition (GPL)

Type ‘help;’ or ‘\h’ for help. Type ‘\c’ to clear the current input statement.

mysql> show engines;
+————+———+—————————————————————-+
| Engine     | Support | Comment                                                        |
+————+———+—————————————————————-+
| MyISAM     | YES     | Default engine as of MySQL 3.23 with great performance         |
| MEMORY     | YES     | Hash based, stored in memory, useful for temporary tables      |
| InnoDB     | DEFAULT | Supports transactions, row-level locking, and foreign keys     |
| BerkeleyDB | NO      | Supports transactions and page-level locking                   |

This should now change the storage engine for mysql on the server.

RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}

This will help you to redirect all the http URL’s in the domain to https.