le-cert-server
GitHub

OVH

Configuration for the OVH DNS provider.

See the lego documentation for full details.

letsEncrypt:
  dnsProvider: "ovh"
  dnsCredentials:
    # OVH_ACCESS_TOKEN: Access token
    accessToken: ""
    # OVH_APPLICATION_KEY: Application key (Application Key authentication)
    applicationKey: ""
    # OVH_APPLICATION_SECRET: Application secret (Application Key authentication)
    applicationSecret: ""
    # OVH_CONSUMER_KEY: Consumer key (Application Key authentication)
    consumerKey: ""
    # OVH_ENDPOINT: Endpoint URL (ovh-eu or ovh-ca)
    endpoint: ""
    # OVH_POLLING_INTERVAL: Time between DNS propagation check in seconds (Default: 2)
    pollingInterval: ""
    # OVH_PROPAGATION_TIMEOUT: Maximum waiting time for DNS propagation in seconds (Default: 60)
    propagationTimeout: ""
    # OVH_TTL: The TTL of the TXT record used for the DNS challenge in seconds (Default: 120)
    ttl: ""

Credentials are passed directly to lego using strong types and are never written to the process environment. You may also use the raw lego environment-variable names as keys instead of the normalized names.

In addition to the application-key credentials above, OVH supports OAuth2 client credentials (OVH_CLIENT_ID/OVH_CLIENT_SECRET). Those are read by lego from the environment and cannot currently be set through dnsCredentials.

Edit this page on GitHub