Earlier quoted context omitted.
txt records are the only way to do the dns-01 challenge with certbot/Let's Encrypt. The http-01 challenge is simpler, we can get people setup with one CNAME/A-record. Once we're serving traffic, we can do all renewals with an http challenge and they don't need to change DNS ever again.
This is an often overlooked option, but you can indeed solve the DNS challenge by having someone create a CNAME record for _acme-challenge.example.com that points to a domain under your control, and then serve the TXT record needed to verify the challenge from that domain. acme-dns[1] provides a nice implementation of this idea, as well as a more detailed explanation. [1]: https://github.com/joohoi/acme-dns
How We Deliver Global SSL with Let's Encrypt
61–68 of 68 posts
Re: How We Deliver Global SSL with Let's Encrypt
#62Earlier quoted context omitted.
We wouldn't need to have this conversation if the title said TLS.
You're correct, but you're fighting an uphill battle: https://certsimple.com/blog/ssl-or-tls
Re: How We Deliver Global SSL with Let's Encrypt
#63Earlier quoted context omitted.
Yes this is a delight compared to the old way of having to hand over $10 or whatever to someone for a certificate that one had to remember to renew in a timely fashion versus just using a cron job now with LE.
Right?! "Sure I won't think about this for a year, then I'll remember it 30 days before I need to have it fixed, it'll be great".
I don't mind offering 90 day certificates, but requiring it goes against the offered reason of LE to expand HTTPS.
Re: How We Deliver Global SSL with Let's Encrypt
#64Re: How We Deliver Global SSL with Let's Encrypt
#65Completely unrelated, what is the blog framework / cms you are using the the fly.io blog? It is amazing!
Re: How We Deliver Global SSL with Let's Encrypt
#66Completely unrelated, what is the blog framework / cms you are using the the fly.io blog? It is amazing!
Thanks! We're using ghost.org and of course all our illustrations are done by Annie ( https://twitter.com/annieruygt ) :)
Re: How We Deliver Global SSL with Let's Encrypt
#67Interesting product - fly.io It’s essentially a reverse proxy as a service. Sort of like Cloudflare but with what looks like a nicer API, and custom domain name SSL eg. for multi tenant apps. It was a bit pricy when I plugged in how many requests we get per month on our servers, easily in 5-figure per month. Having said that, internally we built most of their selling points already.
Custom domain name SSL is also provided by Cloudflare, it's called "SSL for SaaS".