TLS Certificate Request Error

[elipurdyflacks]

Select Topic Area

Question

Body

Hello! My TLS Certificate is stuck on the first step with the error: Certificate Request Error: Certificate provisioning will retry automatically in a short period, please be patient.

It has stuck like this for hours.

On Name cheap my Host Records are setup as such:
A Record | @ | 185.199.108.153 | Automatic |
A Record | @ | 185.199.109.153 | Automatic |
A Record | @ | 185.199.110.153 | Automatic |
A Record | @ | 185.199.111.153 | Automatic |
CNAME Record | www | elipurdyflacks.github.io. | Automatic

Anyone know what I am doing wrong?

[LozanoMatheus]

Hey @elipurdyflacks did it work for you in the end? Mine is also stuck for a day or so

[Bohousek007]

It looks like you're trying to set up a TLS/SSL certificate for a GitHub Pages site with a custom domain, and the process is stuck. Based on the DNS records you've shared and the error you're encountering, there are a few things to check and correct:

1. Check GitHub Pages Custom Domain Configuration

• Make sure you have configured your custom domain correctly in the GitHub Pages settings. Go to your repository on GitHub, then navigate to Settings > Pages. Ensure that your custom domain is correctly entered there (e.g., yourdomain.com).
• Ensure that the Enforce HTTPS option is checked.

2. Verify DNS Configuration

• Your DNS records appear mostly correct for pointing a custom domain to a GitHub Pages site. However, here are a few details to verify:
  • A Records:
    • You have correctly set four A records pointing to GitHub Pages IP addresses. This is good.
  • CNAME Record:
    • Your CNAME record for www pointing to elipurdyflacks.github.io. is correct. Ensure that the trailing dot . is present at the end of the domain in the DNS settings (some DNS providers automatically add it, so it might not be visible).

3. Wait for DNS Propagation

• DNS changes can take some time to propagate fully across the internet. Depending on the DNS provider, this could take anywhere from a few minutes to 48 hours. During this time, your certificate might not be issued.

4. Check for Conflicting DNS Records

• Ensure that there are no conflicting DNS records, such as:
  • Any additional CNAME or A records for the root domain (@) that point elsewhere.
  • An AAAA record that might conflict with the A records.

5. Verify Certificate Provisioning on GitHub

• If the DNS settings are correct and it's been several hours, the issue might be with GitHub's certificate provisioning process.
• GitHub usually retries automatically, but you can try to trigger the process manually by:
  1. Removing the custom domain in your GitHub repository settings (under Settings > Pages).
  2. Waiting a few minutes.
  3. Re-adding the custom domain.
• This might force GitHub to re-initiate the certificate provisioning.

6. Check for DNSSEC

• If you're using DNSSEC (DNS Security Extensions), ensure that it’s configured correctly. Misconfigurations in DNSSEC can sometimes prevent GitHub from verifying your domain.

7. Use Online Tools to Verify DNS Settings

• You can use online tools like whatsmydns.net or DNS Checker to check if your DNS settings have propagated correctly across different regions.
• Ensure that your domain resolves to the correct IP addresses and CNAME across various locations.

8. Contact GitHub Support

• If the problem persists even after verifying everything, it may be worth contacting GitHub support. There might be an issue on their end that they need to resolve.

By following these steps, you should be able to identify and correct the issue that's preventing the TLS certificate from being provisioned for your GitHub Pages site.

[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! 💬