Skip to content

Instantly share code, notes, and snippets.

Last active February 14, 2024 06:21
Star You must be signed in to star a gist
Save cvan/8630f847f579f90e0c014dc5199c337b to your computer and use it in GitHub Desktop.
How to serve a custom HTTPS domain on GitHub Pages with CloudFlare: *FREE*, secure and performant by default


CloudFlare is an awesome reverse cache proxy and CDN that provides DNS, free HTTPS (TLS) support, best-in-class performance settings (gzip, SDCH, HTTP/2, sane Cache-Control and E-Tag headers, etc.), minification, etc.

  1. Make sure you have registered a domain name.
  2. Sign up for CloudFlare and create an account for your domain.
  3. In your domain registrar's admin panel, point the nameservers to CloudFlare's (refer to this awesome list of links for instructions for various registrars).
  4. From the CloudFlare settings for that domain, enable HTTPS/SSL and set up a Page Rule to force HTTPS redirects. (If you want to get fancy, you can also enable automatic minification for text-based assets [HTML/CSS/JS/SVG/etc.], which is a pretty cool feature if you don't want already have a build step for minification.)
  5. If you don't already have one, create a new repository on GitHub to store your site's contents (preferably in the form of static web pages and assets; though not necessary, for the A-Frame site we use a static-site generator called Hexo).
  6. From your domain registrar's settings, create a CNAME record to point <domain>.<tld> to <user> (Refer to the GitHub docs for more information.)
  7. In your Github repo, create a file at the root called CNAME containing the domain name (e.g.,
  8. Push to GitHub Pages (either by pushing to gh-pages or master of your repo; or you can use the master branch of a repo named <org> - example: automatically gets published to, which redirects to
  9. You're done! All content will now be served to your users from CloudFlare.
Copy link

cvan commented May 26, 2020

@Aurorum fixed link; thanks

Copy link

brilliant, thanks a lot.
this articles was supplemented by your steps

Copy link

tomekit commented May 4, 2022

If despite all that, you're still getting: "404 File not found The site configured at this address does not contain the requested file." your repo might be configured to use: main instead of master branch. You may try to change default repo back to master, but Github Pages doesn't seem to care about that (you may have to modify Actions/Workflows)... but hey don't worry, at least you support some good cause, the more time you waste/spend on things like this !

Copy link

taufiq33 commented Jun 9, 2022

Great Tutorial! thanks for sharing

Copy link

bkingg commented Dec 1, 2023

I managed to have HTTPS on my custom domain without any third party.

  • Make sure your A record points to the correct IP addresses
  • Create a CNAME record www and set it to <USERNAME>
  • Go back to your repo settings and remove the custom domain and re-enter it then Save.
  • HTTPS checkbox should be checked after certificate issued

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment