Re:Free SSL on Github Pages with a custom domain: Part 2 – L...
by dayvidwhy on Wednesday May 02, 2018 @09:36PM
(#16982678)
In your position I did these things;
- Removed the CNAME record;
- Changed my A records to point to githubs https ip's
- Deleted the site from cloudflare
- Purged my cache for the site in chrome (chrome appears to remember who your site has its cert with for a bit?)
- Profit
Re:Free SSL on Github Pages with a custom domain: Part 2 – L...
by hdra on Thursday May 03, 2018 @05:40AM
(#16984524)
I had to put remove the CNAME file, push, add it back, and push it again to trigger the check again (You can do this with the domain textbox on your settings page as well).
Re:Free SSL on Github Pages with a custom domain: Part 2 – L...
by isaack on Thursday May 03, 2018 @02:13AM
(#16983715)
You need to turn off CloudFlare proxying for your domain. Instructions here: [1]. (Can't find an official help page, sorry).
Also make sure that you are using a CNAME record pointing to `YOUR-USERNAME.github.io.`.
[1]: https://webmasters.stackexchange.com/a/71922
[2]: https://help.github.com/articles/setting-up-a-www-subdomain/
Re:Free SSL on Github Pages with a custom domain: Part 2 – L...
by scrollaway on Thursday May 03, 2018 @02:14AM
(#16983718)
I had to contact support. They nudged the system for me.
Though in github, the "enforce https" is greyed out and says: "Unavailable for your site because your domain is not properly configured to support HTTPS (lab.openbloc.fr)". Does anyone knows what isn't actually "properly configured"? I have a CNAME file in the repo containing "lab.openbloc.fr".
The help says "If you're updating an existing custom domain, first remove and then re-add your custom domain to your GitHub account to trigger the process of enabling HTTPS." but the option is still disabled.