Configure Traefik to use Let's Encrypt staging server
- Add caServer to ACME resolver for staging certificates - Prevents hitting production rate limits during testing
This commit is contained in:
@@ -28,6 +28,7 @@ certificatesResolvers:
|
|||||||
letsencrypt:
|
letsencrypt:
|
||||||
acme:
|
acme:
|
||||||
email: ACME_EMAIL_PLACEHOLDER # Will be replaced by deploy script
|
email: ACME_EMAIL_PLACEHOLDER # Will be replaced by deploy script
|
||||||
|
caServer: https://acme-staging-v02.api.letsencrypt.org/directory
|
||||||
storage: /acme.json
|
storage: /acme.json
|
||||||
# For testing: Use staging to avoid production rate limits
|
# For testing: Use staging to avoid production rate limits
|
||||||
# caServer: https://acme-staging-v02.api.letsencrypt.org/directory
|
# caServer: https://acme-staging-v02.api.letsencrypt.org/directory
|
||||||
|
|||||||
@@ -27,15 +27,13 @@ entryPoints:
|
|||||||
certificatesResolvers:
|
certificatesResolvers:
|
||||||
letsencrypt:
|
letsencrypt:
|
||||||
acme:
|
acme:
|
||||||
email: kelinfoxy@gmail.com
|
email: kelinfoxy@gmail.com # Will be replaced by deploy script
|
||||||
|
caServer: https://acme-staging-v02.api.letsencrypt.org/directory
|
||||||
storage: /acme.json
|
storage: /acme.json
|
||||||
# Use DNS challenge for wildcard certificate support
|
# DNS challenge - For wildcard certificates (*.yourdomain.duckdns.org)
|
||||||
|
# Works with DuckDNS - requires DUCKDNS_TOKEN in environment
|
||||||
dnsChallenge:
|
dnsChallenge:
|
||||||
provider: duckdns
|
provider: duckdns
|
||||||
delayBeforeCheck: 300 # Wait 5 minutes before checking DNS propagation
|
|
||||||
resolvers:
|
|
||||||
- "1.1.1.1:53"
|
|
||||||
- "8.8.8.8:53"
|
|
||||||
|
|
||||||
providers:
|
providers:
|
||||||
docker:
|
docker:
|
||||||
|
|||||||
Reference in New Issue
Block a user