bunny-lab/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update Docker & Kubernetes/Docker/Docker Compose/Traefik.md

Browse Source
This commit is contained in:
Nicole Rappe
2024-11-07 18:18:11 -07:00
parent 7b265e9e7b
commit 498d46e900
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
Docker & Kubernetes/Docker/Docker Compose/Traefik.md
View File

@ -21,7 +21,11 @@
If these are not set, Traefik will still work, but SSL certificates will not be issued from Let's Encrypt, and SSL traffic will be terminated using a self-signed Traefik-based certificate, which is only good for local testing.
If you plan on using HTTP-based challenges, you will need to un-comment `"--certificatesresolvers.myresolver.acme.tlschallenge=true"` in the docker-compose data, and comment-out `"--certificatesresolvers.letsencrypt.acme.dnschallenge=true"` and `"--certificatesresolvers.letsencrypt.acme.dnschallenge.provider=cloudflare"`. Lastly, you need to ensure that port 80 on your firewall is opened to the IP of the Traefik Reverse Proxy to allow Let's Encrypt to do TLS-based challenges.
If you plan on using HTTP-based challenges, you will need to make the following changes in the docker-compose.yml data:
- Un-comment `"--certificatesresolvers.myresolver.acme.tlschallenge=true"`
- Comment-out `"--certificatesresolvers.letsencrypt.acme.dnschallenge=true"`
- Comment-out `"--certificatesresolvers.letsencrypt.acme.dnschallenge.provider=cloudflare"`
- Lastly, you need to ensure that port 80 on your firewall is opened to the IP of the Traefik Reverse Proxy to allow Let's Encrypt to do TLS-based challenges.
### Stack Deployment Information
```jsx title="docker-compose.yml"