How to enable https support on custom domains

[andy5995]

I have a registered domain - https://mentalhealth-kb.net and added a Let’s Encrypt certificate to it last week.

The GitHub Pages URL for it https://mhwkb.github.io/

The first problem is that in the options for my repo, under the custom domain section, the check box is disabled (after I enter in the the custom domain and save).

Enforce HTTPS — Unavailable for your site because your domain is not properly configured to support HTTPS ([mentalhealth-kb.net](http://mentalhealth-kb.net/))

The second problem is that when I go to https://mentalhealth-kb.net in my browser, I get the message

Your connection is not secure
mentalhealth-kb.net uses an invalid security certificate. The certificate is only valid for the following names: *.github.com, github.com, *.github.io, github.io

[andy5995]

I changed my A records to

185.199.108.153
185.199.109.153
185.199.110.153
185.199.111.153

Now waiting for DNS to update

[saurabhsingh26]

Add www. before your domain name in CNAME file.

[sudip051]

This worked for me. Thanks👍

[tagatuha]

I’m getting the following message after updating my DNS to point to the four IP addresses:

Enforce HTTPS — Unavailable for your site because you have a custom domain configured

[andy5995]

@tagatuhaI’ve got that message too, but it’s changed a few times for me since I started fiddling with my settings. Right now I’m told

Unavailable for your site because your domain is not properly configured to support HTTPS

I’m gonna let it sit for a day or 2 and see how things look after the DNS update. I’ll post here if I get things straightened out properly and make notes on what I’ve done.

[ChrisFb98]

did it worked? i got the same message as you

[ThirdEyeRose]

Hi @andy5995, @donotspampls, and @tagatuha,

Edit: You need to use our new IP addresses to set up custom domains. These are:

• 185.199.108.153
• 185.199.109.153
• 185.199.110.153
• 185.199.111.153

If you are still having this problem  after using these new IP addresses and haven’t opened up a ticket with our support team, could you please contact us at git.io/c? That way, we can help resolve this issue.

Thanks!

[correiamath]

I successfully resolved the issue by first removing all A records associated with the new IP addresses. Subsequently, I proceeded to remove the custom domain entirely and then re-added it. This approach effectively resolved the issue for me.

[KirolosMFahem]

I've done that and still

[zarabeth-yumie]

I've done that and still

did you fix it? i still have the same issue. trippin my balls for 3 hours to fix this lmao

[bircni]

I still have the same issue

[ldjb]

In my case, I had to remove the custom domain from the repository settings, then re-add it. This did not immediately work, but nine hours later, the certificate was issued and my site started being served over HTTPS.

So I would suggest to anyone having difficulty to first try removing and re-adding their custom domain, if they have not already done so. And secondly, a little patience may be required – the process can take a number of hours.

[tagatuha]

I deleted the custom domain (setting the custom domain field to empty and hit save), waited 30 seconds, and then added my domain again. Now I’m getting the expected message! Fast forward 5 minutes and the certificate was issued and the checkbox was clickable. Now I have HTTPS :smileyvery-happy:

Enforce HTTPS — Not yet available for your site because the certificate has not finished being issued

[IanLulu]

i think this worked for me?

i also added another CNAME record for the original domain (.github.io) to my DNS host records per this
source: https://stackoverflow.com/questions/76957713/google-domains-github-pages-enforce-https-unavailable-for-your-site-because-yo

[xalxnder]

6 years later, and this worked for me. Thanks!

[andy5995]

Thanks @tagatuha , I did what you said, but 12 hours later, I still see

Enforce HTTPS — Not yet available for your site because the certificate has not finished being issued

with a checkbox I can’t click.

@that-patI’ll open a ticket, thanks for the suggestion.

[andy5995]

After opening a ticket, support staff resolved the issue in less than 30 minutes.

[marinawolff]

how?

[upupming]

I renew my A records, deleted my custom domain and added it again.

But this message shows about one day:

Enforce HTTPS — Not yet available for your site because the certificate has not finished being issued (upupming.site)

😢

[andy5995]

Hi @upupming

I marked this ticket as solved a few days ago. Check out page 1 for the post marked as “solution”. Good luck!

[JonathanChaochen]

Hi, Me too. I got the same problem. I changed my domain yesterday. Did you solve that right now?

[CarsArena]

Me too. It doesn’t work same: Not yet available for your site because the certificate has not finished being issued

[Tibingeo]

Why does this require to create ticket to solve issue everytime, 3 days back I hosted a githubpage and then this issue was sloved after writing to support. Today I created a page and same issue created tocket to GH support and waiting to reply from last 5 hours, no reply yet.

[andy5995]

I assume it’s because not all the bugs have been worked out of the automated process yet. It’s a very new feature.

[nadiajoyce]

Hi @jonathanchaochen and @carsarena,

As the Accepted Solution to this thread states, if you’re still experiencing issues with HTTPS, you should reach out to our support team so we can help.

Cheers!

[logiti]

How do I use that to add it to my custom domain?

[sergey-alekseev]

Took about an hour in my case.

[sharnkaur]

I renew my A records, deleted my custom domain and added it again.

But this alert shows continuously from last Monday:

Enforce HTTPS — unavailable for your site because your website is not properly configured. why this !!

[GunvirDhesi]

Find a solution yet? I have the exact same problem!

[mkapuza]

If you're using Cloudflare you need to disable their proxy feature

Cloudflare enables their HTTP/DNS proxy feature by default, meaning GitHub isn't able to see the DNS records required to generate an HTTPS certificate. You'll need to disable this for any DNS records that point towards GitHub.

Disclaimer Disabling the HTTP/DNS proxy may interfere with other Cloudflare services.

If you use other Cloudflare services with your site, we aren't able to guarantee that these will continue working. For more help with this, I'd recommend reaching out to Cloudflare's support team.

First of all, make sure you've set up your DNS records in Cloudflare according to the instructions in our help documentation

To disable CloudFlare's DNS/HTTP proxy, you'll need to log in to your Cloudflare account, navigate to the DNS settings page for your domain, and click on the orange cloud icon next to any DNS records related to your GitHub Pages domain.

The cloud icon should turn grey when it's correctly disabled.

Once your certificate has been provisioned, you'll then be able to enforce HTTPS by checking the "Enforce HTTPS" checkbox. Keep in mind that it can take an hour or so for an HTTPS certificate to be requested, so if you follow these steps but are still having trouble, that's usually why.

If you're not sure how to resolve these SSL errors, contact your DNS provider, or have a look at our custom domain troubleshooting guide.

[daveliao]

This worked for me, thank you!

[mbronstein1]

This was SUPER helpful. Thank you so much!

[miwgel]

this fixed it for me, cheers 🥃

[trumanjchan]

Thank you! This worked for me. I deleted the other DNS records that did not pertain to github per @ThirdEyeRose's answer, then since I use CloudFlare I toggled the github DNS records' Proxy status to 'DNS only'. A minute later after one refresh I was able to see the checkbox to force HTTPS.

[Nikita31]

@mkapuza
Hi @guanerlin
I am unable to get https for my custom domain. I have added A with IP address, and CNAME with my github free domain, but still it does not work. removing and re-adding the custom domain this is not working for me tried multiple times.
Please help, Im using go daddy, and I have done everything whatever is required.
Still getting Enforce HTTPS — Unavailable for your site because your domain is not properly configured to support HTTPS

[SANJANASOLANGA]

In my case, I had to remove the custom domain from the repository settings, then re-add it. Immediately, the certificate was issued and my site started being served over HTTPS.

[guanerlin]

@ldjb thanks to this guy's suggestion, I was able to solve the "Enforce HTTPS Unavailable" issue for my website. When I tried to enable HTTPS enforcement on my domain, I received an error saying my domain was not properly configured to support HTTPS (mywebsite.domain).

To fix this, I removed the custom domain configured in my Pages settings and then added it again. After waiting about a minute, the "Not Secure" warning disappeared from my domain - it worked!

Let me share the steps I took that led to this issue in case it helps others:

I built my website using GitHub Pages at guanerlin.github.io
I purchased a custom domain and added it to the Custom Domain field in my GitHub Pages settings
I configured the CNAME and A records for my custom domain with my domain provider
When trying to enable Enforce HTTPS, I got the error that my custom domain was not able to support HTTPS
Removing and re-adding the custom domain, then waiting a minute resolved the issue and allowed me to enable HTTPS enforcement.
Overall, the key steps were removing and re-adding the custom domain, then allowing some time for the changes to propagate through DNS. Hopefully this helps anyone running into similar issues when trying to use a custom domain with GitHub Pages HTTPS enforcement.

[Nikita31]

Hi @guanerlin
I am unable to get https for my custom domain. I have added A with IP address, and CNAME with my github free domain, but still it does not work. removing and re-adding the custom domain this is not working for me tried multiple times.
Please help

[Nikita31]

Fixed it by removing forwarding on go daddy.

[parimalongithub]

hey can elaborate how do you did that

[ashtamudibackwaters]

First remove all unnecessary records. Then give enough processing time, We need patience.

[Nikita31]

I am unable to get https for my custom domain. I have added A with IP address, and CNAME with my github free domain, but still it does not work. Please refer attached images.

Please help really stuck :(

[Nikita31]

Yes it workef for me, I removed forwarding on godaddy.

…

On Mon, 27 May 2024 at 11:28 AM, ChrisFb98 ***@***.***> wrote: did it worked? i got the same message as you — Reply to this email directly, view it on GitHub <#23049 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFMMI3Z5QFCMK42KE6LTN7LZELDORAVCNFSM56UK3G32U5DIOJSWCZC7NNSXTOKENFZWG5LTONUW63SDN5WW2ZLOOQ5TSNJWGY2DINI> . You are receiving this because you commented.Message ID: ***@***.***>

[parimalongithub]

what worked for me is adding www followed by domain name insted of the just domain name

[DawitMengistu]

https://youtu.be/XQKkb84EjNQ

Finally after doing everything, I was using cloudflare. You can setup dns settings without actually starting the processes, but you have to choose a plan for your service to actually start everything.

So if you want the free plan choose that and finish the process, you can skip some of them and then it should work.

And ofcourse follow this comment https://github.com/orgs/community/discussions/23049#discussioncomment-3238817

[MSoup]

Also using cloudflare with github pages

On the cloudflare side I had to delete my CNAME record and then re-add it. I also had to disable "proxy" for each of my CNAME records. Then on github pages I was able to check the box!

[Gourab-Goswami]

If you have the domain from GoDaddy just clearing the unnecessary DNS solved this issue for me.
Added the DNS for A[@] and A[www], thats all it needed. no other DNS info were required for this to work for me.

[onitgo]

Hi,
I removed the A records and added only the CNAME record in the DNS settings. It worked for me. My domain provider is HostGator. Take a screenshot backup before trying; it might be helpful. Thanks."

Correct DNS Setup:
CNAME Record for www.onitgo.com pointing to GitHub Pages:
Name TTL Type Record
www 14400 CNAME onitgo.github.io

[NooruddinLakhani]

I was facing the same issue then I tried https://register.domains/en/hs/ssl-certificates which helps me to fixed the issue by providing a valid SSL certificate and assisting with proper DNS configuration. Your current SSL setup conflicts with GitHub Pages' HTTPS enforcement, which requires correct domain settings.