| ▲ | endorphine a day ago |
| 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? |
|
| ▲ | aaronax a day ago | parent | next [-] |
| Slow adoption of ACME by corporate customers that pay the bills. Must be a bigger effort than one would initially think, too. |
|
| ▲ | lysace a day ago | parent | prev | next [-] |
| 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. |
| |
| ▲ | senko a day ago | parent | next [-] | | Looks like haproxy also doesn't support it natively. (unless I'm googlin' it wrong - all info points to using with acme.sh) | |
| ▲ | jsheard a day ago | parent | prev | next [-] | | See also: nginx's HTTP/3 support still being experimental, when pretty much every other server besides Apache shipped it years ago. | | |
| ▲ | a day ago | parent | next [-] | | [deleted] | |
| ▲ | everfrustrated a day ago | parent | prev [-] | | Yes tho the odds are anybody wanting http3 likely also using a cdn. There aren't too many cdns which support http3 back to origin. Heck most of them don't even support ipv6-only origins. |
| |
| ▲ | Graphon1 a day ago | parent | prev [-] | | No love for caddyserver? | | |
|
|
| ▲ | preisschild a day ago | parent | prev [-] |
| What does this offer to you vs using a tool such as certbot/cert-manager, and then just referencing the path in nginx? |
| |
| ▲ | aargh_aargh a day ago | parent | next [-] | | One less program to install, configure, upgrade, watch vulnerabilities in, monitor. | | |
| ▲ | benwilber1 a day ago | parent [-] | | All of those things also apply to this module since it's an extra module that you have to install separate. It's not included with the nginx base distribution. You have to configure it specifically, you have to monitor it. You have to upgrade and watch for vulnerabilities. |
| |
| ▲ | petre a day ago | parent | prev [-] | | Not needing a python interprter and setting up cron jobs? The sole reason for using Caddy really, because it's just install and forget. I never had an expired certificate with it. I don't want to mess with an entirely different webserver config either after having fully configured my nginx instances. Too bad they wrote it in rust instead of C, now I need another compiler to build it. Minor nuisance. Hopefully it will get packaged. |
|
