Mengamankan Nginx dengan SSL/TLS
Terapkan HTTPS dengan mengonfigurasi sertifikat SSL/TLS pada Nginx untuk komunikasi yang aman.
Mengamankan Nginx dengan SSL/TLS adalah pelajaran API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) gratis di CoddyKit. Ini adalah pelajaran 1 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway), dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) mencakup 4 pelajaran total.
Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.
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: Usecurl -v https://yourdomain.comfrom 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.
Belajar API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) dengan tutor AI — gratis
Tulis dan jalankan kode asli di browser kamu, dapatkan bantuan instan dari tutor AI 24/7, dan lanjutkan di mana kamu tinggalkan di web atau aplikasi.
- Kursus
- 12
- Pelajaran
- 48
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Mengamankan Nginx dengan SSL/TLS” gratis?
Ya — teks lengkap “Mengamankan Nginx dengan SSL/TLS” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway), upgrade ke CoddyKit PRO. Kursus API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) mencakup 4 pelajaran total.
Apa yang akan aku pelajari di “Mengamankan Nginx dengan SSL/TLS”?
Terapkan HTTPS dengan mengonfigurasi sertifikat SSL/TLS pada Nginx untuk komunikasi yang aman. Kamu berlatih API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.
Apakah aku perlu pengalaman untuk memulai API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway)?
Tidak diperlukan pengalaman sebelumnya. API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 1 dari 4.
Berapa lama pelajaran “Mengamankan Nginx dengan SSL/TLS” memakan waktu?
Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.
Bisakah aku menulis dan menjalankan kode dalam pelajaran API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) ini?
Ya. Setiap pelajaran API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.
Semua pelajaran dalam kursus ini
- Mengamankan Nginx dengan SSL/TLS
- HTTP/2 dan Optimasi Nginx
- Autentikasi Dasar dan Kontrol Akses
- Memperkuat Nginx dengan Header Keamanan