Custom domain of the blogger.com to CLOUDFLARE #設定自訂網域 #google #網誌

 

You may find the support / help online

BUT 

always

The devil / GOD in the details

In the end,

As-Is: XXX.blogspot.com

To-Be: XXX.yourdomain.com

First of all

1. Register Domain on the Cloudflare

Why the high C/P to select Cloudflare? Ask GPT ^^

2. Access your Cloudflare DNS Settings

• Log in to your Cloudflare account.
  Select the custom domain you want to use for your blog (e.g., yourdomain.com).
  Go to the DNS section (usually on the left-hand sidebar).

• Add the Required CNAME Records:
• CNAME Record 1:
  
  Type: CNAME
  Name/Host: www
  Target/Points to: ghs.google.com
  Proxy Status (Orange Cloud): Click the orange cloud to make it grey (DNS Only).

This is crucial for Blogger to verify. Cloudflare's proxying (the orange cloud) can sometimes interfere with Google's verification process. You can re-enable proxying after verification if you wish, but it's generally recommended to keep ghs.google.com as DNS Only.

• CNAME Record 2:
  
  Type: CNAME
  Name/Host: XXX
  (This will be a unique, long string of letters and numbers provided by Blogger in your specific error message. You need to copy the exact unique code Blogger gave you.)
  Target/Points to: gv-XXX.dv.googlehosted.com
  (Again, this gv-XXX part will be a unique string from your error message.)
  Proxy Status (Orange Cloud): Click the orange cloud to make it grey (DNS Only).

Similar to the www CNAME, this needs to be DNS Only for verification.

3. Adjust Cloudflare's SSL/TLS Encryption Mode

• Go to the SSL/TLS section in the left-hand menu.
  Click on the "Overview" tab (if not already there).
  Under "SSL/TLS encryption mode," select "Flexible".
  
  

Why "Flexible"?

Full (Strict): Cloudflare requires a valid SSL certificate on your origin server (Blogger). Since Blogger provides its own SSL, Cloudflare sometimes has trouble validating it perfectly when set to Full (Strict), leading to the 525 error.

Flexible: Cloudflare encrypts the connection between the visitor and Cloudflare, but the connection between Cloudflare and your origin server (Blogger) is unencrypted. This works well for Blogger because Blogger itself handles the HTTPS for your custom domain on their end.

 4. Check Blogger's HTTPS Availability:

• Go to your Blogger dashboard.
  Navigate to Settings > HTTPS.
  Ensure that "HTTPS availability" is set to "Yes".
  Also, ensure "HTTPS redirect" is set to "Yes". This will force all traffic to use HTTPS.

Finally

Clear Cache and Wait

After making these changes in Cloudflare, clear your browser's cache.

Wait for 5-15 minutes (or up to an hour) for the changes to propagate on Cloudflare's edge network.

Then, try Browse your custom domain (www.yourdomain.com) again.