[fixed] ACME config seems broken in beta1

ldez · July 21, 2019, 12:24am

You have to set a certResolver inside the tls section of your routers.

https://docs.traefik.io/v2.0/routing/routers/#certresolver

CLOUDFLARE_API_KEY is an alias to CF_API_EMAIL
CLOUDFLARE_EMAIL is an alias to CF_API_KEY

go-acme/lego/blob/d594e35ca6099e8be88aee72dcfe00f4d24f754f/providers/dns/cloudflare/cloudflare.toml#L18-L22


[Configuration.Credentials]
  CF_API_EMAIL = "Account email"
  CF_API_KEY = "API key"
  CLOUDFLARE_EMAIL = "Alias to CF_API_EMAIL"
  CLOUDFLARE_API_KEY = "Alias to CLOUDFLARE_API_KEY"

Topic		Replies	Views
V2.2.1: Router uses a non-existing resolver Traefik v2 (latest) letsencrypt-acme	1	1302	June 9, 2020
ACME/lego certificate request never happen Traefik v2 (latest) letsencrypt-acme	8	1593	September 19, 2022
Traefik refuses to use my valid ACME certificate, falls back to self signed Traefik v2 (latest) docker , letsencrypt-acme	3	853	August 4, 2023
Letsencrypt acme ends in 404 Traefik v2 (latest) docker-swarm , letsencrypt-acme	4	4502	February 10, 2021
ACME not working/ starting Traefik v2 (latest) docker	3	2278	March 26, 2021

[fixed] ACME config seems broken in beta1

Related Topics