GitHub Pages custom domain mrxpanel.com stuck on DNS Check in Progress; www serves wrong TLS certificate #211218
Replies: 1 comment
|
The read-only view you asked for is the Pages REST endpoint, and it already names the state. The repo is public, so no token is needed: curl -s https://api.github.com/repos/kriswantoro82-sys/mrxpanel-root-redirect/pagesRight now it returns: "https_certificate": {
"state": "dns_changed",
"description": "Detected a change to DNS settings. Requesting a new certificate.",
"domains": ["mrxpanel.com"],
"expires_at": "2026-12-12"
},
"https_enforced": false
As admin you can also call The documented way out of a stuck request is the single reset you were holding back: when provisioning has not finished "several minutes after you clicked Save", click Remove, retype the domain, Save, which "will cancel and restart the provisioning process" (Troubleshooting certificate provisioning). Once, not in a loop. Pick a quiet window: between Remove and Save the apex returns GitHub's 404, and the docs allow up to an hour for HTTPS afterwards (HTTPS errors); I have not timed it. Poll the |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Pages
Body
Problem
Repository: https://github.com/kriswantoro82-sys/mrxpanel-root-redirect
Configured Pages domain:
mrxpanel.com(published frommain; CNAME file matches).On 25 October 2026, Settings → Pages still shows DNS Check in Progress, TLS certificate is being provisioned / Certificate Requested, and Enforce HTTPS is unavailable.
https://mrxpanel.com/works with a valid TLS certificate formrxpanel.com(Sep 13–Dec 12, 2026), buthttps://www.mrxpanel.com/presents the fallback*.github.iocertificate that does not containwww.mrxpanel.comin its SAN. Standard TLS verification fails.Checks performed
185.199.108.153,.109.153,.110.153,.111.153; no conflicting apex AAAA.www.mrxpanel.comCNAME →kriswantoro82-sys.github.io.wwwpermits Let's Encrypt.wwwHTTP redirects to http://mrxpanel.com/, andwwwHTTPS fails hostname validation.Independent CI evidence (redirect check correctly FAILS; certificate-inspection step PASS): https://github.com/kriswantoro82-sys/mrxpanel-job-staging/actions/runs/40163587654
Technical diagnostics and read-only evidence: kriswantoro82-sys/mrxpanel-root-redirect#10 (comment)
Question
What GitHub Pages DNS-validation or certificate-binding state could leave the
wwwhostname serving the default certificate when the apex hostname already has a valid certificate? Is there a read-only way to determine the failing validation before a single remove/re-add of the custom domain? We have intentionally not repeatedly reset the domain or changed DNS to avoid downtime.Thanks for guidance from Pages maintainers or anyone who has resolved this issue.
All reactions