GitHub Pages custom-domain certificate still new 65 hours after full Pages reset #213492
Replies: 1 comment
|
Thank you for your interest in contributing to our community! We currently only accept discussions created through the GitHub UI using our provided discussion templates. Please re-submit your discussion by navigating to the appropriate category and using the template provided. This discussion has been closed because it was not submitted through the expected format. If you believe this was a mistake, please reach out to the maintainers. |
0 replies
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.
My GitHub Pages site at www.subwire.net (alternate hostname subwire.net) has not received a working HTTPS certificate since its migration on November 1, 2026.
The source repository is private. Actions builds and deployments succeed, and the site serves over HTTP. Both HTTPS hostnames fail certificate hostname validation (curl error 60).
Current DNS:
GitHub's Pages health endpoint reports both hostnames as is_valid=true, is_served_by_pages=true, is_https_eligible=true, with caa_error=null.
Troubleshooting history:
Could a GitHub Pages staff member inspect or restart the underlying certificate-provisioning job, or identify a validation failure not exposed by the Pages API? We have retained timestamped API/DNS diagnostics and the reset history and can provide these through a private support channel.
All reactions