Follow
对于 GitHub Pages 的劫持影响来自大陆的访问。凑巧前段时间我启用了 Cloudflare 的代理，不过之前因此导致 GitHub 无法更新证书，所以这个代理功能我本来是关闭的，否则需要定期的关闭，使自己的域名指向 GitHub Pages 的 IP，证书才能更新。应该是这样。
对于 GitHub Pages 的劫持影响来自大陆的访问。凑巧前段时间我启用了 Cloudflare 的代理，不过之前因此导致 GitHub 无法更新证书，所以这个代理功能我本来是关闭的，否则需要定期的关闭，使自己的域名指向 GitHub Pages 的 IP，证书才能更新。应该是这样。
本来要写博客但是咕了的 GitHub 支持邮件部分内容
> GitHub Pages doesn't support external SSL certificates directly. We only officially support certificates that are generated and manged by GitHub itself.
> While it is possible to set up your own certificate service using 3rd parties like Cloudflare, these won't link in with the "Enforce HTTPS" option in the repository settings, and this will remain disabled even when you've manually set up HTTPS.
> 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.
> ... for GitHub to handle the renewal of HTTPS certificates automatically you need your DNS records to point to GitHub IPs.
> If you do use GitHub's service and enforce HTTPS, it means you would also be using our CDN as well! If you are determined to use an external service, then yes, you would need to manage the renewal yourself.