Skip to content
This repository has been archived by the owner on Jun 4, 2024. It is now read-only.
/ lego-deprecated Public archive

(DEPRECATED) DNS modules so Caddy can solve the ACME DNS challenge with over 75 providers

License

Notifications You must be signed in to change notification settings

caddy-dns/lego-deprecated

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

14 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

DNS Providers for Caddy (deprecated)

This one module gives Caddy the ability to solve the ACME DNS challenge with over 75 DNS providers.

⚠️ This module is deprecated

This module wraps DNS providers that are implemented by go-acme/lego which uses an old API that is no longer supported by Caddy. As such, this module is a temporary shim until a sufficient number of providers are ported to the new libdns interfaces.

You can use this module to get up and running quickly with your provider of choice, but instead of using this module long-term, please consider contributing to a libdns package for your provider instead.

The libdns implementations offer better performance, lighter dependencies, easier maintainability with growth, and more flexible configuration.

Instructions

  1. Get Caddy with the lego-deprecated plugin installed
  2. Find your DNS Provider and provider code, in the lego DNS documentation
    • Example: CloudFlare is cloudflare, DNSimple is dnsimple
  3. Set the lego provider's credentials and other ENVs in your environment configuration
    • Example: CLOUDFLARE_API_KEY=xxxxxxxx
  4. Configure the ACME issuer
    via Caddy JSON
    {
    	"module": "acme",
    	"challenges": {
    		"dns": {
    			"provider": {
    				"name": "lego_deprecated",
    				"provider_name": "<provider_code>"
    			}
    		}
    	}
    }
    or Caddyfile
    tls {
    	dns lego_deprecated <provider_code>
    }
  5. (don't forget to replace <provider_code> with the name of your provider, such as cloudflare or dnsimple)

Compatibility note

Unlike other modules in the caddy-dns repositories, this one can only be used in the ACME issuer module for solving the DNS challenge. Even though it shares the more general dns.providers namespace with other provider modules, using this module in any other place in your config will result in errors.