I seem to have gotten the Traefik reverse proxy working according to Techno Tim Put Wildcard Certificates and SSL on EVERYTHING (github reference_files for traefik-portainer-ssl)

Below is a basic description of the process that aligns with my configuration files. I do this for 2 reasons, both allowing me independence.

1. Sometimes the source information or link are; changed, lost or removed.
2. These note reference my current specific installation.

These containers all talk via a docker bridge network named proxy, docker network create proxy

cd /home/docker_store
sudo mkdir traefik
sudo chown baumkp:baumkp traefik
cd traefik
mkdir data
cd data
touch acme.json
chmod 600 acme.json
touch traefik.yml
cd ..

My traefik.yml locatation: /home/docker_store/traefik/data/traefik.yml. The current TechnoTim one here.

docker network create proxy

touch docker-compose.yml
touch provider.env

My docker-compose.yml location: /home/docker_store/traefik/docker-compose.yml. The current TechnoTim one here.
Note my docker compose file has some changes from the TechnoTim one, in particular the use of the Godaddy DNS chanlenge API instead of the the Cloudflare one used by TechnoTim.

Sadly Godaddy does not make it as transparent as it should be to access their DNS challenge API. Perhaps because they are focused on their commercial certificate product. It is accessed from their developer portal Godaddy Developer Portal, from here the API keys can be made. These keys then need to be copied into /home/docker_store/traefik/data/provider.env:

GODADDY_API_KEY=[Your API_KEY key from Godaddy API]
GODADDY_API_SECRET=[Your API_SECRET key from Godaddy API]

sudo apt update
sudo apt install apache2-utils

echo $(htpasswd -nb "<USER>" "<PASSWORD>") | sed -e s/\\$/\\$\\$/g

NOTE: Replace <USER> with your username and <PASSWORD> with your password to be hashed.

Paste the output in your docker-compose.yml in line (traefik.http.middlewares.traefik-auth.basicauth.users=<USER>:<HASHED-PASSWORD>)

cd data
touch config.yml

docker-compose up -d

cd /home/docker_store
sudo mkdir portainer
sudo chown baumkp:baumkp portainer
cd portainer
touch docker-compose.yml
mkdir data

My docker-compose.yml location: /home/docker_store/portainer/docker-compose.yml. The current TechnoTim one here.

docker-compose up -d

cd /home/docker_store/traefik/data
nvim config.yml

I have broken down the Traefik router dynamic configuration file, My config.yml into 2 configuration files. One for the http/https specific router configuration and the other for the tcp router configuration, I do not use any UDP router configurations to date. I placed these files in the sub-directory: /home/docker_store/traefik/data/config. Traefik has been setup to look at all configuration files in this sub-directory and to dynamically update changes on the run. The current TechnoTim one here., also look at Portainer's instructions here: Deploying Portainer behind Traefik Proxy

docker-compose up -d --force-recreate

Folder Structure:

./traefik
├── data
│   ├── acme.json         | This is the Lets Encrypt RSA key file downloaded by Traefik
│   ├── config
|   |   ├── http.yml      | This is the dynamic configuration file for http
|   |   └── tcp.yml       | This is the dynamic configuration file for tcp
│   ├── provider.env      | This has the key file for DNS wildcard challenge on LetsEncrypt 
│   ├── traefik.yml       | This is the main traefik static configuration file 
│   └── traefik.log       | This is the main traefik log file (permanent, but does not show up on the Docker error log)
└── docker-compose.yml

The Traefik middleware

ipWhitelist

  <code>default-whitelist:|
    ipWhiteList:
      sourceRange:
      - "10.0.0.0/8"
      - "192.168.0.0/16"
      - "172.16.0.0/12"</code>

Todo: look at whitelisting in more detail

• /home/docker_store/traefik/data/config/http.yml has traefik middleware whitelisting defined looks defined as default for all containers in config.yml. Need to check following:
  • Can this be defined for each container setup in config.yml? Looks likely.
  • Can this be reliably setup for public access of certain containers?
  • Ensure no public access to portainer and traefik dashboards?
• See reddit dicussion https://www.reddit.com/r/Traefik/comments/qi2435/traefik_v2_mixed_and_both_internal_and_external/Traefik v2 mixed (and both) internal and external?, which indicates this is so, however it notes a possible issue with VPN access.

For TCP and HTTPS services behind the Traefik router that require TLS the Traefik router must be specified to pass through the TLS, that is not terminate the SSL connection.

The Standard entry point port normally defined are HTTP (port 80 and perhaps 8080) and HTTPS (port 443). If you are using other services then additional entry points need to be defined, as required for each service / port. Mail servers are an example that requires use of specialised TCP entrypoints. Often these entry points also needed to be passed to the server without handling (termination) of SSL connections. Do not forget to expose the used ports in the Docker / Docker Compose file.

• Router passthrough
• Traefik and TLS Passthrough
• Enable and configure file provider within a docker-compose defined Traefik instance

• Traefik
  • Traefix
  • traefik proxy & Lets Encrypt
  • Smarthome Beginner Ultimate Traefik Docker Compose Guide [2022] with LetsEncrypt
  • Christian Lempa boilerplates/docker-compose/traefik/
  • Techno Tim techno-tim.github.io/reference_files/traefik-portainer-ssl/traefik/docker-compose.yml / Put Wildcard Certificates and SSL on EVERYTHING
  • Add a Docker Standalone environment
  • (Traefik v2.2) Unable to obtain ACME certificate with DNS challenge using Go Daddy
  • Cannot get wildcard certificate with traefik v2 and godaddy
  • Traefik - ACME with GoDaddy as provider

• Traefik whitelists

• Nginx Proxy Manager
  • Nginxproxymanager.com Best Practice: Use a Docker network

• openssl x509 -in (path to certificate and certificate filename) -text -noout
• openssl s_client -connect localhost:443 2>/dev/null | openssl x509 -noout -dates
• How to utilize openssl in Linux to check SSL certificate details

• Export Traefik Certificates
• Need to install the jq package

#!/bin/bash
 
# Requirements: you will need to install jq and maybe openssl
 
# creates a directory for all of your certificates
mkdir -p certificates/
 
# reads the acme.json file, please put this file in the same directory as your script
json=$(cat acme.json)
 
export_cer_key () {
    echo $json | jq -r '.[].Certificates[] | select(.domain.main == "'$1'") | .certificate' | base64 -d > certificates/$1.cer
    echo $json | jq -r '.[].Certificates[] | select(.domain.main == "'$1'") | .key' | base64 -d > certificates/$1.key
}
 
export_pfx () {
        openssl pkcs12 -export -out certificates/$domain.pfx -inkey certificates/$domain.key -in certificates/$domain.cer -passout pass: 
}
 
read -p "Do you want to export as .pfx file as well [y]?" REPLY
 
# iterates through all of your domains
for domain in $(echo $json | jq -r '.[].Certificates[].domain.main')
do
    if [[ $REPLY =~ ^[Yy]$ ]]
    then
        export_cer_key "$domain"
        export_pfx "$domain"
    else
        export_cer_key "$domain"
    fi
done

There is also How to export certificates from Traefik certificate store in python.

AS of writing (June 2023) Crowdsec is still relatively new. The documentation is not that easy to follow. Most the Youtube crowd info uses Traefik to with Crowdsec. I could also consider using nftable that I use as main ingress fire wall Firewall Bouncer.

References:

• Crowdsec home
• Open Source & Collaborative Security with CrowdSec and Traefik - CrowdSec & Traefik Tutorial
• ibracorp.io Crowdsec
• Smarthome Beginner
  • Crowdsec Docker Compose Guide Part 1: Powerful IPS with Firewall Bouncer
  • CrowdSec Docker Part 2: Improved IPS with Cloudflare Bouncer
  • CrowdSec Docker Part 3: Traefik Bouncer for Additional Security] *[[https://www.smarthomebeginner.com/crowdsec-multiserver-docker/|CrowdSec Multiserver Docker (Part 4): For Ultimate Protection
  • Cloudflare Settings for Traefik Docker: DDNS, CNAMEs, & Tweaks
  • 20 Docker Security Best Practices – Hardening Traefik Docker Stack

Crowdsec Bouncer Traefik plugin

• Crowdsec Bouncer Traefik Plugin