Skip to content

DNSChallenge is not activated #1642

@sylvainmouquet

Description

@sylvainmouquet

Welcome!

  • Yes, I've searched similar issues on GitHub and didn't find any.
  • Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What version of the Traefik's Helm Chart are you using?

39.0.0

What version of Traefik are you using?

latest

What did you expect to happen ?

DNSChallenge must be set to true when in certificatesResolvers the dnsChallenge is configured

What did you notice instead ?

The TLS challenge is activated, the variable --certificatesresolvers.letsencrypt.acme.dnschallenge=true is not present in the command line of traefik

What are your values ?

certificatesResolvers:
  letsencrypt:
    acme:
      email: <email>
      dnsChallenge:
        provider: cloudflare
        propagation:
          delayBeforeChecks: 30   # 30s delay is recommended for DNS propagation
        resolvers:
          - 1.1.1.1
          - 8.8.8.8
      #tlsChallenge: true
      #httpChallenge:
      #  entryPoint: "web"
      storage: /data/acme.json

Additional Information

i have added this configuration to solve it:

additionalArguments: 
  - "--certificatesresolvers.letsencrypt.acme.dnschallenge=true"

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bug/possiblea possible bug that needs analysis before it is confirmed or fixed.

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions