![\"Start](\"https:\/\/www.tecmint.com\/wp-content\/uploads\/2018\/11\/Start-and-Check-Nginx-Status.png\")
<\/a><\/p>\nStart and Check Nginx Status<\/p>\n
At this point, the Nginx web server should be up and running, you can verify the status with the netstat command<\/a>.<\/p>\n $ sudo netstat -tlpn | grep nginx<\/p>\n Check Nginx Port Status<\/p>\n If your system has a firewall enabled, you need to open port 80 and 443 to allow HTTP and HTTPS traffic respectively, through it, by running.<\/p>\n ———— On CentOS ———— ———— On Ubuntu ———— The ideal method for testing the Nginx installation and checking whether it\u2019s running and able to serve web pages is by opening a web browser and pointing to the IP of the server.<\/p>\n http:\/\/Your-IP-Address A working installation should be indicated by the following screen.<\/p>\n Check Nginx Web Page<\/p>\n Nginx\u2019s configuration files are located in the directory \/etc\/nginx and the global configuration file is located at \/etc\/nginx\/nginx.conf on both CentOS and Ubuntu.<\/p>\n Nginx is made up of modules that are controlled by various configuration options, known as directives. A directive can either be simple (in the form name and values terminated with a \ud83d\ude09 or block ( has extra instructions enclosed using {}). And a block directive which contains other directives is called a context.<\/p>\n All the directives are comprehensively explained in the Nginx documentation<\/a> in the project website. You can refer to it for more information.<\/p>\n At a foundational level, Nginx can be used to serve static content such as HTML and media files, in standalone mode, where only the default server block is used (analogous to Apache where no virtual hosts have been configured).<\/p>\n We will start by briefly explaining the configuration structure in the main configuration file.<\/p>\n $ sudo vim \/etc\/nginx\/nginx.conf<\/p>\n If you look into this Nginx configuration file, the configuration structure should appear as follows and this is referred to as the main context, which contains many other simple and block directives. All web traffic is handled in the http context.<\/p>\n user nginx; error_log \/var\/log\/nginx\/error.log warn; events { http { The following is a sample Nginx main configuration (\/etc\/nginx\/nginx.conf) file, where the http block above contains an include directive which tells Nginx where to find website configuration files (virtual host configurations).<\/p>\n Nginx Configuration File<\/p>\n user www-data; events { http { include \/etc\/nginx\/mime.types; access_log \/var\/log\/nginx\/access.log; sendfile on; include \/etc\/nginx\/conf.d\/*.conf; Note that on Ubuntu, you will also find an additional include directive (include \/etc\/nginx\/sites-enabled\/*;), where the directory \/etc\/nginx\/sites-enabled\/ stores symlinks to the websites configuration files created in \/etc\/nginx\/sites-available\/, to enable the sites. And deleting a symlink disables that particular site.<\/p>\n Based on your installation source, you\u2019ll find the default website configuration file at \/etc\/nginx\/conf.d\/default.conf (if you installed from official NGINX repository and EPEL) or \/etc\/nginx\/sites-enabled\/default (if you installed from Ubuntu repositories).<\/p>\n This is our sample default nginx server block located at \/etc\/nginx\/conf.d\/default.conf on the test system.<\/p>\n server { A brief explanation of the directives in the above configuration:<\/p>\n From a web browser, when you point to the server using the hostname localhost or its IP address, it processes the request and serves the file \/var\/www\/html\/index.html, and immediately saves the event to its access log (\/var\/log\/nginx\/access.log) with a 200 (OK) response. In case of an error (failed event), it records the message in the error log (\/var\/log\/nginx\/error.log).<\/p>\n Test Nginx Default Site<\/p>\n To learn more about logging in Nginx, you may refer to How to Configure Custom Access or Error Log Formats in Nginx<\/a>.<\/p>\n Instead of using the default log files, you can define custom log files for different web sites, as we shall look at later on, under the section \u201csetting up name-based virtual hosts (server blocks)<\/a>\u201d.<\/p>\n In order to restrict access to your website\/application or some parts of it, you can setup basic HTTP authentication<\/a>. This can be used essentially to restrict access to the whole HTTP server, individual server blocks or location blocks.<\/p>\n Start by creating a file that will store your access credentials (username\/password) by using the htpasswd utility.<\/p>\n $ yum install httpd-tools #RHEL\/CentOS As an example, let\u2019s add user admin to this list (you can add as many users as possible), where the -c option is used to specify the password file, and the -B to encrypt the password. Once you hit [Enter], you will be asked to enter the users password:<\/p>\n $ sudo htpasswd -Bc \/etc\/nginx\/conf.d\/.htpasswd admin<\/p>\n Then, let\u2019s assign the proper permissions and ownership to the password file (replace the user and group nginx with www-data on Ubuntu).<\/p>\n $ sudo chmod 640 \/etc\/nginx\/conf.d\/.htpasswd As we mentioned earlier on, you can restrict access to your webserver, a single website (using its server block) or specific directory or file. Two useful directives can be used to achieve this:<\/p>\n As an example, we will show how to password-protect the directory \/var\/www\/html\/protected.<\/p>\n server { location \/protected\/ { Now, save changes and restart Nginx service.<\/p>\n $ sudo systemctl restart nginx<\/p>\n The next time you point your browser to the above directory (http:\/\/localhost\/protected) you will be asked to enter your login credentials (username admin and the chosen password).<\/p>\n A successful login allows you to access the directory\u2019s contents, otherwise you will get a a \u201c401 Authorization Required\u201d error.<\/p>\n The server context allows multiple domains\/sites to be stored in and served from the same physical machine or virtual private server (VPS). Multiple server blocks (representing virtual hosts) can be declared within the http context for each site\/domain. Nginx decides which server processes a request based on the request header it receives.<\/p>\n We will demonstrate this concept using the following dummy domains, each located in the specified directory:<\/p>\n Next, assign the appropriate permissions on the directory for each site.<\/p>\n $ sudo chmod -R 755 \/var\/www\/html\/wearetecmint.com\/public_html Now, create a sample index.html file inside each public_html directory.<\/p>\n <html> Next, create the server block configuration files for each site inside the \/etc\/httpd\/conf.d directory.<\/p>\n $ sudo vi \/etc\/nginx\/conf.d\/wearetecmint.com.conf Add the following server block declaration in the wearetecmint.com.conf file.<\/p>\n wearetecmint.com.conf<\/p>\n server { }<\/p>\n Next, add the following server block declaration in the welovelinux.com.conf file.<\/p>\n welovelinux.com.conf<\/p>\n server { }<\/p>\n To apply the recent changes, restart the Nginx web server.<\/p>\n $ sudo systemctl restart nginx<\/p>\n and pointing your web server to the above addresses should make you see the main pages of the dummy domains.<\/p>\n http:\/\/wearetecmint.com Test Nginx Virtual Hosts Websites<\/p>\n Important: If you have SELinux enabled, its default configuration does not allow Nginx to access files outside of well-known authorized locations (such as \/etc\/nginx for configurations, \/var\/log\/nginx for logs, \/var\/www\/html for web files etc..).<\/p>\n You can handle this by either disabling SELinux, or setting the correct security context. For more information, refer to this guide: using Nginx and Nginx Plus with SELinux<\/a> on the Nginx Plus website.<\/p>\n SSL certificates help to enable secure http (HTTPS) on your site, which is essential to establishing a trusted\/secure connection between the end users and your server by encrypting the information that is transmitted to, from, or within your site.<\/p>\n We will cover how to create and install a self-signed certificate, and generate a certificate signing request (CSR) to acquire an SSL certificate from a certificate authority (CA), to use with Nginx.<\/p>\n Self-signed certificates are free to create and are practically good to go for testing purposes and for internal LAN-only services. For public-facing servers, it is highly recommended to use a certificate issued by a CA (for example Let\u2019s Encrypt<\/a>) to uphold its authenticity.<\/p>\n To create a self-signed certificate, first create a directory where your certificates will be stored.<\/p>\n $ sudo mkdir \/etc\/nginx\/ssl-certs\/<\/p>\n Then generate your self-signed certificate and the key using the openssl command line tool.<\/p>\n $ sudo openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout \/etc\/nginx\/ssl-certs\/nginx.key -out \/etc\/nginx\/ssl-certs\/nginx.crt<\/p>\n Let\u2019s briefly describe the options used in the above command:<\/p>\n Create SSL Certificate and Key for Nginx<\/p>\n Next, open your virtual host configuration file and add the following lines to a server block declaration listening on port 443. We will test with the virtual host file \/etc\/nginx\/conf.d\/wearetecmint.com.conf.<\/p>\n $ sudo vi \/etc\/nginx\/conf.d\/wearetecmint.com.conf<\/p>\n Then add the ssl directive to nginx configuration file, it should look similar to below.<\/p>\n server { ssl on; server_name wearetecmint.com; }<\/p>\n Now restart the Nginx and point your browser to the following address.<\/p>\n https:\/\/www.wearetecmint.com<\/p>\n Check Nginx SSL Website<\/p>\n If you would like to purchase an SSL certificate from a CA, you need to generate a certificate signing request (CSR) as shown.<\/p>\n $ sudo openssl req -newkey rsa:2048 -nodes -keyout \/etc\/nginx\/ssl-certs\/example.com.key -out \/etc\/nginx\/ssl-certs\/example.com.csr<\/p>\n You can also create a CSR from an existing private key.<\/p>\n $ sudo openssl req -key \/etc\/nginx\/ssl-certs\/example.com.key -new -out \/etc\/nginx\/ssl-certs\/example.com.csr<\/p>\n Then, you need to send the CSR that is generated to a CA to request the issuance of a CA-signed SSL certificate. Once you receive your certificate from the CA, you can configure it as shown above.<\/p>\n Read Also: The Ultimate Guide to Secure, Harden and Improve Performance of Nginx Web Server<\/a><\/p>\n In this article, we have explained how to install and configure Nginx; covered how to setup name-based virtual hosting with SSL to secure data transmissions between the web server and a client.<\/p>\n If you experienced any setbacks during your nginx installation\/configuration process or have any questions or comments, use the feedback form below to reach us.<\/p>\n<\/a><\/p>\n
\n$ sudo firewall-cmd –permanent –add-port=80\/tcp
\n$ sudo firewall-cmd –permanent –add-port=443\/tcp
\n$ sudo firewall-cmd –reload<\/p>\n
\n$ sudo ufw allow 80\/tcp
\n$ sudo ufw allow 443\/tcp
\n$ sudo ufw reload<\/p>\n
\nOR
\nhttp:\/\/Your-Domain.com<\/p>\n<\/a><\/p>\nHow to Configure Nginx Web Server<\/h3>\n
How to Serve Static Content Using Nginx in Standalone Mode<\/h4>\n
\nworker_processes 1;
\n…..<\/p>\n
\npid \/var\/run\/nginx.pid;
\n…..<\/p>\n
\n…..
\n}<\/p>\n
\nserver{
\n\u2026\u2026.
\n}
\n…..
\n}<\/p>\n
\nworker_processes auto;
\npid \/run\/nginx.pid;<\/p>\n
\nworker_connections 768;
\n# multi_accept on;
\n}<\/p>\n
\ninclude \/etc\/nginx\/mime.types;
\ndefault_type application\/octet-stream;<\/p>\n
\ndefault_type application\/octet-stream;<\/p>\n
\nerror_log \/var\/log\/nginx\/error.log;<\/p>\n
\n#tcp_nopush on;
\nkeepalive_timeout 65;
\n#gzip on;<\/p>\n
\n}<\/p>\n
\nlisten 80 default_server;
\nlisten [::]:80 default_server;
\nserver_name _;
\nroot \/var\/www\/html\/;
\nindex index.html;
\nlocation \/ {
\ntry_files $uri $uri\/ =404;
\n}
\n}<\/p>\n\n
<\/a><\/p>\nHow ot Restrict Access to a Web Page with Nginx<\/h4>\n
\n$ sudo apt install apache2-utils #Debian\/Ubuntu<\/p>\n
\n$ sudo chmod nginx:nginx \/etc\/nginx\/conf.d\/.htpasswd<\/p>\n\n
\nlisten 80 default_server;
\nserver_name localhost;
\nroot \/var\/www\/html\/;
\nindex index.html;
\nlocation \/ {
\ntry_files $uri $uri\/ =404;
\n}<\/p>\n
\nauth_basic “Restricted Access!”;
\nauth_basic_user_file \/etc\/nginx\/conf.d\/.htpasswd;
\n}
\n}<\/p>\nHow to Setup Name-based Virtual hosts (Server Blocks) in Nginx<\/h3>\n
\n
\n$ sudo chmod -R 755 \/var\/www\/html\/welovelinux.com\/public_html<\/p>\n
\n<head>
\n<title>www.wearetecmint.com<\/title>
\n<\/head>
\n<body>
\n<h1>This is the index page of www.wearetecmint.com<\/h1>
\n<\/body>
\n<\/html><\/p>\n
\n$ sudo vi \/etc\/nginx\/conf.d\/welovelinux.com.conf<\/p>\n
\nlisten 80;
\nserver_name wearetecmint.com;
\nroot \/var\/www\/html\/wearetecmint.com\/public_html ;
\nindex index.html;
\nlocation \/ {
\ntry_files $uri $uri\/ =404;
\n}<\/p>\n
\nlisten 80;
\nserver_name welovelinux.com;
\nroot \/var\/www\/html\/welovelinux.com\/public_html;
\nindex index.html;
\nlocation \/ {
\ntry_files $uri $uri\/ =404;
\n}<\/p>\n
\nhttp:\/\/welovelinux.com<\/p>\n<\/a><\/p>\nHow to Install and Configure SSL with Nginx<\/h3>\n
\n
<\/a><\/p>\n
\nlisten 80;
\nlisten [::]:80;
\nlisten 443 ssl;
\nlisten [::]:443 ssl;<\/p>\n
\nssl_certificate \/etc\/nginx\/ssl-certs\/nginx.crt;
\nssl_trusted_certificate \/etc\/nginx\/ssl-certs\/nginx.crt;
\nssl_certificate_key \/etc\/nginx\/ssl-certs\/nginx.key;<\/p>\n
\nroot \/var\/www\/html\/wearetecmint.com\/public_html;
\nindex index.html;
\nlocation \/ {
\ntry_files $uri $uri\/ =404;
\n}<\/p>\n<\/a><\/p>\nSummary<\/h5>\n