Native ACME support comes to Nginx
letsencrypt.org
Native ACME support comes to Nginx
1–10 of 96 posts
Re: Native ACME support comes to Nginx
#2I have moved most of my personal stuff to caddy, but I look forward to testing out the new release for a future project and learning about the differences in the offerings.
Thanks for this!
Re: Native ACME support comes to Nginx
#3Re: Native ACME support comes to Nginx
#4I'd expect nginx to have this years ago. Is that so hard to implement for some reason?
Re: Native ACME support comes to Nginx
#5What took them so long? Honest question. I'd expect nginx to have this years ago. Is that so hard to implement for some reason?
Re: Native ACME support comes to Nginx
#6What took them so long? Honest question. I'd expect nginx to have this years ago. Is that so hard to implement for some reason?
Re: Native ACME support comes to Nginx
#7What took them so long? Honest question. I'd expect nginx to have this years ago. Is that so hard to implement for some reason?
What does this offer to you vs using a tool such as certbot/cert-manager, and then just referencing the path in nginx?
Re: Native ACME support comes to Nginx
#8What took them so long? Honest question. I'd expect nginx to have this years ago. Is that so hard to implement for some reason?
Related notice: I really enjoy using haproxy for load balancing.
Re: Native ACME support comes to Nginx
#9Re: Native ACME support comes to Nginx
#10Why even bother calling out that it's written in "memory safe Rust code" when the code itself is absolutely riddled with unsafe {} everywhere.
It seems to me that it's written in memory unsafe Rust code.