11–20 of 50 posts
I was hoping this was an nginx module where you could specify something like `ssl_letsencrypt on;` and be done with it.
I was hoping this was an nginx module where you could specify something like `ssl_letsencrypt on;` and be done with it.
Caddy has this feature and it's amazing. https://caddyserver.com/docs/automatic-https
All other web servers I looked at (nginx, apache, lighttpd) still require at least a reload for an updated certificate and a configuration file change for a new certificate to be used.
I wonder how caddy works with the very low 5 certificates per public suffix and week limit. Does it automatically bundle domains and request a single certificate with SANs?
I was hoping this was an nginx module where you could specify something like `ssl_letsencrypt on;` and be done with it.
I think its not gona be easy as that - there has to be some croned process and some kind of error handling. (I created https://hub.docker.com/r/analogic/lemanager/ which does both but i am still waiting for some better "native" solution)
Earlier quoted context omitted.
Caddy has this feature and it's amazing. https://caddyserver.com/docs/automatic-https
Wow. I might check try it out then.
https://github.com/Xe/dotfiles/tree/master/ansible/roles/cad...
Earlier quoted context omitted.
Caddy has this feature and it's amazing. https://caddyserver.com/docs/automatic-https
this is how it should work. Very nice. I can't wait for other web servers to gain this ability too. Or at least allow us to load certificates from dynamic locations based on some request data. All other web servers I looked at (nginx, apache, lighttpd) still require at least a reload for an updated certificate and a configuration file change for a new certificate to be used. I wonder how caddy works with the very low…
Yeah, Caddy is amazing. Matt is doing an awesome job with it.
> I wonder how caddy works with the very low 5 certificates per public suffix and week limit. Does it automatically bundle domains and request a single certificate with SANs?
I directed Matt to this discussion so I hope can answer these questions for you. I unfortunately cannot.
Earlier quoted context omitted.
Caddy has this feature and it's amazing. https://caddyserver.com/docs/automatic-https
this is how it should work. Very nice. I can't wait for other web servers to gain this ability too. Or at least allow us to load certificates from dynamic locations based on some request data. All other web servers I looked at (nginx, apache, lighttpd) still require at least a reload for an updated certificate and a configuration file change for a new certificate to be used. I wonder how caddy works with the very low…
Thanks for your comments; glad you like the way we integrated it!
> Does it automatically bundle domains and request a single certificate with SANs?
No, as it turns out, SAN makes the auto-management code highly complicated, since names could overlap in different certs, etc. It also complicates renewals and gives more room for error (e.g. 49 of the domains verify but 1 fails, so the cert can't be renewed). So I've opted not to support SAN certificates for the automatic HTTPS feature. But you can of course still issue your own SAN certificates and use those.
Right now, Caddy reloads itself when it renews certificates, but as of Caddy 0.8.2 (slated for release any day now), Caddy will do it all in-process, no reloading.
I was hoping this was an nginx module where you could specify something like `ssl_letsencrypt on;` and be done with it.
Or better yet, make "ssl_letsencrypt on;" the default. Make it so that newbies can just apt-get install nginx/apache/lighttpd/etc. and have https up and running, no questions asked. The real reason https adoption isn't up to par has less to do with people not willing to spend money, and more because it's not up by default. Now that https is free, please make it enabled by default.