Dimas Mukhlas Widiantoro

Welcome To dimasmukhlas.com

I am Dimas Mukhlas Widiantoro, a seasoned growth expert with 12 years of experience growing Brainly. I share my expertise in growth strategies, user acquisition, and product development. View my complete portfolio at codify.my.id

Trouble shoot in why sometime the blogger doesnt want to be redirected to your custom domain

  
Video here




Cloudflare + Blogger SSL Issue: What Broke My Site and How I Fixed It

Date: Yesterday

Yesterday my website suddenly stopped loading. It was working perfectly the day before, but when I tried to open it again, I was greeted with a Cloudflare error page showing:

SSL Handshake Failed (Error 525)
Browser: Working
Cloudflare: Working
Host (Blogger): Error

This post documents what happened, what I tried, and the exact fix that finally solved the issue.

The Setup

  • Platform: Google Blogger (Blogspot)
  • DNS & CDN: Cloudflare
  • Custom domain connected to Blogger

The site had been running normally until the SSL error appeared without any changes on my side.

What I Tried First

Initially, I assumed this was a certificate expiration or server issue. However, since Blogger is fully managed by Google, I quickly realized:

I do not control the origin server or SSL certificates.
Everything on the backend is handled by Google.

Changing Cloudflare’s SSL mode produced interesting results:

  • Full (strict) ❌ — Site down (Error 525)
  • Full ❌ — Still unstable
  • Flexible ✅ — Site worked

At first, this looked like a solution — but Flexible SSL is not recommended and can cause security and SEO issues.

The Real Root Cause

After deeper inspection, the real issue turned out to be Cloudflare proxying Blogger traffic.

Cloudflare tries to establish its own SSL connection to the origin. Google Blogger does not support:

  • Cloudflare Origin Certificates
  • Strict SSL validation from third-party proxies

This caused the SSL handshake to fail.

The Fix That Actually Worked

Solution: Set Blogger DNS records to DNS Only (Grey Cloud)

Once I changed the DNS proxy status from Proxied (orange cloud) to DNS only (grey cloud), the site immediately started working again.

This allows:

  • Direct HTTPS connection between visitors and Google Blogger
  • Google-managed SSL certificates to work correctly
  • No SSL interference from Cloudflare

Final Working Configuration

  • Cloudflare DNS: Grey cloud (DNS only)
  • Blogger HTTPS: Enabled
  • Cloudflare SSL mode: Irrelevant (not used)
Key takeaway:
Cloudflare proxying is not compatible with Google Blogger SSL in a reliable way.

Lessons Learned

  • Blogger already provides HTTPS — do not try to “enhance” it
  • Flexible SSL is a workaround, not a solution
  • Grey cloud DNS is the safest and most stable setup for Blogger

Post a Comment

0 Comments