Enable Cloudflare Acceleration and HTTPS on GitHub Pages

A few days ago, when transferring the domain, I found that GitHub Pages hadn't fully enabled HTTPS, and the A records set in Cloudflare were also incomplete, so I went through the process again and decided to document it along the way.

This post was translated from my Chinese blog post with the aid of ChatGpt.



I’ve previously configured Cloudflare, but I’ll provide a brief summary with some images.

  1. Log in to Cloudflare and click on Add site in the top menu.
    Cloudflare Dashboard
  2. Enter your domain name, and then click the Add site button. I’m adding a random one for demonstration purposes.
    Add Site
  3. Choose a plan; usually, the Free plan is sufficient.
    Choose Plan
  4. Cloudflare will automatically fetch your domain’s DNS records. Skip this for now and scroll to the bottom of the page, then click the Continue button. We’ll come back to configure it later.
  5. Copy the domain name servers provided by Cloudflare and replace the existing ones with your domain registrar.
    Change DNS Servers
    Change DNS Servers
  6. Return to Cloudflare and click Done, check nameservers.
  7. Now, patiently wait for it to take effect. You will receive an email notification once it’s active. While waiting, you can set up SSL/TLS.
    1. In the Overview section, set the Encryption Mode to Full.
      Encryption Mode
    2. Then, in Edge Certificates, enable Always Use HTTPS and Opportunistic Encryption, among others.
      Edge Certificates
    3. In Origin Server, enable Authenticated Origin Pulls.
      Origin Server
  8. After it becomes active, go to the DNS settings and add four A records and one CNAME record.
    1. For the CNAME record, set the NAME to www and the Content to GitHub Pages’ default domain, i.e., username.github.io.
    2. For the A records, set the Name to either @ or your domain and the Content to:
  9. Confirm that the Proxy status for each record is set to Proxied, indicated by an orange cloud icon.
    Proxy Status

GitHub Pages Configuration

  1. Open your website’s repository settings, go to Settings-Pages.
  2. In Custom domain, enter your domain name. After clicking Save, it will automatically generate a CNAME file.

Enable Full (strict) Mode Encryption

The difference between Full (strict) mode and Full mode is that Full (strict) mode uses valid certificates signed by trusted CAs or Cloudflare Origin CA and verifies the certificate for each request. On the other hand, Full mode uses unverified self-signed certificates. GitHub Pages can obtain a free trusted certificate by enabling Enforce HTTPS, meeting the conditions to enable Full (strict) mode. Here’s an issue I discovered today: I couldn’t enable Enforce HTTPS in my Pages settings. The checkbox was grayed out. It turned out that the Cloudflare proxy status caused this issue. Here’s the solution:

  1. In Cloudflare’s DNS settings, change the Proxy status for all records to DNS Only, indicated by grayed-out clouds.
  2. Go back to your Pages settings and refresh the page. Now, you can check Enforce HTTPS.
  3. GitHub will automatically apply for an SSL certificate. Having this certificate enables you to enable Full (strict) mode in Cloudflare.
  4. After Pages’ HTTPS takes effect, return to Cloudflare and change the Proxy status for the records back to Proxied, indicated by orange clouds.
  5. In SSL/TLS settings, set the Encryption Mode to Full (strict).

DNS Record Types Overview

Some content is sourced from Wikipedia.

A Record

An A record (Address record) is used to specify the IP address associated with a hostname (or domain name). Users can point the web server of their domain name to their own web server. It returns a 32-bit IPv4 address.

AAAA Record

An AAAA record (AAAA record) is used to resolve a domain name to an IPv6 address in DNS. Users can map a domain name to an IPv6 address and also resolve subdomains to IPv6 addresses. It returns a 128-bit IPv6 address.

CNAME Record

A CNAME record (Canonical Name Record) is used to map one domain name (alias) to another domain name (canonical name). When a DNS resolver encounters a CNAME record, it will restart the query process with the mapped target. CNAME records can be used for CDN acceleration by aliasing domain name resolution for websites.

NS Record

An NS (Name Server) record is a domain name server record used to specify which DNS server is responsible for resolving the domain. If you need to delegate subdomains to other DNS service providers, you should add NS records.

MX Record

An MX (Mail Exchanger) record is used to specify the mail server responsible for handling email sent to the recipient’s domain.

TXT Record

A TXT (Text) record is typically used to provide explanations or additional information for a hostname or domain name.


TTL (Time To Live) indicates the cache time for a DNS record on a DNS server, measured in seconds. When a local DNS server receives a resolution request for a specific domain name, it needs to send a resolution request to the authoritative DNS server specified by that domain name. The obtained resolution record will be stored in the local DNS server for a period. During this time, if the local DNS server receives another resolution request for the same domain name, it will not send a resolution request to the authoritative DNS server again. Instead, it will directly return the resolution record stored in the local DNS server.