4 ms·

Anyone looking to use Let's Encrypt and free to make choices regarding their server may want to check out https://caddyserver.com/ https://caddyserver.com/ -- i

Anyone looking to use Let's Encrypt and free to make choices regarding their server may want to check out https://caddyserver.com/ https://caddyserver.com/ -- it has Let's Encrypt support baked right in.

geostyx 11y ago
Caddy is working really well for me. Way easier than nginx to setup, and TLS is on by default.
recursive 11y ago
Wow, this is awesome. I had been assuming letsencrypt supported only Unixy operating systems. Most of the web hosts I care about necessarily run Windows, so I thought letsencrypt was out of reach. I wonder how they did this.
- simoncion 11y ago
  > I wonder how they did this. The ACME protocol is simple and fully documented: https://letsencrypt.github.io/acme-spec/ https://letsencrypt.github.io/acme-spec/
pilif 11y ago
I've said it before when caddy was last mentioned, but this is how I want Let's Encrypt to work with all web servers. Yes. That includes the big ones like nginx, apache and even IIS. By default, all that's needed is to turn on ssl and you'll be up and running - including a let's encrypt certificate. Following this vision is why I believe that let's encrypt limited the validity period of their certs (in addition to some security benefits and much lower OCSP load): Once the integration into clients has proceeded to this level where caddy is showing us it's going to, then even quicker expirations would become feasible - heck even as low as a week or so. So, while I'm not planning on using caddy any time soon (I don't see a benefit to switching away from nginx right now), I applaud caddy for showing everyone how this should be done. A huge thank you to the author. This goes to show how very important UX is even for backend-y stuff.
- xt 11y ago
  I've been working on a script that does this within Nginx. See https://github.com/torhve/lua-resty-letsencrypt https://github.com/torhve/lua-resty-letsencrypt It's not quite production ready but it shows you it's technically possible
- mholt 11y ago
  Thank you for your kind remarks. :) It goes a long way to keeping the burnout away.
hackerboos 11y ago
Dokku's Letsencrypt plugin is also very simple to use. https://github.com/dokku/dokku-letsencrypt https://github.com/dokku/dokku-letsencrypt
embik 11y ago
Caddy sounds great but I'm a bit worried by the fact it does not offer repositories for major Linux distributions. Shouldn't a component that important for public facing servers be included in standard software updating processes?
- nitrogen 11y ago
  In my experience it's not typical for web infrastructure to come from distro packages, unfortunately.

geostyx 11y ago

Caddy is working really well for me. Way easier than nginx to setup, and TLS is on by default.

recursive 11y ago

Wow, this is awesome. I had been assuming letsencrypt supported only Unixy operating systems. Most of the web hosts I care about necessarily run Windows, so I thought letsencrypt was out of reach. I wonder how they did this.

simoncion 11y ago
> I wonder how they did this. The ACME protocol is simple and fully documented: https://letsencrypt.github.io/acme-spec/ https://letsencrypt.github.io/acme-spec/

pilif 11y ago

I've said it before when caddy was last mentioned, but this is how I want Let's Encrypt to work with all web servers. Yes. That includes the big ones like nginx, apache and even IIS. By default, all that's needed is to turn on ssl and you'll be up and running - including a let's encrypt certificate. Following this vision is why I believe that let's encrypt limited the validity period of their certs (in addition to some security benefits and much lower OCSP load): Once the integration into clients has proceeded to this level where caddy is showing us it's going to, then even quicker expirations would become feasible - heck even as low as a week or so. So, while I'm not planning on using caddy any time soon (I don't see a benefit to switching away from nginx right now), I applaud caddy for showing everyone how this should be done. A huge thank you to the author. This goes to show how very important UX is even for backend-y stuff.

xt 11y ago
I've been working on a script that does this within Nginx. See https://github.com/torhve/lua-resty-letsencrypt https://github.com/torhve/lua-resty-letsencrypt It's not quite production ready but it shows you it's technically possible
mholt 11y ago
Thank you for your kind remarks. :) It goes a long way to keeping the burnout away.

hackerboos 11y ago

Dokku's Letsencrypt plugin is also very simple to use. https://github.com/dokku/dokku-letsencrypt https://github.com/dokku/dokku-letsencrypt

embik 11y ago

Caddy sounds great but I'm a bit worried by the fact it does not offer repositories for major Linux distributions. Shouldn't a component that important for public facing servers be included in standard software updating processes?

nitrogen 11y ago
In my experience it's not typical for web infrastructure to come from distro packages, unfortunately.