Challenge 1: An Nginx HTTPS Server Block for shop.example — Solution Walkthrough

The configuration:

  server {
      listen 443 ssl;
      server_name shop.example;
      ssl_certificate /etc/ssl/certs/shop.crt;
      ssl_certificate_key /etc/ssl/private/shop.key;
  }

Why this works:

listen 443 ssl tells Nginx to accept HTTPS connections on the standard
HTTPS port, server_name matches this block to the shop.example
domain (per Chapter 4's own server-block model), and
ssl_certificate/ssl_certificate_key point Nginx at the certificate
and private key files it needs to complete the TLS handshake and
terminate the connection at this block, exactly the directive pairing
this chapter's own Nginx section introduced.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise is a direct, hands-on application of this chapter's own
Nginx TLS example to a new domain and file paths, confirming the
listen/server_name/ssl_certificate/ssl_certificate_key combination as
the actual mechanism rather than a fixed example tied to one specific
domain.