Comment by vbezhenar | Hacker News Reader

Comment by vbezhenar | Hacker News Reader

Parent Full thread

Contrary to popular belief, it might be quite hard to configure it. I spent few days trying to make it work, but I didn't succeed yet. Though my requirements might be a bit atypical. I'm not going to run their software which does too much for my taste, therefore I'm using letsencrypt.sh, which I briefly inspected and I feel comfortable to have full control over process. I don't want to perform domain validation using HTTP, I want to use DNS validation, so I have to write an additional software layer to integrate letsencrypt.sh and my DNS provider API (vultr). And that turns out not so easy.

For me StartSSL was the best offering, but now I need few 3-rd level domains, so letsencrypt seems the only free choice.

To be completely honest, if you're not using the tool Let's Encrypt is creating with the specific intent of making configuration easier, it sounds like a moot point to state that it "might be quite hard to configure it". I'm not saying that your use case is invalid, but starting your comment off with stating that it is hard to configure might throw people off.

I don't think it's too much to expect people to read a single paragraph before jumping to conclusions.

Take a look at lego, it appears to support Vultr's DNS API[1] (and many others).

[1]: https://github.com/xenolf/lego/tree/master/providers/dns/vul...

+1 for lego.

It made things a breeze to configure. I'm now just hoping that ACMESharp will incorporate ACME DNS challenge support soon so that I can automate getting certs for individual machines right on the same box. Imagine: no more complaints of certs when RDPing to machine.

> it might be quite hard to configure it.

I want something completely custom and that's hard therefore Lets Encrypt is too hard.

I was in a similar situation a few months ago, I wanted to update my Route53 DNS and didn't want to trust the magic tool.

I wrote my own simple script in Ruby using the letsencrypt gem and the AWS SDK. It might be a good starting place, feel free to fork and modify it for your own DNS provider.

https://github.com/paul/letsencrypt-route53

Reply on news.ycombinator.com