HTTPS certificate stuck in "new" state for 9 days (custom domain, DNS checks all pass) #212659
Replies: 2 comments
|
I checked your setup from outside and the DNS really is right: the apex has the four GitHub A records, One thing you have not tried yet: set the custom domain to the apex instead of www.
Right now your certificate request lists only If it is still at |
|
Update (Nov 13, 2026): Thank you, @Akshay-cp7, for the suggestion. On Nov 12 at about 07:00 UTC, I changed the custom domain in Settings → Pages from www.hanno-insatsu.jp to the apex, hanno-insatsu.jp, and left DNS unchanged. The certificate state then moved from "new" to "dns_changed", but it has stayed at "dns_changed" since then. I checked the Pages API every 20 minutes until Nov 13, 09:00 UTC (about 26 hours), and it never reached "approved" or "issued". HTTPS still cannot be enforced. The certificate has now been stuck for 12 days in total, and the DNS still matches GitHub's documentation (4 A records on the apex, www CNAME to the github.io host, no AAAA, no CAA). Could a GitHub staff member please re-trigger or clear the certificate request for hanno-insatsu.jp (repository: yhdog0425-eng/hanno-insatsu)? Thank you. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Pages
Body
Hello,
The HTTPS certificate for my GitHub Pages custom domain has not been issued for 9 days.
GitHub Support closed my ticket (#4967482) and pointed me here, so I am asking the community.
Setup
Current state (2026-11-11)
https_certificate.state: "new" ("This domain was recently added. The certificate request process will begin shortly.")https_enforced: false (the "Enforce HTTPS" checkbox cannot be enabled)is_valid: trueandis_https_eligible: true;https_error: "peer_failed_verification"What I have tried
Is there anything else I can do on my side, or does the certificate request need to be re-triggered by GitHub staff?
Any advice would be appreciated. Thank you.
All reactions