---
title: "Discussion on \"The wildcard cert saga — eight days from expiry, three failed attempts, one flag\" | Hashnode"
description: "Discussion on \"The wildcard cert saga — eight days from expiry, three failed attempts, one flag\". Eight days from expiry, three failed renewal attempts across cert-manager and acme.sh. The fix was two DNS records and one flag, once reframed."
url: "https://hashnode.com/posts/wildcard-cert-renewal-dns-alias/6a909397f96af761e75c496a"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The wildcard cert saga — eight days from expiry, three failed attempts, one flag](https://jjozzietech.hashnode.dev/wildcard-cert-renewal-dns-alias?utm_source=hashnode&utm_medium=feed)

Eight days from expiry, three failed renewal attempts across cert-manager and acme.sh. The fix was two DNS records and one flag, once reframed.

Aug 27 · 21 min read · jjozzietech.hashnode.dev  
Read the article

-   [#kubernetes](https://hashnode.com/tag/kubernetes)
-   [#homelab](https://hashnode.com/tag/homelab)
-   [#devops](https://hashnode.com/tag/devops)
-   [#cloudflare](https://hashnode.com/tag/cloudflare)
-   [#letsencrypt](https://hashnode.com/tag/letsencrypt)

## Written by

[JJozzieTech](https://hashnode.com/@jjozzietech)

@jjozzietech · Sydney, Australia

  
[View profile](https://hashnode.com/@jjozzietech)

Enterprise lab. Sydney rack. I write about what actually breaks.

Sydney-based infrastructure operator. Enterpriselab, DePIN workloads, and the incident logs behind them. I write about what actually breaks.

## Responses 1

Markdown supported · ⌘↵ to post

[Node Edge Ops](https://hashnode.com/@nodeedgeops)

[Oct 30](https://hashnode.com/posts/wildcard-cert-renewal-dns-alias/6a909397f96af761e75c496a/comment/6ae520e99e7c87c38ce3ca7c)

For wildcards I prefer DNS-01 with a dedicated ACME challenge CNAME so renewals do not touch the edge nginx config. Keep the auth hook idempotent and verify TXT before calling certbot renew --dry-run.
