0Pricing
API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) · Leçon

Sécuriser Nginx avec SSL/TLS

Mettez en œuvre HTTPS en configurant des certificats SSL/TLS avec Nginx pour sécuriser les communications.

Sécuriser Nginx avec SSL/TLS est une leçon API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) gratuite sur CoddyKit. Ceci est la leçon 1 sur 4. Tu peux lire la leçon complète ci-dessous gratuitement — puis la pratiquer en direct dans le navigateur avec un éditeur de code intégré et un tuteur IA 24/7. Elle fait partie du parcours d'apprentissage API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway), et ta progression se synchronise sur le web et l'application CoddyKit. Le cours API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) comprend 4 leçons au total.

Certaines parties de cette leçon n'ont pas encore été traduites et s'affichent en anglais.

Secure Your Site with HTTPS

Welcome to securing Nginx with SSL/TLS! This lesson will guide you through setting up HTTPS for your websites.

HTTPS (Hypertext Transfer Protocol Secure) is the secure version of HTTP. It ensures that communication between a user's browser and your Nginx server is encrypted and authenticated.

Using HTTPS is crucial for protecting sensitive data, building user trust, and is often a requirement for modern web features and SEO.

How SSL/TLS Protects Data

At its core, HTTPS relies on SSL/TLS (Secure Sockets Layer/Transport Layer Security) protocols. These protocols establish an encrypted link between a client and a server.

  • Handshake: When you visit an HTTPS site, your browser and the server perform a 'handshake' to agree on encryption methods.
  • Encryption: Once agreed, all data exchanged (passwords, credit card numbers, etc.) is encrypted, making it unreadable to eavesdroppers.
  • Authentication: It also verifies the server's identity using a certificate, preventing 'man-in-the-middle' attacks.

Understanding SSL Certificates

An SSL Certificate is a digital file that binds a cryptographic key to an organization's details. It's issued by a trusted Certificate Authority (CA).

When a browser connects to an HTTPS website, it checks the certificate to ensure:

  • The website's identity is legitimate.
  • The connection is encrypted.
  • The data hasn't been tampered with.

Certificates come in different validation levels, from basic Domain Validated (DV) to Extended Validation (EV) for higher assurance.

Obtaining Your SSL Certificate

To enable HTTPS, you first need an SSL certificate. There are two main ways to get one:

  • Commercial CAs: Companies like DigiCert or GlobalSign sell certificates, often with additional features and warranties.
  • Let's Encrypt: A free, automated, and open certificate authority. It's widely used for its simplicity and cost-effectiveness. We'll focus on configuring Nginx with certificates obtained this way.

For Let's Encrypt, tools like Certbot automate the process of obtaining and renewing certificates.

Nginx SSL Configuration Prep

Before we dive into Nginx configuration, ensure you have these prerequisites:

  • Nginx Installed: Your Nginx server is up and running.
  • Domain Name: A registered domain name pointing to your server's IP address.
  • Certificate Files: You'll need two main files: the certificate file (e.g., yourdomain.crt) and the private key file (e.g., yourdomain.key). These are usually placed in a secure directory like /etc/nginx/ssl/ or /etc/letsencrypt/live/yourdomain/.

Essential Nginx SSL Directives

Configuring Nginx for SSL starts with defining a server block that listens on port 443 (the standard HTTPS port) and specifies your certificate files.

Here's a basic example:

server {
    listen 443 ssl;
    server_name example.com;

    ssl_certificate /etc/nginx/ssl/example.com.crt;
    ssl_certificate_key /etc/nginx/ssl/example.com.key;

    # Your website's root directory
    root /var/www/html;
    index index.html;

    location / {
        try_files $uri $uri/ =404;
    }
}

Advanced SSL Security Settings

To enhance security, it's good practice to specify which SSL/TLS protocols and ciphers Nginx should use. This helps prevent vulnerabilities from older, less secure options.

  • ssl_protocols: Defines allowed TLS versions (e.g., TLSv1.2, TLSv1.3).
  • ssl_ciphers: Lists strong encryption algorithms.
  • ssl_prefer_server_ciphers on: Tells the server to prefer its own cipher order over the client's.
server {
    listen 443 ssl;
    server_name example.com;

    ssl_certificate /etc/nginx/ssl/example.com.crt;
    ssl_certificate_key /etc/nginx/ssl/example.com.key;

    ssl_protocols TLSv1.2 TLSv1.3;
    ssl_ciphers 'ECDHE-ECDSA-AES128-GCM-256:ECDHE-RSA-AES128-GCM-256:ECDHE-ECDSA-AES256-GCM-256:ECDHE-RSA-AES256-GCM-256:DHE-RSA-AES128-GCM-256:DHE-RSA-AES256-GCM-256';
    ssl_prefer_server_ciphers on;

    root /var/www/html;
    index index.html;

    location / {
        try_files $uri $uri/ =404;
    }
}

Enforcing HTTPS Redirects

For optimal security, you should ensure all HTTP traffic is automatically redirected to HTTPS. This can be done by adding a separate server block that listens on port 80 (HTTP) and issues a 301 (permanent) redirect.

This ensures users always access your site securely, even if they type in http://.

server {
    listen 80;
    server_name example.com www.example.com;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    server_name example.com www.example.com;

    ssl_certificate /etc/nginx/ssl/example.com.crt;
    ssl_certificate_key /etc/nginx/ssl/example.com.key;

    ssl_protocols TLSv1.2 TLSv1.3;
    ssl_ciphers 'ECDHE-ECDSA-AES128-GCM-256:ECDHE-RSA-AES128-GCM-256:ECDHE-ECDSA-AES256-GCM-256:ECDHE-RSA-AES256-GCM-256:DHE-RSA-AES128-GCM-256:DHE-RSA-AES256-GCM-256';
    ssl_prefer_server_ciphers on;

    root /var/www/html;
    index index.html;

    location / {
        try_files $uri $uri/ =404;
    }
}

Testing Your HTTPS Configuration

After configuring Nginx, it's vital to test your setup to ensure everything works correctly and securely.

  • Browser: Open your site in a browser. Look for the padlock icon in the address bar.
  • Developer Tools: Use your browser's dev tools (Network tab) to check that requests are over HTTPS.
  • SSL Labs: Use online tools like SSL Labs' SSL Server Test to get a comprehensive report and a security grade for your server.
  • curl: Use curl -v https://yourdomain.com from your terminal to inspect the SSL handshake details.

Check Your SSL Knowledge

Which Nginx directive is primarily responsible for specifying the file path to your server's public SSL certificate?

Recap & Next Steps

Congratulations! You've learned how to secure Nginx with SSL/TLS.

We covered:

  • The importance of HTTPS and how SSL/TLS works.
  • Understanding SSL certificates and how to obtain them.
  • Configuring Nginx with essential and advanced SSL directives.
  • Implementing HTTP to HTTPS redirects for full security.
  • Methods for testing your SSL configuration.

Keeping your websites secure is a continuous process. Regularly check your certificates for expiry and keep Nginx updated.

Questions Fréquemment Posées

La leçon « Sécuriser Nginx avec SSL/TLS » est-elle gratuite ?

Oui — le texte complet de « Sécuriser Nginx avec SSL/TLS » est gratuit à lire ici sur le web. Pour la pratiquer de manière interactive (un éditeur de code intégré et un tuteur IA 24/7) et déverrouiller le reste du cours API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway), passe à CoddyKit PRO. Le cours API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) comprend 4 leçons au total.

Qu'est-ce que j'apprendrai dans « Sécuriser Nginx avec SSL/TLS » ?

Mettez en œuvre HTTPS en configurant des certificats SSL/TLS avec Nginx pour sécuriser les communications. Tu pratiques API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) avec du code pratique que tu exécutes directement dans le navigateur, et un tuteur IA 24/7 répond à tes questions au fur et à mesure que tu avances dans la leçon.

Dois-je avoir de l'expérience pour commencer API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) ?

Aucune expérience préalable n'est requise. API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) sur CoddyKit est structuré pour les débutants jusqu'aux apprenants avancés, donc tu peux commencer ici ou depuis le début et avancer à ton rythme. Ceci est la leçon 1 sur 4.

Combien de temps prend la leçon « Sécuriser Nginx avec SSL/TLS » ?

La plupart des leçons CoddyKit prennent environ 5–10 minutes. Chacune est courte et interactive, tu progresses régulièrement et tu repiques exactement où tu t'es arrêté sur le web et l'app.

Peux-tu écrire et exécuter du code dans cette leçon API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) ?

Oui. Chaque leçon API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) inclut un éditeur de code intégré, tu écris et exécutes du vrai code directement dans ton navigateur et tu reçois des retours IA instantanés — aucune configuration locale requise.

Toutes les leçons de ce cours

  1. Sécuriser Nginx avec SSL/TLS
  2. HTTP/2 et optimisation de Nginx
  3. Authentification de base et contrôle d’accès
  4. Renforcer Nginx avec des en-têtes de sécurité
← Retour à API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway)