Open the mod_security whitelist file:
vi /usr/local/apache/conf/modsec2/whitelist.conf

Code:

SecRule REMOTE_ADDR "^111\.222\.333\.444" phase:1,nolog,allow,ctl:ruleEngine=off


Where 111.222.333.444 would be replaced with the IP address you wish to whitelist.

Cannot connect to DB, check your credentials, exiting …..
Sorry your request can not be processed now.Please contact your service provider. .

This is not a user problem, but a RVSiteBuilder problem. Check the database username and password in the config file located here:

/var/cpanel/rvglobalsoft/rvsitebuilder/var/SERVER.IP.ADDRESS.conf.php

Make sure that the username and password listed in that file match what MySQL has.

If you run the following commands, it will apply the username and password to the database.

grant all privileges on DATABASE_NAME.* to USERNAME@”localhost” identified by ‘PASSWORD’;
grant all privileges on DATABASE_NAME.* to USERNAME@”SERVER.IP.ADDRESS” identified by ‘PASSWORD’;
grant all privileges on DATABASE_NAME.* to USERNAME@”SERVER.HOSTNAME” identified by ‘PASSWORD’;

There was a bug in SpamAssassin that hit Jan 1st, 2010. All emails were getting marked with the above error in SpamAssassin, and it was adding 3.5 to the spam score, thus getting blocked by most standard spamassassin configs.

To fix this, simply run sa-update from a linux command line.

Edit the .bash_profile file of the user whose account you wish to monitor – typically: /root/.bash_profile

echo ‘ALERT – Root Shell Access on:’ `hostname` `date` `who` | mail -s “Alert: Root Access on `hostname`” email@yourdomain.com

You will then receive an email each time the selected user logs into the system via SSH. The email will provide you with their full connection string and IP so you can keep a close eye on who’s accessing a particular server with root privileges.

If that causes a site error or it doesn’t work you’re most likely using mod security 2.X. To disable mod security on version 2.X:
First you have to find the path to your whitelist file. To find this cd into your apache configuration folder. On cpanel you would run:
cd /usr/local/apache/conf
Then run:
grep whitelist *|grep modsec

This should show you the exact location of your whitelist file. If the file doesn’t exist create it using touch or vi. Once the file has been created add the following:
SecRule SERVER_NAME “yourdomain.com” phase:1,nolog,allow,ctl:ruleEngine=off
Be sure to replace yourdomain.com with the domain that you want to disable mod security on. Then save the file and restart apache.

Share IP addresses for a select set of accounts in cpanel:

Lets say you have domain1.com, domain2.com, and domain3.com on the same server and you want to keep them as individual accounts while allowing them to share an IP address.
1.) Login to the WHM and click Show IP Address Usage
2.) Find an available IP address that you would like to use and Copy it
3.) Click on Basic cPanel/WHM Setup – Main Shared Virtual Host IP – This should be your primary server IP (Write down this IP for future reference). Update this with the newly copied IP address that you’d like to use and click Save Changes
– Note this does not change any sites to this IP
4.) Click Change Multiple Sites’ IP Addresses
Locate and check the domains that should share this new IP i.e. domain1.com, domain2.com, domain3.com
5.) Click Change IPs of Selected Accounts
6.) Next to each site there should be a drop down box. Select the last option in each drop down box which should read:
0.0.0.0 (main shared IP) where 0.0.0.0 is the new IP for the sites to share
7.) Click Change IPs

You now have a group of accounts sharing the same IP in cpanel!

Important! – Once you are done Click on Basic cPanel/WHM Setup – Main Shared Virtual Host IP – replace this value with the original Main Shared Virtual Host IP and click Save Changes. If you don’t newly created accounts will receive the IP address that you just setup for a specific group.

Edit/Create the file:
/hsphere/local/var/vpopmail/etc/tcp.smtp
Add the following:

#whitelist IP addresses
$IP1:allow,RBLSMTPD=""
$IP2:allow,RBLSMTPD=""


Then: Recompile via Command Line option

cd /hsphere/local/var/vpopmail/etc/
/hsphere/shared/bin/tcprules tcp.smtp.cdb tcp.smtp.tmp < tcp.smtp



netstat -an|awk '{print $5}'|cut -d ":" -f1|sort|uniq -c|sort -n


We will post an automated method to check for an excessive number of connections and then block the IP’s if they hit a certain threshold. However, that article won’t be ready for a few days.

You cannot password protect specific files, instead you must password protect an entire folder and then any files within it are automatically password protected. For example – here’s your folder structure:

/home/user/domain-www
the domain-www is the folder you place all of your files in for people to access your site. Lets say you have a set of files that you want password protected. You would simply create another folder in the domain-www folder – lets call it protected.
Now you would have:
/home/user/domain-www/protected/ – upload all of the protected files into that folder. Then login to your control panel and choose the Protect Directories Option:

Then in the drop down box select:
/home/user/domain-www/protect
Click Load
Another form then appears with User ID and Password – then simply type in the username you want to protect the directory and the according password and click Submit.

You can repeat this as many times as you’d like to add multiple users to that directory.