Pages TLS Provisioning Stuck - [www.saumyadas.com.np]

[SaumyaKumarDas]

Why are you starting this discussion?

Question

What GitHub Actions topic or product is this about?

General

Discussion Details

TLS certificate is showing Certificate Request Error, wait for 15 minutes but it has been 24 hours now, it still is showing the same problem. Please look into it.

[anyexpjay]

Hi, thanks for bringing this up.

This issue is related to GitHub Pages TLS / HTTPS certificate provisioning, not a problem with GitHub Actions workflows themselves.
In most cases, the “Certificate Request Error” resolves automatically within 15 minutes. However, if it persists for more than 24 hours, it usually indicates a configuration or DNS-related issue rather than a transient delay.

From my experience, the most common causes are:

• A recent change to the custom domain or DNS records
• An incorrect or missing CNAME / A / AAAA record
• A mismatch between the domain configured in GitHub Pages and the actual DNS target
• DNS propagation still being incomplete or cached incorrectly

At this point, the recommended steps are:

1. Re-verify the DNS configuration for the domain and ensure it points correctly to GitHub Pages.
2. Remove the custom domain from GitHub Pages, wait a few minutes, and then add it back.
3. Make sure there are no conflicting DNS records (especially multiple CNAMEs or mixed A records).
4. Confirm that HTTPS is enabled after the domain is correctly recognized.

Once the DNS configuration is correct, GitHub will automatically reattempt certificate issuance — no manual action is required beyond that.
We’re actively reviewing this from our side as well, but in nearly all cases like this, correcting the domain/DNS setup resolves the issue.
Feel free to share the domain details if you’d like us to take a closer look.

[TheCHARIITH]

The "Certificate Request Error" can occur due to several reasons, such as issues with the certificate authority, DNS misconfigurations, or problems during the certificate issuance process. Here are a few steps you can try to troubleshoot:

1. Check DNS Configuration: Ensure that your DNS records (especially CNAME or A records) are set correctly, and the domain is pointing to the right server.

2. Verify Certificate Authority: Ensure you're using a trusted certificate authority (CA) and the certificate is issued for the correct domain.

3. Re-request the Certificate: Sometimes, re-triggering the certificate request in your platform or service (e.g., GitHub Actions, a web hosting service) can resolve the issue.

4. Check for Platform Outages: Look into whether there are any ongoing issues with the service you're using (GitHub, your certificate provider, etc.).

5. Ensure Proper Configuration: Double-check the configuration files (e.g., for web servers or SSL/TLS settings) to ensure everything is set correctly.

If none of these steps work, you might want to reach out to GitHub support or your certificate provider to check if there are any issues on their end.

[SaumyaKumarDas]

Hi there, Thanks for your response in short notice. My DNS configuration is correct and there is no issue as such. Still it is showing "Certificate Request Error". It is been more than 24 hours from now. Still TLS certificate is not working. I have attached the screenshot of my CNAME / A / AAAA record in this mail. Please take a closer look. It seems the TLS certificate is stuck from Github side. Thanks and regards, Saumya Kumar Das

…

On Sun, 4 Jan 2026 at 20:57, THE CHARITH ***@***.***> wrote: The "Certificate Request Error" can occur due to several reasons, such as issues with the certificate authority, DNS misconfigurations, or problems during the certificate issuance process. Here are a few steps you can try to troubleshoot: 1. *Check DNS Configuration*: Ensure that your DNS records (especially CNAME or A records) are set correctly, and the domain is pointing to the right server. 2. *Verify Certificate Authority*: Ensure you're using a trusted certificate authority (CA) and the certificate is issued for the correct domain. 3. *Re-request the Certificate*: Sometimes, re-triggering the certificate request in your platform or service (e.g., GitHub Actions, a web hosting service) can resolve the issue. 4. *Check for Platform Outages*: Look into whether there are any ongoing issues with the service you're using (GitHub, your certificate provider, etc.). 5. *Ensure Proper Configuration*: Double-check the configuration files (e.g., for web servers or SSL/TLS settings) to ensure everything is set correctly. If none of these steps work, you might want to reach out to GitHub support or your certificate provider to check if there are any issues on their end. — Reply to this email directly, view it on GitHub <#183459 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BQAVOPKCKGCADT4P7WOQGRT4FEUWDAVCNFSM6AAAAACQUOJKCSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNBQGUZDSMI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[nirgranthi]

You have branching issue, your index.html is in a branch called "master", merge it into the main branch, this should resolve your issue. Or sometimes just removing and adding your website url from github pages fixes the certification issue.

[SaumyaKumarDas]

Hi there, Now it showing certificate has been activated. TLS is working fine now. Thanks for your help. Regards Saumya Kumar Das

…

On Sun, 4 Jan 2026 at 21:17, Saumya Das ***@***.***> wrote: Hi there, Thanks for your response in short notice. My DNS configuration is correct and there is no issue as such. Still it is showing "Certificate Request Error". It is been more than 24 hours from now. Still TLS certificate is not working. I have attached the screenshot of my CNAME / A / AAAA record in this mail. Please take a closer look. It seems the TLS certificate is stuck from Github side. Thanks and regards, Saumya Kumar Das On Sun, 4 Jan 2026 at 20:57, THE CHARITH ***@***.***> wrote: > The "Certificate Request Error" can occur due to several reasons, such as > issues with the certificate authority, DNS misconfigurations, or problems > during the certificate issuance process. Here are a few steps you can try > to troubleshoot: > > 1. > > *Check DNS Configuration*: Ensure that your DNS records (especially > CNAME or A records) are set correctly, and the domain is pointing to the > right server. > 2. > > *Verify Certificate Authority*: Ensure you're using a trusted > certificate authority (CA) and the certificate is issued for the correct > domain. > 3. > > *Re-request the Certificate*: Sometimes, re-triggering the > certificate request in your platform or service (e.g., GitHub Actions, a > web hosting service) can resolve the issue. > 4. > > *Check for Platform Outages*: Look into whether there are any ongoing > issues with the service you're using (GitHub, your certificate provider, > etc.). > 5. > > *Ensure Proper Configuration*: Double-check the configuration files > (e.g., for web servers or SSL/TLS settings) to ensure everything is set > correctly. > > If none of these steps work, you might want to reach out to GitHub > support or your certificate provider to check if there are any issues on > their end. > > — > Reply to this email directly, view it on GitHub > <#183459 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BQAVOPKCKGCADT4P7WOQGRT4FEUWDAVCNFSM6AAAAACQUOJKCSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNBQGUZDSMI> > . > You are receiving this because you authored the thread.Message ID: > ***@***.*** > com> >

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬