Recommendation vs joohoi/acme-dns-certbot-joohoi

[crisperdue]

Question: Do you now recommend this software versus joohoi/acme-dns-certbot-joohoi?
They appear to be direct alternatives, or is that incorrect?

Thanks!

[joohoi]

They are direct alternatives, you are right. And yes, this was written to replace the python wrapper. This client addresses many shortcomigs of acme-dns-certbot-joohoi

…

On Wed 23. Jun 2021 at 22.54, Cris Perdue ***@***.***> wrote: Question: Do you now recommend this software versus joohoi/acme-dns-certbot-joohoi? They appear to be direct alternatives, or is that incorrect? Thanks! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#9>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABH6DJOOIJBIFEV2SBVHLQ3TUI3XFANCNFSM47GPDJ2Q> .

[crisperdue]

Thanks much, that is very helpful info.

For what it's worth, there is a tutorial on using the old Python version,
at https://www.digitalocean.com/community/tutorials/how-to-acquire-a-let-s-encrypt-certificate-using-dns-validation-with-acme-dns-certbot-on-ubuntu-18-04.

Perhaps the author would be interested in creating an updated tutorial when you feel your new software is ready for more widespread use.

[oblitum]

By looking at old Python code version, it seems to avoid issue #13:

• https://github.com/joohoi/acme-dns-certbot-joohoi/blob/908aefb0ea3925aaeaf78a7ca32e6a526b1bb563/acme-dns-auth.py#L122-L123

It's a problematic issue with the new go client which may affect usage with most registrars when attempting to obtain a wildcard certificate.

[joohoi]

That's a good observation @oblitum , I'll fix that in Go client!

[joohoi]

...and it's fixed

[lonix1]

Does this new client have dockerised deployment or must we manage scripts etc. manually? (Sorry, I'm new to this, but long-time user of certbot.)