I always had this in mind, but until recently had no time to look closely at implementing it. Then I saw a forum post with a sample script for generating the nginx configuration file based on Cpanel account info, and then an onslaught of visitors on a shared Cpanel server I admin slowed it to a crawl, and I was forced to delve into the innards of Cpanel. As a result of this investigation I wrote the “nginx on Cpanel” HOWTO presented below.

Installing Apache module

First of all, when nginx is used as a reverse proxy to Apache, the visitors’ IPs received by Apache are wrong – all requests to Apache come from nginx, so the main server IP will be logged.
To make Apache log the real IPs of the visitors instead of the main server IP, a special Apache module (mod_rpaf) is needed.
Download, untar, cd to the newly created directory and run this command as root:
/usr/local/apache/bin/apxs -i -c -n mod_rpaf-2.0.so mod_rpaf-2.0.c
That will install the module into the Apache module directory.

Then go to WHM, Main >> Service Configuration >> Apache Configuration > Include Editor > Pre Main Include and add this section there, replacing LIST_OF_YOUR_IPS with the list of IP addresses managed by Cpanel:

LoadModule rpaf_module modules/mod_rpaf-2.0.so 

RPAFenable On
# Enable reverse proxy add forward
RPAFproxy_ips 127.0.0.1 LIST_OF_YOUR_IPS
# which ips are forwarding requests to us
RPAFsethostname On
# let rpaf update vhost settings
# allows to have the same hostnames as in the "real"
# configuration for the forwarding Apache
RPAFheader X-Real-IP
# Allows you to change which header mod_rpaf looks
# for when trying to find the ip the that is forwarding
# our requests

Apache configuration changes

Then we need to move Apache to another port, let’s take 81 for example. You can simply edit it in the “Tweak Settings” page in WHM, replacing 0.0.0.0:80 with 0.0.0.0:81 or, doing it command line way, edit /var/cpanel/cpanel.config and change port 80 in apache_port assignment to 81:

apache_port=0.0.0.0:81

Run /usr/local/cpanel/whostmgr/bin/whostmgr2 –updatetweaksettings as advised at the top of that file.
Check /usr/local/apache/conf/httpd.conf for any occurences of port 80, and run /scripts/rebuildhttpdconf to make sure httpd.conf is up to date.

It also makes sense to reduce the number of Apache children, as nginx will take care of spoonfeeding the data to the clients connecting via the slow network links, freeing Apache children to do their backend work. Edit/usr/local/apache/conf/httpd.conf and replace prefork.c section with this (note that I used very modest values here, and your mileage may vary):

<IfModule prefork.c>
    StartServers 5
    MinSpareServers 2
    MaxSpareServers 5
    MaxClients 50
    MaxRequestsPerChild 0
</IfModule>

Run /usr/local/cpanel/bin/apache_conf_distiller –update –main to pick up the changes, and then/scripts/rebuildhttpdconf to make sure your changes are in.
Note that you will need to watch Apache extended server status at the peak load times to have an idea how many Apache children your server needs by default.

You’ll also need to update the Apache port in /etc/chkserv.d/httpd and restart chksrvd with /etc/init.d/chksrvd restart

Generating nginx config files

The final step – we have to build the nginx config file based on the domains hosted on your server.
It is done by the simple script which will generate two configuration files for nginx – main one here:/usr/local/nginx/conf/nginx.conf and the include file with all virtual hosts: /usr/local/nginx/conf/vhost.conf

#!/bin/sh

cat > "/usr/local/nginx/conf/nginx.conf" <<EOF
user  nobody;
# no need for more workers in the proxy mode
worker_processes  1;

error_log  logs/error.log info;

worker_rlimit_nofile  8192;

events {
 worker_connections  512; # increase for more busy servers
 use rtsig; # you should use epoll here for Linux kernels 2.6.x
}

http {
 server_names_hash_max_size 2048;

 include    mime.types;
 default_type  application/octet-stream;

 sendfile on;
 tcp_nopush on;
 tcp_nodelay on;

 keepalive_timeout  10;

 gzip on;
 gzip_min_length  1100;
 gzip_buffers  4 32k;
 gzip_types    text/plain text/html application/x-javascript text/xml text/css;
 ignore_invalid_headers on;

 client_header_timeout  3m;
 client_body_timeout 3m;
 send_timeout     3m;
 connection_pool_size  256;
 client_header_buffer_size 4k;
 large_client_header_buffers 4 32k;
 request_pool_size  4k;
 output_buffers   4 32k;
 postpone_output  1460;

 include "/usr/local/nginx/conf/vhost.conf";
}

EOF

/bin/cp /dev/null /usr/local/nginx/conf/vhost.conf

cd /var/cpanel/users
for USER in *; do
 for DOMAIN in `cat $USER | grep ^DNS | cut -d= -f2`; do
  IP=`cat $USER|grep ^IP|cut -d= -f2`;
  ROOT=`grep ^$USER: /etc/passwd|cut -d: -f6`;
  echo "Converting $DOMAIN for $USER";

  cat >> "/usr/local/nginx/conf/vhost.conf" <<EOF
   server {
  access_log off;

  error_log  logs/vhost-error_log warn;
  listen    80;
  server_name  $DOMAIN www.$DOMAIN;

  # uncomment location below to make nginx serve static files instead of Apache
  # !WARNING!
  # it will make the bandwidth accounting incorrect as these files won't be logged!
  #location ~* \.(gif|jpg|jpeg|png|wmv|avi|mpg|mpeg|mp4|htm|html|js|css)$ {
  # root   $ROOT/public_html;
  #}

  location / {
   client_max_body_size    10m;
   client_body_buffer_size 128k;

   proxy_send_timeout   90;
   proxy_read_timeout   90;

   proxy_buffer_size    4k;
   # you can increase proxy_buffers here to suppress "an upstream response
   #  is buffered to a temporary file" warning
   proxy_buffers     16 32k;
   proxy_busy_buffers_size 64k;
   proxy_temp_file_write_size 64k;

   proxy_connect_timeout 30s;

   proxy_redirect  http://www.$DOMAIN:81   http://www.$DOMAIN;
   proxy_redirect  http://$DOMAIN:81   http://$DOMAIN;

   proxy_pass   http://$IP:81/;

   proxy_set_header   Host   \$host;
   proxy_set_header   X-Real-IP  \$remote_addr;
   proxy_set_header   X-Forwarded-For \$proxy_add_x_forwarded_for;
  }
 }
EOF
 done
done

Run /usr/local/nginx/sbin/nginx -t to check the configuration, and then /usr/local/nginx/sbin/nginx to start nginx. You are set!

If you don’t care about the bandwidth consumed by the virtual hosts and are willing to lose the correct bandwidth calculation over the increased server performance, you can uncomment the <location> lines below the WARNING comment and watch the server picking up the speed. Beware of the two gotchas here: the sub domains most likely will not work as they have document root pointed to a different place, and as nginx doesn’t support .htaccess files for the performance reasons, they won’t be obeyed for the file types listed.

Obviously, the config file must be regenerated every time a new domain is added. The deleted and suspended domains should work just fine though.

You don’t need to download any files in order to install Fantastico!

Just SSH to your server and enter following commands (you may also copy/paste):

cd /usr/local/cpanel/whostmgr/docroot/cgi
wget -N http://files.betaservant.com/files/free/fantastico_whm_admin.tgz
tar -xzpf fantastico_whm_admin.tgz
rm -rf fantastico_whm_admin.tgz

NOW GO TO YOUR WHM -> Add-Ons (Plugins on v11.x or higher) -> Fantastico De Luxe WHM Admin (scroll down the left menu).

Follow the on screen instructions.

If you get a Source Guardian error when you go to Fantastico for the first time, just run this command:

chmod -R 0755 /usr/local/cpanel/3rdparty/etc/ixed

After the installation is complete, click on “Settings” and go through the settings. While some settings are not important, some other (marked below with an *) are essential for a proper functioning of Fantastico installations.
Language: Select the language for the admin backend AND default language for users without a language selected.
Email notifications: Enter an email address in order to receive notifications when users perform installations using Fantastico.
Master files settings (*): If you are not an advanced user who modifies the master files, leave this to “Remove”. Change this only if you know what you are doing
PHPsuexec (*): VERY ESSENTIAL!!! Changing this value will not install or de-install phpsuexec for you. It will only tell Fantastico that you have phpsuexec installed or not installed on your server. Change to “installed” if you perform installations which produce an “Internal Server Error”. Notice: Changes will not apply to existing installations! You have to re-install in order to have working installations.
Path to netPBM: Enter the full path to the netPBM binaries in order to enable Gallery installations. As long as this field has no value, your users will not be able to install Gallery.
Select Fantastico licensing and files server: If the Fantastico pages take long to load switch to the server that works best for you. Fantastico will auto-switch if connections time out.
Update preference: Select latest version (sometimes experimental) or stable version (best working).

If your users don’t see a Fantastico link in their CPanel: Go to WHM and edit the “default” Features List. Activate Fantastico.

If you are still having problems, take a look at this article

mod_pagespeed is an open-source Apache module that automatically optimizes web pages and resources on them. It does this by rewriting the resources using filters that implement web performance best practices. Webmasters and web developers can use mod_pagespeed to improve the performance of their web pages when serving content with the Apache HTTP Server.

mod_pagespeed includes several filter that optimize JavaScript, HTML and CSS stylesheets. It also includes filters for optimizing JPEG and PNG images. The filters are based on a set of best practices known to enhance web page performance. Webmasters who set up mod_pagespeed in addition to configuring proper caching and compression on their Apache distribution should expect to see an improvement in the loading time of the pages on their websites.

Sounds interesting. Mod_pagespeed is brand new, and running it with Apache on a Cpanel server is a very easy task. While you can follow the instructions mentioned here to build from source, you can also use the binary.

But then, it fails to install correctly on a Cpanel server as it requires httpd package. Still, we can extract the files from the binary and copy it over to the necessary paths to get it up and running in a few minutes time  This is how I did it on a Apache v2.2 + CPanel server running on CentOS 5.5 (32-bit):

 cd /usr/src
 wget https://dl-ssl.google.com/dl/linux/direct/mod-pagespeed-beta_current_i386.rpm

For 64 bit use this link ! 
https://dl-ssl.google.com/dl/linux/direct/mod-pagespeed-beta_current_x86_64.rpm

 mkdir mod-pagespeed
 cd mod-pagespeed
rpm2cpio ../mod-pagespeed-beta_current_i386.rpm | cpio -idmv
./etc/cron.daily/mod-pagespeed
./etc/httpd/conf.d/pagespeed.conf
./usr/lib/httpd/modules/mod_pagespeed.so
./var/mod_pagespeed/cache
./var/mod_pagespeed/files
3135 blocks
 cp ./etc/httpd/conf.d/pagespeed.conf /usr/local/apache/conf/
 cp ./usr/lib/httpd/modules/mod_pagespeed.so /usr/local/apache/modules/
 chmod 755 /usr/local/apache/modules/mod_pagespeed.so
 mkdir /var/mod_pagespeed/{cache,files} -p
 chown nobody:nobody /var/mod_pagespeed/*

Mod_pagespeed needs mod_deflate to be loaded in Apache. If it is not yet installed, you can just include the same from apache source, like: /usr/local/apache/bin/apxs -c -i /home/cpeasyapache/src/httpd-2.2.14/modules/filters/mod_deflate.c

Now, edit /usr/local/apache/conf/pagespeed.conf and change the LoadModule lines to point to these paths:

LoadModule pagespeed_module modules/mod_pagespeed.so

# Only attempt to load mod_deflate if it hasn’t been loaded already.

<IfModule !mod_deflate.c>

LoadModule deflate_module modules/mod_deflate.so

And finally, include pagespeed.conf in /usr/local/apache/conf/httpd.conf:

Include “conf/pagespeed.conf”

and then restart apache:

service httpd restart

If everything is fine, apache will start normally and as your domains begin to get hits, you will see data being written in to /var/mod_pagespeed/*. Just a reminder that this module seems to write a lot of data in apache error log. You might need to monitor the server load and i/o stats for some time to ensure that everything is stable.

NOTE: The above guide is strictly for 32-bit servers. If you are running on 64-bit, then you need the 64-bit package (.rpm).

If you didn’t stumbled upon something bizarre on eBay then have a look. It is astonishing how people post these sort of things online and even get bids, sales and reputation points.

Thank God! these sort of goods aren’t available in stores or else it would be called “the freak-shop” you can add your interesting names to the weird world using the comment section below this post.

1.) A Penis Shaped Cheeto

Hmm… strange, idiotic and even slutty, who’d purchase that, who’d want this in their home. A Cheeto shaped to man’s genital, it was sold at a price $1.25 with a few bidder, strange!

2.) A Town in Texas

I know eBay sells property, but that should be property, like a house or something. Buying or selling or even bidding for something like the complete town is shocking.

3.) An Ad Banner on Man’s Forehead

I agree with God, he is unfare, he made idiots and then made my hands to write about them. I know people adopt offbeat jobs to earn a living but something like selling your body parts as advertising spots is far more than insanity.

The price he offered for his forehead was $322, amazing, weird, bizarre, idiotic, stupid, entrepreneur, i have no words. I just hope people reading this don’t get excited about the whole thing and start selling advertising spots on body.

4.) The Meaning of Life

Yeah! the world is full of distracted souls and thousands of books, literally thousands of books are published every year worldwide of which many tell the same thing “Meaning of Life” but on eBay a guy sold video session and paper course about the same for $3.26.

5.) Wisdom Teeth

Woah! now that made me creek, yuck! who’d break his wisdom teeth for money and even if that was the result of an accident! who would be so dumb to see profit in those broken calcium bits.

Albert Einstein noted correctly, “Two things in this universe are infinite the universe and human stupidity and i am not sure about the universe.”

Well, this is so true and worthy of getting quoted here.

6.) An Iron Man Mask

Iron man, yeah.. the character played by Robert Downie Jr. made a buzz in all of Hollywood but eBay wasn’t left behind either. A man who got the souvenir from Iron Man Sets — The Iron Man Mask — decided to list it on eBay at a starting price of $32.5 and the bid got this guy a whopping 325%.

It is amazing how a hairbrush of some hot top pop start can make a fortune on eBay.

Though craziness is not just determined by these activities, it is the inner drive that makes people come up with these amazing and bizarre listing.

You can see the whole listings on eBay, the sold may have been removed.

Here it’s goes:

- Create repo
# cd /etc/yum.repos.d
# vim rusia-repo.repo

- and paste this

[rusia-repo]
name=CentOS-$releasever – rusia packages for $basearch
#baseurl=file:///raid/RH/CentOS/$releasever/local/$basearch
baseurl=http://centos.alt.ru/pub/repository/centos/5/i386/
enabled=1
gpgcheck=0
protect=1

- Enable EPEL repo
# rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/$(uname -m)/epel-release-5-3.noarch.rpm

- Install nginx and php-fpm

# yum install nginx php-fpm

- go to nginx configuration file: “/usr/local/nginx/conf/nginx.conf” , and add  the php configuration

location ~ \.php$ {
root /usr/share/nginx/html; # itmena the root of the coument are located on

/usr/share/nginx/html
fastcgi_pass 127.0.0.1:9000;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME /usr/share/nginx/html$fastcgi_script_name;
include fastcgi_params;
}

- Go to /usr/share/nginx/html and create php files
# vi index.php
<?php phpinfo(); ?>

- Start the nginx and php-fpm
# service php-fpm start
# service nginx start

You can go to your server domain / ip address to see the phpinfo files

Source : Here