Pages HTTPS certificate stuck in "dns_changed" for 8+ days (support ticket #4948231) #212590
Unanswered
tcbhagat
asked this question in
Other Feature Feedback, Questions, & Ideas
Replies: 3 comments
This comment was marked as spam.
This comment was marked as spam.
|
Thanks for the suggestions. I checked all of them on 10 Nov 2026: CAA: no CAA on constrovet.com; www inherits github.io's CAA, which allows letsencrypt.org. |
0 replies
This comment was marked as low quality.
This comment was marked as low quality.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Pages
Body
Repository: tcbhagat/constrovet-website (GitHub Pro, Pages from branch main). Custom domain: www.constrovet.com.
The Pages API shows https_certificate.state = "dns_changed" ("Detected a change to DNS settings. Requesting a new certificate.") since at least 2 Nov 2026. It was unchanged on 10 Nov 2026 at 04:36 UTC.
"Enforce HTTPS" fails with "The certificate has not finished being issued".
DNS is correct and has not changed since 4 Nov: www is a DNS-only CNAME to tcbhagat.github.io. The Pages health check shows the domain as valid and https eligible, with no CAA error.
The domain already serves a valid Let's Encrypt certificate for www.constrovet.com (issued 19 Oct 2026, expires 17 Jan 2027).
I removed and re-added the custom domain twice (3 Nov 2026, 17:17 and 17:33 UTC), with no change.
Support ticket #4948231 has had no reply since 3 Nov. Could a GitHub staff member reset the certificate request for www.constrovet.com? Thank you.
All reactions