4 ms·
I'm not going to give them credit for the work that Lets Encrypt did.
by Tostino 11mo ago
I'm not going to give them credit for the work that Lets Encrypt did.
- master_crab 11mo agoI agree, Let’s encrypt and ACME played a massive role. But it’s still far easier having Cloudflare handle TLS encryption for you. And i say this as someone who uses ACME in certmanager and certbot at home and still prefers the ease with which Cloudflare generates a cert for my domain and terminates TLS for the public side of my cloudflare tunnel.
- Tostino 11mo agoFor my home stuff I just use nginx-proxy-manager and haven't thought about it since I set it up a couple of years ago. For work, I used to use certbot directly at my old place. Now I am building my new stuff on k8s, and I have the ingress manage my certs for me (likely using certbot or similar behind the scenes). Both have been extremely low setup effort and no ongoing effort. I don't like giving Cloudflare my (or my companies/customers) data in exchange for being able to click a checkbox.
- TiredOfLife 11mo agoLets Encrypt can proxy my old http only website to show as https? Without access to server configuration? How?
- Tostino 11mo agoWith nginx-proxy-manager which uses Let's Encrypt for certs you can... This isn't the gotcha you think it is.
- TiredOfLife 11mo agoI don't have access to the server.
- Tostino 11mo agoIt can be run anywhere. You don't need it on the same server. Cloudflare isn't running on the same server either.
- TiredOfLife 11mo agoCloudflare is a checkbox.
- Tostino 11mo agoAnd you only let them see every bit of traffic to and from your site in exchange. What a deal. You changed the subject btw.
- TiredOfLife 11mo agoI didn't. I said that Cloudflare is the one that allowed my http only site to become https.
- spoiler 11mo agoMy bad! I slightly confused my timeline. CF offered free certs long before LE!