HTTPS does work for my site now, but I get this warning:
Your connection is not secure / Your connection is not private
Error code: SSL_ERROR_BAD_CERT_DOMAIN (Firefox)
NET::ERR_CERT_COMMON_NAME_INVALID (Chrome)
Trying adding the A records as described here:
https://help.github.com/articles/setting-up-an-apex-domain/
Will update if that works..
My site says "Unavailable for your site because your domain is not properly configured to support HTTPS", but I don't see instructions to resolve it?
This is great! Now, if only GitHub would be available via IPv6, that would remove the need for CloudFlare — not that I would necessarily remove CloudFlare, but I would feel better if my setup wasn’t dependent on it.
Hm, I get SSL_ERROR_NO_CYPHER_OVERLAP in Firefox on https://stack.blogs.losttech.software/ , that is served from https://github.com/losttech/stack-blog via Cloudflare.
I've been doing HTTPS on hosted domains for years, and I don't really get how it works in this case. Is it that you don't use your own certificate, but GitHub automatically generates one with Let's Encrypt for you? If not, then how exactly do you give GitHub your cert? The instructions seem vague on this.
Such a shame they quietly broke IPv6 support.
Could this be related to Google's recent announcement of the .app TLD with mandatory HTTPS[0]?
[0]: https://www.blog.google/topics/developers/introducing-app-mo...
Can you host multiple HTTPS sites at different domains from one GitHub account?
Too little, too late.
I moved my repo to GitLab pages after Google announced it would prioritise sites that support HTTPS in its search results.
I use Cloudflare to get HTTPS on my github pages site, and I really like it. I get a lot of control over cached content and security, and statistics about site traffic. I am kind of happy that GitHub did not support HTTPS for custom domains, because then I would not have learned how to use Cloudflare.