Trying to enforce https button grayed out #209568
Replies: 1 comment 1 reply
|
The repository CNAME file only declares the custom hostname; it does not issue the certificate. Please verify the authoritative DNS for both names: @ should have exactly the four Pages A records (185.199.108.153, .109, .110 and .111), with no extra A/AAAA/ALIAS/ANAME records, and www should be a single CNAME directly to greg-aborgata.github.io. Also check for a CAA record that could block the certificate authority, and query the authoritative nameservers rather than only a recursive resolver. If DNS is consistent and the Pages domain check remains successful but HTTPS is still unavailable after propagation, the certificate job is likely stuck on GitHub’s side; avoid repeatedly removing/re-adding the domain and include the DNS check timestamp when contacting GitHub Support. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Code Search and Navigation
Body
Hello, I’m setting up GitHub Pages for the custom domain aborgata.com. My DNS is correctly configured:
aborgata.com resolves to GitHub Pages IPs
www.aborgata.com resolves to greg-aborgata.github.io
I’ve also added the repository CNAME file with:
aborgata.com
However, GitHub Pages still reports:
“Unavailable for your site because your domain is not properly configured to support HTTPS (aborgata.com)”
I’ve waited more than 24 hours and the issue persists. The site is configured in GitHub Pages and the DNS appears correct, so this appears to be on the GitHub side.
All reactions