From 78fdf489408bf15cc452e33751f772ec99d4046b Mon Sep 17 00:00:00 2001 From: Linden Crandall Date: Sat, 8 Feb 2025 01:36:41 +0000 Subject: [PATCH] Update Production HTTPS Setup --- Production-HTTPS-Setup.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/Production-HTTPS-Setup.md b/Production-HTTPS-Setup.md index c6a3bdb..a0e3715 100644 --- a/Production-HTTPS-Setup.md +++ b/Production-HTTPS-Setup.md @@ -81,8 +81,15 @@ server { } } ``` -- Run `sudo docker compose up` to generate SSL cert -- There should be a new /certbot folder created at the project root, and the cert and key `.pem` files should be created at `/etc/letsencrypt/live` +- Run `sudo docker compose up` to generate SSL cert. You should see something like this in the console, note the .pem key locations: +``` +certbot-1 | Successfully received certificate. +certbot-1 | Certificate is saved at: /etc/letsencrypt/live/automatisch.lasthourhosting.org/fullchain.pem +certbot-1 | Key is saved at: /etc/letsencrypt/live/automatisch.lasthourhosting.org/privkey.pem +certbot-1 | This certificate expires on 2025-05-09. +certbot-1 | These files will be updated when the certificate renews. +``` +- There should be a new /certbot folder created at the project root, and the cert and key `.pem` files should be created at `/etc/letsencrypt/live` - After this completes, stop the containers `ctrl+c` and overwrite the `automatisch_letsencrypt_nginx.conf` file with the `secondary_automatisch_letsencrypt_nginx.conf` file's contents which has the 443 https and SSL configs: ``` cp https/nginx/secondary_automatisch_letsencrypt_nginx.conf https/nginx/automatisch_letsencrypt_nginx.conf