CentOS - Installing nginx from source

Nginx is a popular lightweight server for those who do not need the bulk and extra services that Apache may offer.

This article will look at installing Nginx from source on a CentOS Cloud Server.



At the time of writing, the latest stable version of Nginx is 0.6.34. You can check the latest versions and change logs at the main nginx site.

Building from source will allow you to have the latest available versions of Nginx. However, keep in mind that security updates will not be applied automatically.

Please see this article if you want to install Nginx with the package manager which ensures that any dependencies as well as security updates are installed as needed.


As we are not using the package manager to install nginx, we need to take care of some dependencies.

Not many are needed and include pcre-devel zlib-devel and openssl-devel packages.

sudo yum install pcre-devel zlib-devel openssl-devel


Now we can download the source code.

Create a 'sources' directory (you can download it anywhere you want to):

mkdir ~/sources

Now move into the folder:

cd ~/sources/

And then download the source code:

wget http://sysoev.ru/nginx/nginx-0.6.34.tar.gz


Unpack the downloaded tar file and move into the newly created directory:

tar -zxvf nginx-0.6.34.tar.gz
cd nginx-0.6.34/


There are quite a few compile time options that are available to use.

Have a look at the Install Options page of the Nginx wiki for full details.

We're going to use just two options to customize the install. The first of which is:


By default, nginx will be installed in /usr/local/nginx which, although a good place, does mean the main Nginx binary will be found in /usr/local/nginx/sbin/nginx.

Not a location we are likely to find in our default search paths. So instead of adding new directories to our path (which may cause errors later on) we simply define where to put the binary.

The second option is:


Probably self explanatory, but this will enable the SSL module to be compiled so we can parse https requests.


Let's go ahead and compile Nginx using those two options:

./configure --sbin-path=/usr/local/sbin --with-http_ssl_module

There will be a nice summary at the end of the compile which includes such items as:

nginx path prefix: "/usr/local/nginx"
nginx binary file: "/usr/local/sbin"
nginx configuration file: "/usr/local/nginx/conf/nginx.conf"

Keep a note of the output as it does contain some useful paths and locations for various files.


Ok, let's go ahead and 'make' and then 'make install':

sudo make install


Done. We can test the install by starting Nginx:

sudo /usr/local/sbin/nginx

and navigating to our Cloud Server IP address (assuming you have no other server running):

You will be greeted with the standard welcome page:



If you have used Apache or some other web server (or even installing Nginx via a package manager), you may be used to using a script to start and stop it such as you might find in '/etc/init.d/'.

Unfortunately, compiling from source does not create a script like that (we will create an init script in the next article or two).

You may have noticed that one of the paths noted in the compile summary was:

nginx pid file: "/usr/local/nginx/logs/nginx.pid"

Let's make use of that to stop Nginx:

sudo kill `cat /usr/local/nginx/logs/nginx.pid`

That will use the output of the pid file to kill the Nginx process - note the use of backticks (`) and not single quotes (') in the command.


Although quite detailed, we have installed the latest stable version of Nginx from source and compiled it with some custom options to make life slightly easier.

We also know how to start and stop Nginx by hand.

As mentioned, the next couple of articles will deal with learning how to create an init script so we have more control over Nginx.

Once done, we will then look at configuring Nginx, setting up vhosts and proxying to a backend (such as a cluster of mongrels).

© 2015 Rackspace US, Inc.

Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License

See license specifics and DISCLAIMER