3 ms·
Interesting, as it wasn't possible to have https and a custom domain in the past, I'm using Cloudflare with the flexible https & enforce https settings. Though
by blaze33 8y ago
Interesting, as it wasn't possible to have https and a custom domain in the past, I'm using Cloudflare with the flexible https & enforce https settings.
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.
- dayvidwhy 8y agoIn 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
- isaack 8y agoYou 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 https://webmasters.stackexchange.com/a/71922 [2]: https://help.github.com/articles/setting-up-a-www-subdomain/ https://help.github.com/articles/setting-up-a-www-subdomain/
- scrollaway 8y agoI had to contact support. They nudged the system for me.
- hdra 8y agoI 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).