When creating a new GitHub pages site with Cloudflare’s DNS, the default setting is proxying all data via Cloudflare. This is OK, but Cloudflare can slow down GitHub pages somewhat, and GitHub pages have no bandwidth limits so might as well serve directly.


However, turning off proxying will… break things. Here’s an example from my settlers site, where Cloudflare was increasing load times from ~100ms to ~300ms:

Uh oh. This happens because the site previously worked over HTTPS, and now doesn’t, as shown:

  Old   New   Target
Cloudflare handles HTTPS Yes -> No -> No
GitHub handles HTTPS No -> No -> Yes

So, we obviously need to get GitHub to provision a certificate for us, and handle it all. Unfortunately, it still thinks Cloudflare is handling it all, so won’t provide a certificate. We’ll have to force it.

Note the misleading “Unavailable for your site because your domain is not properly configured to support HTTPS” error.


The solution is luckily not too tricky, but not at all obvious:

  1. Remove your custom domain (screenshot).
  2. Wait a few minutes, refresh the page, and add your custom domain back in.
  3. Wait a few more minutes, refresh it a few more times, you should see messages about a certificate being provisioned.
  4. Wait yet again, and eventually the HTTPS checkbox will be tickable again.
  5. After 5-10m, the DNS changes should propagate and your site will be back up again.

If you’re doing this for a custom domain, not subdomain, you’ll also need to:

  1. Disable proxying for ALL the A records.
  2. Add a CNAME record for www and <yourusername>.github.io to force a certificate to be created.

If these steps don’t seem to solve it, and troubleshooting doesn’t help, nor the tips in this thread, you’ll need to raise a support ticket!