How I solve Custom Domain Issues

How I Solved Cloudflare + Blogger Custom Domain Issues

If you're facing issues connecting your Blogger blog with a custom domain via Cloudflare — you're not alone. I recently went through the same experience with www.blseos.com. This post shares my step-by-step solution and answers common FAQs to help others fix it easily.

Step-by-Step Solution:

Added Domain to Cloudflare: First, I connected my domain (blseos.com) to Cloudflare and completed the DNS setup.

Pro Tips: Always wait for Blogger to finish setting up HTTPS before enabling full redirect in Cloudflare.

Added Blogger CNAME Records: From Blogger, I got two CNAME records:

• www → ghs.google.com
• A unique verification CNAME (e.g. abcd123 → gv-xyz.googlehosted.com)

Removed A Record: Initially, I added an A record pointing to 192.0.2.1, but later removed it to avoid redirect and SSL issues.

Cloudflare SSL Settings: I set SSL mode to Full (not Strict). "Strict" caused HTTP 525 SSL errors because Blogger doesn’t use a public certificate that Cloudflare validates.

Dealt with Redirect Issues: When both Cloudflare and Blogger forced HTTPS before Blogger's SSL was ready, it caused "Too Many Redirects" error. Disabling Blogger HTTPS temporarily fixed it.

Waited for HTTPS Activation: Blogger showed "HTTPS Availability: Pending" — it took some time. After waiting, it got activated.

Final Test: Once HTTPS was ready, I turned it back ON in Blogger and kept Cloudflare on Full SSL mode. Everything started working perfectly!

Pro Tip : Use Full SSL in Cloudflare, not Strict, unless you're using a valid certificate on your origin server.

---

Frequently Asked Questions (FAQ)

Q: What is the correct CNAME setup for Blogger?
A: You need to add:

• www → ghs.google.com
• A second verification CNAME provided by Blogger (e.g. abcd123 → gv-xyz.googlehosted.com)

Q: Should I add an A record in Cloudflare for Blogger?
A: No. Blogger doesn’t require an A record. Adding one can cause redirect loops or SSL errors.

Q: What Cloudflare SSL mode should I use?
A: Use Full SSL mode. Do not use "Strict" unless Blogger provides a valid public SSL certificate (which it doesn’t).

Tip 4: If you're stuck on “Too Many Redirects”, temporarily disable HTTPS in Blogger and wait for propagation.

Q: Why am I getting 'Too Many Redirects'?
A: This happens when HTTPS is enabled in both Cloudflare and Blogger but Blogger's SSL isn't ready yet. Temporarily disable HTTPS redirect in Blogger.

Q: How long does 'HTTPS Availability: Pending' take?
A: It can take from a few minutes to 24 hours. Be patient and check back later.

Q: What is a fallback subdomain?
A: It's your original Blogspot URL (e.g. yourblog.blogspot.com) that Blogger uses temporarily if your custom domain fails to load.

Pro Tips: Remove any A records if you are hosting only on Blogger. CNAME records are enough for custom domain setup.

I hope this guide helps you resolve your Blogger + Cloudflare + custom domain issues easily. Let me know in the comments if you have questions or need more help!