Resolving GitHub Pages TLS Stuck Issues: A Community Insight for Your Software Project Dashboard

Setting up custom domains for GitHub Pages can sometimes present unexpected challenges, particularly when it comes to TLS certificate provisioning. A recent discussion on the GitHub Community forum highlighted a common frustration: a custom domain's TLS certificate getting stuck in a "dns_changed" state, preventing secure access to what might be a crucial software project dashboard or public-facing site.

The Case of the Stuck TLS Certificate

User junteakim reported an issue while migrating their GitHub Pages site, junteakim/sps-company-website, to the custom domain smc12puls.com. While HTTP access worked perfectly, the custom-domain TLS certificate remained unavailable. The GitHub Pages settings indicated "DNS check successful" but the TLS certificate was stuck at "1 of 3 - Certificate Requested: Detected a change to DNS settings." This status persisted despite extensive external verification confirming correct DNS configuration:

• Apex ALIAS @ pointing to junteakim.github.io.
• www CNAME pointing to junteakim.github.io.
• All authoritative nameservers (ns-cloud-c1/c2/c3/c4.googledomains.com) correctly resolving to GitHub Pages IPv4 and IPv6 addresses.

Despite these clear external checks, the site continued to present the default *.github.io certificate, not the custom one. Compounding the issue, the Pages DNS check intermittently reported "Domain does not resolve to the GitHub Pages server. (NotServedByPagesError)," conflicting with all independent external validations.

Troubleshooting Attempts and What Not to Do

Following official documentation, junteakim attempted to resolve the issue by removing and re-adding the custom domain. While this reset the provisioning process, the TLS certificate remained stuck at "1 of 3." This highlights a critical point in troubleshooting:

• Avoid Repeated Resets: As community member jovanovic-djo advised, repeatedly removing and re-adding the domain can restart the provisioning process each time and potentially lead to rate limits, further delaying resolution.

The Recommended Solution: Engage GitHub Support

When external DNS checks are flawless and the internal GitHub Pages status remains stuck, it often indicates an internal platform issue that requires direct intervention. The recommended course of action is to:

1. Open a Support Ticket: Contact GitHub Support at support.github.com.
2. Provide Key Details: Include the repository name (e.g., junteakim/sps-company-website), the custom domain (smc12puls.com), and the exact status message ("Certificate Requested: Detected a change to DNS settings") along with the timestamp when this status was first observed.

Once the certificate is successfully issued by GitHub Support, remember to:

• Enable Enforce HTTPS: This ensures all traffic to your custom domain is secure.
• Trigger a New Pages Build: If redirects don't kick in immediately, a small commit to your repository can trigger a new build and refresh the Pages configuration.

Developer Productivity Takeaway

This scenario underscores the importance of understanding platform-specific behaviors. For engineering teams relying on GitHub Pages for their software project dashboard, documentation, or public-facing applications, such blockers can impact project visibility and perceived reliability. Timely resolution of these infrastructure issues is crucial for maintaining high performance development software practices and ensuring accurate metrics for engineering teams are not skewed by preventable downtime. Knowing when to escalate to support rather than endlessly troubleshooting external configurations is a key productivity insight.