search
HomeOperation and MaintenanceNginxHow to configure and use NGINX web server in Ubuntu 16.04

Nginx is specially developed for performance optimization. Its most well-known advantages are its stability and low system resource consumption, as well as its high processing capability for concurrent connections (a single physical server can Supports 30,000 to 50,000 concurrent connections), is a high-performance HTTP and reverse proxy server, and is also an IMAP/POP3/SMTP proxy service. Ubuntu 16.04中怎么配置和使用NGINX Web服务器

Installing Certbot

The first step is to install certbot, a software client that can automate almost all processes. Certbot developers maintain their own Ubuntu repositories that contain newer software than what exists in the Ubuntu repositories.

Add Certbot repository:

# add-apt-repository ppa:certbot/certbot

Next, update the APT source list:

# apt-get update

At this point, you can use the following apt command to install certbot:

# apt-get install certbot

Certbot is now installed and ready to use.

Obtaining a Certificate

There are various Certbot plugins available for obtaining SSL certificates. These plugins help obtain certificates, while the installation of certificates and web server configuration are left to the administrator.

We use a plugin called Webroot to obtain the SSL certificate.

This plugin is recommended where you have the ability to modify the content being served. There is no need to stop the web server during the certificate issuance process.

Configuring NGINX

Webroot creates a temporary file for each domain in the .well-known directory under the web root. In our example, the web root is /var/www/html. Make sure this directory is accessible during Let's Encrypt authentication. To do this, edit the NGINX configuration. Open /etc/nginx/sites-available/default using a text editor:

# $EDITOR /etc/nginx/sites-available/default

In that file, inside the server block, enter the following:

location ~ /.well-known {
allow all;
}

Save, exit and check NGINX Configuration:

# nginx -t

If there are no errors, it should be displayed as follows:

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

Restart NGINX:

# systemctl restart nginx

Use Certbot to obtain the certificate

The next step is to use Certbot Webroot plugin obtains new certificate. In this tutorial, we will secure the example domain www.example.com. Each domain that should be protected by the certificate needs to be specified. Execute the following command:

# certbot certonly --webroot --webroot-path=/var/www/html -d www.example.com

During this process, Cerbot will ask for a valid email address for notifications. You will also be asked to share with EFF, but this is not required. After agreeing to the terms of service, it will get a new certificate.

Finally, the directory /etc/letsencrypt/archive will contain the following files:

  • chain.pem: Let's Encrypt encryption chain certificate.

  • cert.pem: Domain name certificate.

  • fullchain.pem: The combination of cert.pem and chain.pem.

  • privkey.pem: The private key of the certificate.

Certbot will also create a symbolic link to the latest certificate file in /etc/letsencrypt/live/domain_name/. This is the path we will use in the server configuration.

Configuring SSL/TLS on NGINX

The next step is server configuration. Create a new snippet in /etc/nginx/snippets/. A snippet refers to a piece of configuration that can be included in a virtual host configuration file. Create a new file as follows:

# $EDITOR /etc/nginx/snippets/secure-example.conf

The contents of this file will specify the certificate and key location. Paste the following:

ssl_certificate /etc/letsencrypt/live/domain_name/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/domain_name/privkey.pem;

In our example, domain_name is example.com.

Edit NGINX configuration

Edit the default virtual host file:

# $EDITOR /etc/nginx/sites-available/default

As follows:

server {
listen 80 default_server;
listen [::]:80 default_server;
server_name www.example.comreturn 301 https://$server_name$request_uri;# SSL configuration#listen 443 ssl default_server;
listen [::]:443 ssl default_server;
include snippets/secure-example.conf## Note: You should disable gzip for SSL traffic.# See: https://bugs.debian.org/773332# ...}

This will enable NGINX encryption.

Save, exit and check the NGINX configuration file:

# nginx -tnginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

Restart NGINX:

# systemctl restart nginx

The above is the detailed content of How to configure and use NGINX web server in Ubuntu 16.04. For more information, please follow other related articles on the PHP Chinese website!

Statement
This article is reproduced at:亿速云. If there is any infringement, please contact admin@php.cn delete
Using NGINX Unit: Deploying and Managing ApplicationsUsing NGINX Unit: Deploying and Managing ApplicationsApr 22, 2025 am 12:06 AM

NGINXUnit can be used to deploy and manage applications in multiple languages. 1) Install NGINXUnit. 2) Configure it to run different types of applications such as Python and PHP. 3) Use its dynamic configuration function for application management. Through these steps, you can efficiently deploy and manage applications and improve project efficiency.

NGINX vs. Apache: A Comparative Analysis of Web ServersNGINX vs. Apache: A Comparative Analysis of Web ServersApr 21, 2025 am 12:08 AM

NGINX is more suitable for handling high concurrent connections, while Apache is more suitable for scenarios where complex configurations and module extensions are required. 1.NGINX is known for its high performance and low resource consumption, and is suitable for high concurrency. 2.Apache is known for its stability and rich module extensions, which are suitable for complex configuration needs.

NGINX Unit's Advantages: Flexibility and PerformanceNGINX Unit's Advantages: Flexibility and PerformanceApr 20, 2025 am 12:07 AM

NGINXUnit improves application flexibility and performance with its dynamic configuration and high-performance architecture. 1. Dynamic configuration allows the application configuration to be adjusted without restarting the server. 2. High performance is reflected in event-driven and non-blocking architectures and multi-process models, and can efficiently handle concurrent connections and utilize multi-core CPUs.

NGINX vs. Apache: Performance, Scalability, and EfficiencyNGINX vs. Apache: Performance, Scalability, and EfficiencyApr 19, 2025 am 12:05 AM

NGINX and Apache are both powerful web servers, each with unique advantages and disadvantages in terms of performance, scalability and efficiency. 1) NGINX performs well when handling static content and reverse proxying, suitable for high concurrency scenarios. 2) Apache performs better when processing dynamic content and is suitable for projects that require rich module support. The selection of a server should be decided based on project requirements and scenarios.

The Ultimate Showdown: NGINX vs. ApacheThe Ultimate Showdown: NGINX vs. ApacheApr 18, 2025 am 12:02 AM

NGINX is suitable for handling high concurrent requests, while Apache is suitable for scenarios where complex configurations and functional extensions are required. 1.NGINX adopts an event-driven, non-blocking architecture, and is suitable for high concurrency environments. 2. Apache adopts process or thread model to provide a rich module ecosystem that is suitable for complex configuration needs.

NGINX in Action: Examples and Real-World ApplicationsNGINX in Action: Examples and Real-World ApplicationsApr 17, 2025 am 12:18 AM

NGINX can be used to improve website performance, security, and scalability. 1) As a reverse proxy and load balancer, NGINX can optimize back-end services and share traffic. 2) Through event-driven and asynchronous architecture, NGINX efficiently handles high concurrent connections. 3) Configuration files allow flexible definition of rules, such as static file service and load balancing. 4) Optimization suggestions include enabling Gzip compression, using cache and tuning the worker process.

NGINX Unit: Supporting Different Programming LanguagesNGINX Unit: Supporting Different Programming LanguagesApr 16, 2025 am 12:15 AM

NGINXUnit supports multiple programming languages ​​and is implemented through modular design. 1. Loading language module: Load the corresponding module according to the configuration file. 2. Application startup: Execute application code when the calling language runs. 3. Request processing: forward the request to the application instance. 4. Response return: Return the processed response to the client.

Choosing Between NGINX and Apache: The Right Fit for Your NeedsChoosing Between NGINX and Apache: The Right Fit for Your NeedsApr 15, 2025 am 12:04 AM

NGINX and Apache have their own advantages and disadvantages and are suitable for different scenarios. 1.NGINX is suitable for high concurrency and low resource consumption scenarios. 2. Apache is suitable for scenarios where complex configurations and rich modules are required. By comparing their core features, performance differences, and best practices, you can help you choose the server software that best suits your needs.

See all articles

Hot AI Tools

Undresser.AI Undress

Undresser.AI Undress

AI-powered app for creating realistic nude photos

AI Clothes Remover

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undress AI Tool

Undress AI Tool

Undress images for free

Clothoff.io

Clothoff.io

AI clothes remover

Video Face Swap

Video Face Swap

Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Tools

Notepad++7.3.1

Notepad++7.3.1

Easy-to-use and free code editor

Dreamweaver Mac version

Dreamweaver Mac version

Visual web development tools

ZendStudio 13.5.1 Mac

ZendStudio 13.5.1 Mac

Powerful PHP integrated development environment

SAP NetWeaver Server Adapter for Eclipse

SAP NetWeaver Server Adapter for Eclipse

Integrate Eclipse with SAP NetWeaver application server.

DVWA

DVWA

Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software