Applying SSL to page

[Gaeilgoals]

Select Topic Area

Question

Body

Hi,

My site gaeilgoals.com works on http but not https.
The DNS check remains successful, but I cannot Enforce https as "Unavailable for your site because your domain is not properly configured to support HTTPS"
I have an SSL cert from gandi.net, but I think I must be unable to find what feels like it should be a straightforward step of providing the SSL cert to github.. I uploaded the crt file to the repository, but that doesn't seem to have achieved anything.
Any thoughts much appreciated.

Thank you.

[queenofcorgis]

Hi there @Gaeilgoals 👋🏼

Have you checked out this discussion and tried some of the solutions shared there?

[Gaeilgoals]

I have, and having retried the solutions proposed there, I am still none the wiser. I have the four A records, the CNAME pointing to www to gaeilgoals.github.io., the SSL cert added to my github repository, and I've deleted and recreated the custom domain...

Further suggestions much appreciated!

Thanks!

[jfullstackdev]

answer from Copilot that may help you debugging the issue :

---

GitHub Pages provides a free automatic SSL certificate for your custom domain, but it requires that your DNS is properly configured. Here are some steps to troubleshoot:

1. Check DNS Configuration: Make sure your DNS records are correctly set up. For an apex domain like gaeilgoals.com, you should have A records pointing to the following IP addresses:

   185.199.108.153
   185.199.109.153
   185.199.110.153
   185.199.111.153
   

   If you're using www.gaeilgoals.com, you should have a CNAME record pointing to your GitHub Pages domain (username.github.io).

2. Wait for DNS Propagation: DNS changes can take up to 24-48 hours to propagate across the internet. If you've recently made changes, you might need to wait a bit longer.

3. Check GitHub Pages Settings: Go to your repository settings and scroll down to the GitHub Pages section. Make sure your custom domain is correctly set and try toggling the "Enforce HTTPS" option.

4. Remove External SSL Certificate: If you've uploaded an SSL certificate from another provider to your repository, remove it. GitHub Pages handles SSL certificates automatically and doesn't support external ones.

If you've checked all these and still have issues, it might be a good idea to contact GitHub Support for further assistance.

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

[shamshuddinlakhani-cloud]

GitHub Pages doesn’t allow manual SSL uploads; it auto-issues HTTPS only after DNS (A/CNAME) is correctly configured and fully propagated. Once DNS is fixed, GitHub will generate the SSL automatically and the “Enforce HTTPS” option will become available. The SSL certificates ssl was helpful because it clearly explains how SSL works and why proper DNS setup is required for GitHub’s automatic HTTPS, rather than manually uploading certificates.