GitHub Community
How to enable https support on custom domains #23049
-
|
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).
The second problem is that when I go to https://mentalhealth-kb.net in my browser, I get the message
|
Beta Was this translation helpful? Give feedback.
Replies: 27 comments 22 replies
-
|
I changed my A records to 185.199.108.153 Now waiting for DNS to update |
Beta Was this translation helpful? Give feedback.
-
|
Add www. before your domain name in CNAME file. |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
@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. |
Beta Was this translation helpful? Give feedback.
-
|
did it worked? i got the same message as you |
Beta Was this translation helpful? Give feedback.
-
|
Hi @andy5995, @donotspampls, and @tagatuha, Edit: You need to use our new IP addresses to set up custom domains. These are:
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! |
Beta Was this translation helpful? Give feedback.
-
|
thanks @codelahiru |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
I've done that and still |
Beta Was this translation helpful? Give feedback.
-
did you fix it? i still have the same issue. trippin my balls for 3 hours to fix this lmao |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
After opening a ticket, support staff resolved the issue in less than 30 minutes. |
Beta Was this translation helpful? Give feedback.
-
|
how? |
Beta Was this translation helpful? Give feedback.
-
|
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) 😢 |
Beta Was this translation helpful? Give feedback.
-
|
Hi @upupming I marked this ticket as solved a few days ago. Check out page 1 for the post marked as “solution”. Good luck! |
Beta Was this translation helpful? Give feedback.
-
|
Hi, Me too. I got the same problem. I changed my domain yesterday. Did you solve that right now? |
Beta Was this translation helpful? Give feedback.
-
|
Me too. It doesn’t work same: Not yet available for your site because the certificate has not finished being issued |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
I assume it’s because not all the bugs have been worked out of the automated process yet. It’s a very new feature. |
Beta Was this translation helpful? Give feedback.
-
|
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! |
Beta Was this translation helpful? Give feedback.
-
|
How do I use that to add it to my custom domain? |
Beta Was this translation helpful? Give feedback.
-
|
Took about an hour in my case. |
Beta Was this translation helpful? Give feedback.
-
|
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 !! |
Beta Was this translation helpful? Give feedback.
-
|
Find a solution yet? I have the exact same problem! |
Beta Was this translation helpful? Give feedback.
-
|
If you're using Cloudflare you need to disable their proxy feature
|
Beta Was this translation helpful? Give feedback.
-
|
This worked for me, thank you! |
Beta Was this translation helpful? Give feedback.
-
|
This was SUPER helpful. Thank you so much! |
Beta Was this translation helpful? Give feedback.
-
|
this fixed it for me, cheers 🥃 |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
@mkapuza |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
@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 |
Beta Was this translation helpful? Give feedback.
-
|
Hi @guanerlin |
Beta Was this translation helpful? Give feedback.
-
|
Fixed it by removing forwarding on go daddy. |
Beta Was this translation helpful? Give feedback.
-
|
hey can elaborate how do you did that |
Beta Was this translation helpful? Give feedback.
-
|
First remove all unnecessary records. Then give enough processing time, We need patience. |
Beta Was this translation helpful? Give feedback.
-
|
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 :( |
Beta Was this translation helpful? Give feedback.
-
|
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:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
what worked for me is adding www followed by domain name insted of the just domain name |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
and others
Hi @andy5995, @donotspampls, and @tagatuha,
Edit: You need to use our new IP addresses to set up custom domains. These are:
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!