Live data from Hacker News

Native ACME support comes to Nginx

letsencrypt.org

1–10 of 96 posts

Re: Native ACME support comes to Nginx

#2
Congratulations to the folks involved. I'm sure this wasn't a trivial lift. And the improvement to free security posture is a net positive for our community.

I 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

#3
Hey, I just decided to run a DNS server and a couple of web services on my lan from a raspberry pi over the weekend. I used Nginx for the reverse proxy so all of the services could be addressable without port numbers. It was very easy to set up, it's funny how when you learn something new, you start seeing it all over the place.

Re: Native ACME support comes to Nginx

#7

What 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?

One less program to install, configure, upgrade, watch vulnerabilities in, monitor.

Re: Native ACME support comes to Nginx

#8

What took them so long? Honest question. I'd expect nginx to have this years ago. Is that so hard to implement for some reason?

Nginx is now owned by F5. Big, expensive and amazingly slow in terms of development.

Related notice: I really enjoy using haproxy for load balancing.

Re: Native ACME support comes to Nginx

#10
> the popular open source web server NGINX announced support for ACME with their official ngx_http_acme module (implemented with memory safe Rust code!).

Why 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.

Post reply on HN