How We Deliver Global SSL with Let's Encrypt
1–10 of 68 posts
Re: How We Deliver Global SSL with Let's Encrypt
#2Would greatly benefit from explaining why they couldn't do dns-01 challenges successfully.
This an issue all the way from individuals with crappy or misconfigured DNS locally to whole TLDs (fortunately no really major ones) with non-working DNS. But it's often a teachable moment, something others can learn from.
Re: How We Deliver Global SSL with Let's Encrypt
#3Would greatly benefit from explaining why they couldn't do dns-01 challenges successfully. This an issue all the way from individuals with crappy or misconfigured DNS locally to whole TLDs (fortunately no really major ones) with non-working DNS. But it's often a teachable moment, something others can learn from.
I'd like to see that too, especially since I've been doing fully-automated Let's Encrypt with dns verification for hosted domains for well over a year now. I might be able to offer a solution to whatever issue they've had.
Re: How We Deliver Global SSL with Let's Encrypt
#4Would greatly benefit from explaining why they couldn't do dns-01 challenges successfully. This an issue all the way from individuals with crappy or misconfigured DNS locally to whole TLDs (fortunately no really major ones) with non-working DNS. But it's often a teachable moment, something others can learn from.
DNS challenges weren't broken, they technically worked just fine. But they added an additional step to our setup process, and we were losing customers during signup because of it. We can still do the DNS challenge it's just not how we guide people through our setup.
Basically with the DNS challenge, we had to send people away to make DNS changes, have them come back and confirm they were approved, and then we sent them away _again_ to make another DNS change. It was kind of brutal.
(edit: we also tweaked the article to not imply "broken"!)
Re: How We Deliver Global SSL with Let's Encrypt
#5Would greatly benefit from explaining why they couldn't do dns-01 challenges successfully. This an issue all the way from individuals with crappy or misconfigured DNS locally to whole TLDs (fortunately no really major ones) with non-working DNS. But it's often a teachable moment, something others can learn from.
DNS challenges weren't broken, they technically worked just fine. But they added an additional step to our setup process, and we were losing customers during signup because of it. We can still do the DNS challenge it's just not how we guide people through our setup. Basically with the DNS challenge, we had to send people away to make DNS changes, have them come back and confirm they were approved, and then we sent th…
So typical user engagement/onboarding complexity funnel issues not something inherent to the DNS/LE/Fly.
Re: How We Deliver Global SSL with Let's Encrypt
#6Would greatly benefit from explaining why they couldn't do dns-01 challenges successfully. This an issue all the way from individuals with crappy or misconfigured DNS locally to whole TLDs (fortunately no really major ones) with non-working DNS. But it's often a teachable moment, something others can learn from.
DNS challenges weren't broken, they technically worked just fine. But they added an additional step to our setup process, and we were losing customers during signup because of it. We can still do the DNS challenge it's just not how we guide people through our setup. Basically with the DNS challenge, we had to send people away to make DNS changes, have them come back and confirm they were approved, and then we sent th…
Why would you need to send them away twice for DNS changes?!
Re: How We Deliver Global SSL with Let's Encrypt
#7LE is awesome.
Clients want an SSL server and it lets me set it up in 10 minutes without additional costs.
Re: How We Deliver Global SSL with Let's Encrypt
#8Interesting 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.
Re: How We Deliver Global SSL with Let's Encrypt
#9Earlier quoted context omitted.
DNS challenges weren't broken, they technically worked just fine. But they added an additional step to our setup process, and we were losing customers during signup because of it. We can still do the DNS challenge it's just not how we guide people through our setup. Basically with the DNS challenge, we had to send people away to make DNS changes, have them come back and confirm they were approved, and then we sent th…
Why would you need to send them away twice for DNS changes?!
I'm assuming mrkurt meant that you send your users once to create a dns record (in case you haven't already) - you can add any hostname you want on Fly, it doesn't have to exist, yet. Then you go and create a DNS challenge for Let's Encrypt. Obviously, these 2 steps are orthogonal, but this is the reality of user onboarding.
Re: How We Deliver Global SSL with Let's Encrypt
#10Interesting 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.
I agree with the pricy bit. I've made a calculation, and it would cost me 1200$ a month to run what Cloudflare does for free.
Now, I get that free is not an option. 50/100$ a month is probably OK. But that's beyond reasonable. And prices change depending on where people visit you from (!?)