[CLSTR]
< Back to situations

Monitor this situation.

[SITUATION] · [ACTIVE] · [TECHNOLOGY]

2 clusters · 3 sources · 3 days · First seen · Last updated

Automated TLS certificate management adoption

Overview

The introduction of Let’s Encrypt and the ACME protocol has enabled the automation of X.509 certificate management, aiming to replace manual HTTPS certificate processes with automated creation and retrieval.

This automation has contributed to a shift in the web server landscape, with the Caddy server gaining adoption as an alternative to Nginx. While Nginx typically requires external tools like Certbot and manual cron jobs for renewals, Caddy provides native TLS management through providers such as Let’s Encrypt and ZeroSSL. Although Nginx is noted for lower idle RAM usage due to its C-based architecture, Caddy is gaining traction in DevOps and self-hosting environments due to its ease of configuration, native HTTP/3 support, and reduced operational overhead.

Entities

ZeroSSL · Let's Encrypt · Caddy · Smallstep · ACME

Timeline

  1. 7 days ago

    [TECHNOLOGY] 2 sources
    Caddy gains adoption over Nginx through automated TLS management

    Caddy is gaining adoption over Nginx due to its native, automated TLS certificate management via ACME and its user-friendly configuration compared to Nginx's manual setup requirements.

  2. 9 days ago

    [TECHNOLOGY] 2 sources
    Let's Encrypt and ACME protocol enable automated HTTPS certificate management

    Let's Encrypt and the ACME protocol are enabling automated HTTPS certificate management, with tools like Caddy providing seamless TLS issuance and renewal for both public and local domains.

Sources

blog.josefsson.org · dev.to · technewsdaily.com