As a website owner you would definitely think of getting some additional revenue from it. Your site is doing well for your products, now you want to have some extra earning from it. How to achieve this ?
Google AdSence can be the answer for your question.

An advertiser sign up with Google for AdWords system and creates one or more advertisements that they want to pay to have appear either on Google’s search result pages or on “content pages”. Those content pages are Web sites run by individuals and organizations that include AdSense.
Here advertisers don’t have to pay for their adverts show up on either Google or separate content sites, but instead pay when the ads are clicked by customers, what we call “pay per click” or PPC. A percentage of the amount that the company pays Google for displaying the ad is then shared with the AdSense-enabled web site owner.
Suppose an advertiser is wiling to pays $1.00 for a visitor to their through AdWords, then Google will pay you certain amount (certain percentage : Google haven’t specified it yet ).

Signing up Google AdSense can be considered as an fast an easy way to earn money by displaying relevant Google ads on your site.
All displayed ads are related to what your visitors are looking for on your site — or matched to the characteristics and interests of the visitors your content attracts — you’ll finally have a way to both monetize and enhance your content pages and will earn if they click on them. For getting a good income your site must have a huge traffic and your visitors should clicks on these adverts.
You have choice for locating these adverts within your page by placing special AdSense code into your page, you can also specify color and sizes also for ads.
It is the simple way for earning without negotiating with your advertisers, no more bills for anyone and no headache for payments.

Not every site is approved for AdSense program. Google has their own terms and condition.

For some reasons, you decided to move your site at new host.

Before moving to new host , plan your migration properly otherwise you may end up in a mess.
When you migrate to new host you get new DNS, new IP and new content ( if you manage for it )

Now you may think that you have migrated so why to keep any data at old server so you may put blank pages over there, keeping the old server still live.
This is most worst mistake which is usually done by webmasters which causes their new migrated site to get banned even though there is nothing wrong in it.

The reason for this is :
Since old server is still live, some Googlebots were using the old DNS/old IP and went to old serever and they received a blank page there, other Googlebots were going to new server they were using new DNS, new IP, new Contents. Due to this Google was getting two different pages at same time hence it consider it as an ” Cloaking ” and you are banned for such mistake.

How to avoid this :
*) Bring a copy of your site up at the new IP address.

*) Update your nameserver to point to the new IP address.

*) Once you see search engine spiders fetch pages from the new IP address, then be sure to take down the copy of your site at the old IP address.

*) Do not do all of the changes at the same time.

*) Make sure there are never two servers responding to requests for your domain dishing out different content.

If fantastico is installed on the server, but the fantastico icon is not present in cpanel then you will have to check 3 things on the server as,
1) Make it sure that Option fantastico is CHECKED in the feature list assigned to that account.

In order to check this, you will have to login into the root WHM and select the option called Packages >> Feature Manager and edit the feature list that is assigned to that account.
You can check which feature list is assigned to the account from edit package option in whm.
2) First check the theme that cpanel is using.

And after that please check the symbolic link to the fantastico directory is present or not.
In order to create the symbolic link, run the following command say for theme bluelagoon as
– ln -s /usr/local/cpanel/3rdparty/fantastico
/usr/local/cpanel/base/frontend/bluelagoon
3) Please check the cpanel version and If you are running cpanel version called CPANEL 10.4.0C150 or next and icon is not present in cpanel’s own themes like x, x2,xmail etc, then run the command as a root via SSH

—————-

mv /usr/local/cpanel/3rdparty/fantastico/xskin.html
/usr/local/cpanel/base/frontend/x/cells/fantastico.html

For installation of ioncube for perticular account then goto
http://www.ioncube.com/loaders.php
download it one server server where it is available. you need to do the following process on the server.
1 go to user directory and wget http://downloads.ioncube.com/loader_downloads/ioncube_loaders_lin_x86.tar.gz
2 Extract the tar file with tar -zxvf ioncube_loaders_lin_x86.tar.gz
3. change the permission chown user:user ioncube
4. then goto ioncube directory cd /home/user/ioncube and again change the ownership of all files to user:user
5.after changing the permission copy ioncube-encoded-file.php and ioncube-loader-helper.php in public_html by
cp ioncube-encoded-file.php ../public_html/
cp ioncube-loader-helper.php ../public_html/
6.then goto public_html folder of that user and again change the ownership to user:user for ioncube
7 Now ioncube is get installed you can access that using access ioncube by http://domain.com/ioncube-loader-helper.php
enjoy…..:)

While sending emails from your email address and you get the error Unrouteable address with RCPT reject. That means the problem at receivers end.

Check the following things.

1. Check the domains entry is available in userdoamins.

2. Check the domains entry is is available in localdomain

3. check the domain must having catchall address set if not then set
vi /etc/valiases/domain.com

*: username

4. also make sure that the mail folder having ownership user:mail

5 restart exim services once.

6. Now your problem will get resolved.

MX Record is an entry in a domain name database that identifies the mail server that is responsible for handling e-mail for that domain name.You can have website on one server and MX record on some another server and in that case you will have to ulter your MX entry in DNS zone for that perticular domain.

You can have multiple MX records for a same domain and it will check for MX record set with priority.
lowest number will receive mail first that is lower number will have highest priority.

1)You will have to login as a root in WHM

2)Go to the option called DNS Functions >> Edit DNS Zone

3)Select the domain from list and edit that domain
You will see the entries like
XYZ.com. 14400 MX 0 XYZ.com.
mail 14400 CNAME XYZ.com.

4)Suppose you want to change MX to point to the ip 176.199.1.90 then you will have to do the changes in MX record as
XYZ.com. 14400 MX 0 mail.XYZ.com.
mail.XYZ.com. 14400 A 176.199.1.90

5)Save the chnages and remove the entry for XYZ.com from /etc/localdomains.

6)Edit the /etc/remotedomains file - this tells Exim to not handle mail for this domain.
vi /etc/remotedomains
Add the domain name to this file.
Save the changes.

7)You can check the changes done in MX record for the domain at — http://www.dnsstuff.com/

If you are getting this error message while accessing mysql from the shell then make sure that you have done
su -
from the command prompt after that fire
mysql
even if you are getting that error message then you need to reset the mysql password you can use following steps for it

first locate your mysql’s hostname.pid file then

kill `cat /mysql-data-directory/host_name.pid`
mysqld_safe –skip-grant-tables &
mysqladmin -u root flush-privileges password “newpassword”

New password will be the password that you want to set now.

MySQL is easiest to install on Red Hat systems using the RPM packages. To install MySQL in the same directory as the RPM packages use the command:
# rpm -Uvh *.rpm

Note: You most likely need to do this as the root user. Either log in or su to root.

After MySQL is installed you need to set the root password. To do this use the following commanding changing my_password to the password you want for the root user to access MySQL.
# mysqladmin -u root password ‘my_password’

Note: If the MySQL service is not running, you may have to start it by hand before trying to set the password. It should start automatically when the computer boots. The command to start MySQL is:
# /etc/rc.d/init.d/mysqld start

You can test the MySQL installation by doing the following:

# mysql mysql (connect to mysql database)
Enter Password:
mysql> SELECT * FROM user; (grab some data out of user table)

This should return the data in the user table. Type exit to leave.

This can be done with .htaccess, visitors must input username and password before they can access the protected directory.

Step 1.
Create the file “.htaccess” with the following content under the directory you want to protect, you can specify the password in any place as long as Apache can access it.

AuthUserFile /home/account/passwd/.htpasswd
AuthGroupFile /dev/null
AuthName “Title”
AuthType Basic

Step 2.
Generate the password file “.htpasswd” under the directory /home/account/passwd/ with the following command:
# htpasswd -c .htpasswd user_name

You will be reminded to input password for the user “user_name”, this command can be called multi times to generate multi users.

Step 3.
This step may not be necessary. If there is an entry about the directory you want to protect in Apache configuration file, make sure AllowOverride has the option authconfig.

For example, when protecting Awstats pages, the Apache configuration file should be modified as following:

Options None
AllowOverride authconfig
Order allow,deny
Allow from all

Restart Apache
# /usr/local/sbin/apachectl restart

If you are not aware of my.cnf files configuration and want to use mysql server to optimize your database usage then replace this configuration file.
————————————————————————————
[mysqld]
socket = /var/lib/mysql/mysql.sock
safe-show-database
old-password=1
max_connections=500
interactive_timeout=100
wait_timeout=30
connect_timeout=30
thread_cache_size=8
key_buffer=32M
join_buffer=8M
max_allowed_packet=32M
table_cache=1024
sort_buffer=32M
record_buffer=8M
thread_cache_size=128
max_user_connections=30

thread_concurrency=4
myisam_sort_buffer_size=64M
query_cache_limit=2M
query_cache_size=32M
query_cache_type=1

old-passwords = 1

[safe_mysqld]
err-log=/var/log/mysqld.log
open_files_limit=8192

[mysqldump]
quick
max_allowed_packet=32M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer=64M
sort_buffer=64M
read_buffer=16M
write_bufer=16M

[myisamchk]
key_buffer=64M
sort_buffer=64M
read_buffer=16M
write_buffer=16M

[mysqlhotcopy]
interactive-timeout