Nginx Linux installation and deployment detailed tutorial

1. Introduction to Nginx

Nginx is a web server that can also be used for load balancing and reverse proxy. Currently, the most commonly used is load balancing. I will not introduce the specific introduction. There are many Baidu ones. Let's go directly to the installation steps

2. Nginx Installation

1. Download Nginx and related components

The Linux system is Centos 6.5 64-bit. I directly switched to the root user to install

Enter the user directory to download the program

Download related components

[root@localhost src]# wget http://nginx.org/download/nginx-1.10.2.tar.gz
Omit installation content...
[root@localhost src]# wget http://www.openssl.org/source/openssl-fips-2.0.10.tar.gz
Omit installation content...
[root@localhost src]# wget http://zlib.net/zlib-1.2.11.tar.gz
Omit installation content...
[root@localhost src]# wget ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre-8.40.tar.gz
Omit installation content...

Install the C++ compiler environment. If it is already installed, you can skip this step.

[root@localhost src]# yum install gcc-c++
Omit installation content...
There will be a confirmation prompt. Enter y and press Enter. Is this ok [y/N]: y
Omit installation content...

2. Install Nginx and related components

openssl installation

[root@localhost src]# tar zxvf openssl-fips-2.0.10.tar.gz
Omit installation content...
[root@localhost src]# cd openssl-fips-2.0.10
[root@localhost openssl-fips-2.0.10]# ./config && make && make install
Omit installation content...

pcre installation

[root@localhost src]# tar zxvf pcre-8.40.tar.gz
Omit installation content...
[root@localhost src]# cd pcre-8.40
[root@localhost pcre-8.40]# ./configure && make && make install
Omit installation content...

zlib installation

[root@localhost src]# tar zxvf zlib-1.2.11.tar.gz
Omit installation content...
[root@localhost src]# cd zlib-1.2.11
[root@localhost zlib-1.2.11]# ./configure && make && make install
Omit installation content...

nginx installation

[root@localhost src]# tar zxvf nginx-1.10.2.tar.gz
Omit installation content...
[root@localhost src]# cd nginx-1.10.2
[root@localhost nginx-1.10.2]# ./configure && make && make install
Omit installation content...

3. Start Nginx

First find out where nginx is installed

Enter the nginx directory and start it

An error message is reported: error while loading shared libraries: libpcre.so.1: cannot open shared object file: No such file or directory. Solve it as follows

1. Use the whereis libpcre.so.1 command to find where libpcre.so.1 is. 2. Use the ln -s /usr/local/lib/libpcre.so.1 /lib64 command to make a soft link. 3. Start Nginx with sbin/nginx
4. Use ps -aux | grep nginx to check the status [root@localhost nginx]# whereis libpcre.so.1 [root@localhost nginx]# ln -s /usr/local/lib/libpcre.so.1 /lib64 [root@localhost nginx]# sbin/nginx [root@localhost nginx]# ps -aux | grep nginx 

Enter the graphical interface of the Linux system, open the browser and enter localhost to see the following picture, indicating that nginx has been successfully started

Basic operations of nginx

Start [root@localhost ~]# /usr/local/nginx/sbin/nginx
Stop/restart [root@localhost ~]# /usr/local/nginx/sbin/nginx -s stop (quit, reload)
Command help [root@localhost ~]# /usr/local/nginx/sbin/nginx -h
Verify the configuration file [root@localhost ~]# /usr/local/nginx/sbin/nginx -t
Configuration file[root@localhost ~]# vim /usr/local/nginx/conf/nginx.conf

4. Simple configuration of Nginx

Open the nginx configuration file located in the conf folder under the nginx directory

A brief introduction to vim syntax

By default, vim cannot be entered after it is opened, and keys are required to operate, as follows:
Start editing: Press "i" or "Insert" to exit editing: "Esc" to exit vim: ":q"
Save vim: “:w”
Save and exit vim: “:wq”
Exit vim without saving: “:q!”

"#" represents a comment. The most important thing is that the server{} block represents each web site. For detailed configuration, please refer to my other configuration article. Here we will temporarily set up three sites

Use different ports 80, 81, and 82 respectively to save, exit, and restart nginx

5. Enable external network access

In Linux system, there is a firewall Iptables that manages all ports by default. Only the default remote connection port 22 is enabled and all others are closed. The port 80 we set above is also closed, so we need to open the application port first.

Method 1: Directly turn off the firewall. This has better performance but poorer security. This method can be used if there is a front-end firewall.

Disable the firewall [root@localhost ~]# service iptables stop
Turn off the automatic startup firewall [root@localhost ~]# chkconfig iptables off
[root@localhost ~]# chkconfig --list|grep ipt

The following are other firewall operation commands

Method 2: Add the open port to the firewall whitelist. This method is safer but has relatively poor performance.

Edit the firewall whitelist [root@localhost ~]# vim /etc/sysconfig/iptables
Add the following line of code -A INPUT -p tcp -m state -- state NEW -m tcp --dport 80 -j ACCEPT
Save and exit, restart the firewall [root@localhost ~]# service iptables restart

Linux configuration is complete. Use another computer instead of the one where nginx is installed. I use Windows system. Configure the host and configure domain name redirection in hosts under "C:\Windows\System32\drivers\etc".

10.11.13.22 nginx.test.com nginx.test1.com nginx.test2.com

Then cmd ping to see if the domain name is correctly pointing to the IP.

After pointing correctly, use telnet to check port 80 to see if you can communicate with the port (if telnet prompts that there is no such command, the client is not installed. Install it in the Enable or Disable Windows function and then operate)

The following interface is obtained, indicating successful communication

Open the browser in this Windows system and enter nginx.test.com to get the following result, which means that the external network access is successful.

If you still enable the firewall and just set the enabled port, then we will find that port 81 is inaccessible because I have not added it to the whitelist.

At this point, the Nginx server prototype deployment is complete.

6. Nginx load balancing configuration

Nginx combines reverse proxy and load balancing in one, which can be achieved by modifying the configuration file

First, we open the configuration file

[root@localhost nginx]# vim conf/nginx.conf

Each server is a virtual host, we have one used as a web server

listen 80; represents listening on port 80 server_name xxx.com; represents the domain name accessed from the external network location / {}; represents a filter, / matches all requests. We can also define different filters according to our own situation, such as making exclusive filters for static files js, css, and image root html; represents the root directory of the site index index.html; represents the default homepage

After the configuration is completed, we can access the site by entering the domain name.

The load balancing function often distributes to multiple backend servers after receiving a request, so we need the upstream{} block to use it together

upstream xxx{}; The upstream module names a backend server group. The group name must be the domain name of the backend server site. Multiple server IPs and ports can be written inside. Jump rules and weights can also be set. ip_hash; represents the use of IP addresses to allocate jump backend servers. The same IP request will access the same backend server each time. server; represents the backend server address server{}; The server module is still the part that receives external requests. server_name; represents the domain name for external network access location / {}; also represents the filter, which is used to formulate different operations for different requests. proxy_pass; represents the backend server group name. This group name must be the domain name of the backend server site. The group names of server_name and upstream{} can be inconsistent. server_name is the domain name for external network access to receive requests. The group name of upstream{} is the domain name accessed by the site when jumping to the backend server.

Configure the Windows host to point the domain name aaa.test.com we want to access to Linux

Because of limited hardware, I use IIS in Windows as the backend server of Nginx, so I configure the site domain name of IIS

Open cmd and ping aaa.test.com again. It is indeed pointing to the Linux system. Open the browser and enter aaa.test.com. The bbb site will be displayed, which means the load is successful.

The load function of Nginx has been configured. This is just a simple setting. There are still many detailed adjustments in the production environment, which will be gradually added later. My level is limited. If there is anything wrong, I hope you can give me some guidance. Thank you.

This is the end of this article about the detailed tutorial on Nginx Linux installation and deployment. For more relevant Nginx Linux installation and deployment content, please search 123WORDPRESS.COM's previous articles or continue to browse the following related articles. I hope everyone will support 123WORDPRESS.COM in the future!