4 ms·
That's nice for you, but that's not how it is for other people.
by Joeboy 9y ago
That's nice for you, but that's not how it is for other people.
- ryukafalz 9y agoThe tooling around Let's Encrypt is designed to make it possible to do that. If you're not dead set on using a specific web server, there are web servers with Let's Encrypt support out of the box[0]. And if you're using Apache or Nginx, Certbot[1] can configure Let's Encrypt support for them automatically. It's not the "one-click install" you'd get with some other software, but it's pretty close. [0] https://caddyserver.com/ https://caddyserver.com/ [1] https://certbot.eff.org/ https://certbot.eff.org/
- Joeboy 9y agoFWIW I just tried the automatic tooling. First observation is that my email (which was already using LE) still seems to be working, which is honestly surprising but I suppose I should be pleased. My website still seems to redirect a couple of times before ending up back at the unencrypted version. TBF, nothing's conspicuously broken so far so no immediate damage. I'll go back and try to sort it out when I have some more time / enthusiasm. Update: I got it working. I still maintain that it was largely pointless, not zero-effort, and puts the difficulty of running a webserver further into the domain of stuff that's only likely to be undertaken by professional / commercial entities, and that that's a bit of a pity. Update2: Shit, I broke some other stuff :-(
- CiPHPerCoder 9y agoSwitch to Caddy, then. It becomes mind-numbingly easy to setup. https://caddyserver.com/ https://caddyserver.com/