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.

[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.

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

[codelahiru]

I had entered an additional IP under A Records and because of that, could not enforce HTTPS. I resolved the issue by;

go to https://support.github.com/ -> type "custom domain https" in search field -> select "Our virtual assistant can help" -> follow along with the bots questions.

The bot pointed out the additional IP which was sitting under A Records. After deleting this record, I was able to enforce HTTPS from GitHub pages within 20 minutes.

[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

[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.

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