Birmingham mumbai

[
 369 
]
At this point, assuming that you have the required content in 
/var/www/acmesales.com
 
and have a proper configuration file, the new site should respond as soon as you 
reload 
nginx
. But what about TLS? I recommend we always secure our websites, 
regardless of which solution we're using to serve it. With NGINX, we can add that 
feature easily. The certificate files themselves are the same regardless of whether 
we're using Apache or NGINX. If you haven't already created your certificate files, 
refer back to the section in this chapter where we did so. Assuming you already have 
certificate files, we just need to make additional changes to our configuration.
First, we change the first two lines to listen on port 
443
 with TLS instead of standard 
port 
80
:
listen 443 ssl; 
listen [::]:443 ssl; 
Next, we'll add the following two lines before the 
location
 section:
ssl_certificate /etc/certs/cert.pem; 
ssl_certificate_key /etc/certs/cert.key; 
ssl_session_timeout 5m; 
For this to work, you'll need to adjust the paths and the names of the 
cert
 files to 
make sure they
 match what you called them on your server. The entire file should 
look similar to the following at this point:
server { 
        listen 443 ssl; 
        listen [::]:443 ssl; 
 
        root /var/www/html; 
 
        index index.html index.htm index.nginx-debian.html; 
 
        server_name acmesales.com www.acmesales.com; 
 
         ssl_certificate /etc/certs/cert.pem; 
         ssl_certificate_key /etc/certs/cert.key; 
         ssl_session_timeout 5m; 
        location / { 
                try_files $uri $uri/ =404; 
        } 
} 

---

Serving Web Content