GitHub Pages: custom-domain certificate stuck in bad_authz, expired cert not renewed (jvmguard.dev)

[ingokegel]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Pages

Body

Repository: jvmguard/jvmguard (Pages site, built with an Actions workflow, CNAME jvmguard.dev)
Site: https://jvmguard.dev/

The Let's Encrypt certificate for the custom domain expired on 2026-10-13 08:01 UTC (it was issued on 2026-07-15) and hasn't been renewed. The Pages API reports the authorization as unrecoverable:

GET /repos/jvmguard/jvmguard/pages
"https_certificate": {
  "state": "bad_authz",
  "description": "The ACME authorization is in a bad state. We need to start over.",
  "domains": ["jvmguard.dev"],
  "expires_at": "2026-10-13"
}

The origin still serves the expired certificate:

subject=CN=jvmguard.dev
issuer=Let's Encrypt YR2
notBefore=Jul 15 08:01:13 2026 GMT
notAfter=Oct 13 08:01:12 2026 GMT

The domain sits behind Cloudflare with SSL mode Full (strict), so every visitor gets HTTP 526 since the expiry. Same pattern as #208641, #204388 and #206054.

What I've tried, following the documented procedure:

1. Pointed the apex directly at Pages (A records 185.199.108-111.153, checked with public resolvers). No CAA records, and the HTTP-01 path answers over plain HTTP without a redirect.
2. Removed and re-added the custom domain several times (Settings -> Pages and via the API). The same bad_authz object with expires_at 2026-10-13 comes back immediately, provisioning never restarts.
3. Switched the CNAME to a different hostname and back, to force a fresh domain record. Same result.

Could someone from the Pages team reset the stuck ACME authorization for jvmguard.dev, so a new certificate can be issued? I'll keep the DNS pointing directly at GitHub Pages (proxy off) while that happens.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐