go-acme / lego

Let's Encrypt/ACME client and library written in Go
https://go-acme.github.io/lego/
MIT License
7.58k stars 994 forks source link

Debian 11: unrecognized DNS provider: cloudflare #1922

Closed stephen-hill closed 1 year ago

stephen-hill commented 1 year ago

Welcome

What did you expect to see?

I expected my certificate to be generated using Cloudflare.

lego dnshelp outputs the following:

Credentials for DNS providers must be passed through environment variables.

To display the documentation for a DNS providers:

  $ lego dnshelp -c code

All DNS codes:
  acme-dns, alidns, auroradns, autodns, azure, bindman, bluecat, cloudflare, cloudns, cloudxns, conoha, designate, digitalocean, dnsimple, dnsmadeeasy, dnspod, dode, dreamhost, duckdns, dyn, easydns, exec, exoscale, fastdns, gandi, gandiv5, gcloud, glesys, godaddy, hostingde, httpreq, iij, inwx, joker, lightsail, linode, linodev4, liquidweb, manual, mydnsjp, namecheap, namedotcom, namesilo, netcup, nifcloud, ns1, oraclecloud, otc, ovh, pdns, rackspace, rfc2136, route53, sakuracloud, selectel, stackpath, transip, vegadns, versio, vscale, vultr, zoneee

What did you see instead?

unrecognized DNS provider: cloudflare

How do you use lego?

Binary

Reproduction steps

Version of lego

lego version dev linux/amd64
ldez commented 1 year ago

Hello,

can you provide the whole command line ?

stephen-hill commented 1 year ago
export CLOUDFLARE_DNS_API_TOKEN="<redacted>"
export CLOUDFLARE_ZONE_API_TOKEN="<redacted>"
export LEGO_PATH="/etc/lego"

lego --email webmaster@example.com --dns cloudflare --domains example.com --domains '*.example.com' run
stephen-hill commented 1 year ago

@ldez I have provided full command above, however, I do not think this is an issue with the command but I but in the Debian version of Lego.

ldez commented 1 year ago

Your command line seems right.

yes I think this is a problem with the debian package. We are not maintainers of the package, it's handle by someone outside of the lego team.

Then sorry but I will close this.

I recommend using our binary as a workaround.

stephen-hill commented 1 year ago

@ldez Thanks for letting me know. I have forwarded your reply to the package maintainers.

Just out of interest, do you communicate (have a relationship) with the Debian package maintainers?

ldez commented 1 year ago

We have no relationship with Debian package maintainers then I cannot help.

The Debian package is really old (v3.2.0), I think this package is abandoned.

stephen-hill commented 1 year ago

@ldez I'm sorry to hear that.

Asking a naive question here, but, is this something you could or me could pickup. How easy is it to take over and look after a debian package?

Seems a real shame that such an awesome tool is left abandoned in one of the major linux distros.

ldez commented 1 year ago

How easy is it to take over and look after a debian package?

I don't really know but I think it's complex because each lego dependency seems to need a package and the publication workflow is unclear.

I'm using Linux but I'm not using debian distro based for a long time.