dehydrated VS certify

From this commit:

https://github.com/dehydrated-io/dehydrated/commit/b116e6bc2...

I've had a lot of success with https://github.com/dehydrated-io/dehydrated . It exposes the different parts of the process (deploy challenge to DNS, deploy cert to filesystem, etc) as hooks, so it's pretty easy to integrate with anything and however you want, if you don't mind writing a bit of bash. There's a few scripts out there that use Cloudflare that you can use as well.

Depend on host's capability... - lego - dehydrated - caddy - in case it already works as a web server, it will automatically issue and renew certs

Take a look at this great project : https://github.com/dehydrated-io/dehydrated/wiki : many dns providers are documented.

> Oh, and that 500-line shell script probably ends up being a 5000-line Python monster anyway.

The dehydrated ACME client is 2400 lines of bash/zsh:

* https://github.com/dehydrated-io/dehydrated

And its external dependencies are OpenSSL and cURL. The acme.sh shell ACME client is 8000 lines of shell:

* https://github.com/acmesh-official/acme.sh

The official Let's Encrypt client is written in Python, and the core 'executable' is much longer, and in addition it pulls in a boatload of dependencies:

* https://packages.debian.org/bullseye/python3-certbot

Dehydrated.io, damn few dependencies.

You're welcome.

https://github.com/dehydrated-io/dehydrated

I prefer dehydrated as an ACME client because it's written in bash and the only dependencies are sed, awk, grep, and openssl. This will also leave you free to customize your nginx config as necessary without having to try to cram your needs into a generator that doesn't account for what you're trying to do. It seems odd to me that the generator would create the intermediary file (as per your quoted output above), but then not put that in the nginx config.

This project has helped us immensely with cert renewals - https://github.com/dehydrated-io/dehydrated

Option 2+: If your public DNS is hosted by a provider that has Win-ACME or Certify the Web support, use Let's Encrypt and automate the whole thing.

I use certify the web for the rd gateway

For Exchange and Remote Desktop Service we are using Certify The Web with Lets Encrypt. Works really well.

Certify the Web: https://certifytheweb.com/

https://certifytheweb.com Felt like a complete bait-and-switch to me.

If you're managing Windows Servers and need certificates on them, ditch what you're doing and get this: https://certifytheweb.com

It's worth doing! A few projects I've done:

I once needed a database of EV charging locations, but at the time(2011) there were no open databases, so I built https://openchargemap.org, that now serves millions of API queries per month for other apps and services

For another project, I recently wanted to control my guitar amp (a Positive Grid Spark) from my computer instead of using a mobile app, so I built https://soundshed.com which is both a bluetooth web app and an electron app you can install. It now has a few thousand users :)

And finally, another time I had some SSL certificates I needed to manage for another project (for the above mentioned https://openchargemap.org), so I built a GUI to manage and renew certificates on Windows. It's now a commercial app with hundreds of thousands of users and it's my full time job: https://certifytheweb.com

So yeah, worth doing!