init

data/nginx/app.conf

@@ -17,13 +17,13 @@ server {
     server_name thelinuxpro.net;
     server_tokens off;
 
-    ssl_certificate /etc/letsencrypt/live/example.org/fullchain.pem;
-    ssl_certificate_key /etc/letsencrypt/live/example.org/privkey.pem;
+    ssl_certificate /etc/letsencrypt/live/thelinuxpro.net/fullchain.pem;
+    ssl_certificate_key /etc/letsencrypt/live/thelinuxpro.net/privkey.pem;
     include /etc/letsencrypt/options-ssl-nginx.conf;
     ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem;
 
     location / {
-        proxy_pass  http://example.org;
+        proxy_pass  http://127.0.0.1:8008;
         proxy_set_header    Host                $http_host;
         proxy_set_header    X-Real-IP           $remote_addr;
         proxy_set_header    X-Forwarded-For     $proxy_add_x_forwarded_for;

docker-compose.yml

@@ -1,4 +1,11 @@
-version: '3'
+---
+volumes:
+  nginx_conf:
+    driver: local
+  certbot_conf:
+    driver: local
+  certbot_www: 
+    driver: local
 
 services:
   nginx:

init-letsencrypt.sh

@@ -5,11 +5,11 @@ if ! [ -x "$(command -v docker compose)" ]; then
   exit 1
 fi
 
-domains=(thelinuxpro.net thelinux.pro git.thelinuxpro.net kameronkenny.com www.kameronkenny.com blog.kameronkenny.com)
+domains=(thelinuxpro.net)
 rsa_key_size=4096
 data_path="./data/certbot"
 email="kkenny379@gmail.com" # Adding a valid address is strongly recommended
-staging=1 # Set to 1 if you're testing your setup to avoid hitting request limits
+staging=0 # Set to 1 if you're testing your setup to avoid hitting request limits
 
 if [ -d "$data_path" ]; then
   read -p "Existing data found for $domains. Continue and replace existing certificate? (y/N) " decision