Mailcow-dockerized: Let's encrypt wildcard with cloudflare dns validation

[samuelebistoletti]

Hi,
Any plan to support wildcard certificate validation with cloudflare certbot plugin?
Would be very nice and useful to validate certificates using dns instead of webserver root. In my case I have a reverse proxy in front of all infrastructure, I have to pass specific locations to validate certificates, instead with dns validation I wouldn't have to expose specific routes.

Thanks

[andryyy]

Yes, but no eta. :-(

[itsbhanusharma]

+1 for this! will be very helpful

[germanosbh]

+1 for this!

[bprfh]

maybe I'm wrong one, but if you use acme.sh can't you simply request the certs and have the reverseproxy in front?
acme.sh supports cloudflare as well as most of the other providers

[andryyy]

Sure. With a RP in front of mailcow, you can do whatever you want. Just copy the certs in a post-hook to data/assets/ssl.

[JustAB0x]

+1 for this! Would be hella useful!

[andryyy]

And when using multiple domains from different providers?

I don’t think it is that useful. Just use a rp, maybe even HAProxy in front of it. :)

Will give it a try with our Servercow API.

[greenmoss]

Added a bounty: https://www.bountysource.com/issues/69319873-let-s-encrypt-wildcard-with-cloudflare-dns-validation

[MAGICCC]

Well first the whole LE step needs to be modified to actually support DNS-01 validation

[mamash]

I don't have capacity to do the mailcow integration, but adferrand/docker-letsencrypt-dns works great, taking advantage of the (Python) lexicon library/tool to support a variety of DNS providers.

I'm using it on another node that runs my family & friends websites (similar to how mailcow runs the mail).

[MAGICCC]

Well there are lot of LE helper, but the integration is the difficult part

[greenmoss]

This is what I'm using for now: https://gist.github.com/greenmoss/8ee9d4acd3a21df699cde2225a78399e

Assumes mailcow, etc, so maybe useful for future integration reference.