Custom domain with Blogger not working

Thanks @anon13938084 and @dadepo for continuing the conversation and solving the problem!

Indeed, turning off CDN solves the problem.

To clarify for anyone looking at this thread, I am trying to use a custom domain for blogger that is NOT www. Specifically I am” to “”, but “www” still points to my own server.

Blogger custom domain

Hi !
I am unable to scanning my website. Can anyone help me ?

Thank you, you really saved me from missing with other options.

1 Like

Hi Guys,

So did you finally make it work?
I have similar/same challenge:

I have my blog on google -
I bought domain
I wanted to use Cloudflare to redirect google blogger to the new domain and keep using https / ssl which is crucial for me.

I did the whole setup two days ago and Cloudflare still didn’t authenticate my entry…
I would be grateful for any advice


ok so finally my dns were validated.
The redirection from blogger to my new domain works including https :slight_smile:

Last thing which I can’t sort out is the blogger warning redirection page
I checked above posts but I don’t see the solution for this.
Anyone solved the case where user enters old blogger address (ex. and redirection works without any warning?

My DNS setup:

Same problem.

I may have read this thread about 10 times to get a hang of the solution. I have a blog with custom domain - but when I open my old blog URL - I get a redirect message. I am personally not fond of this message as it has a strong potential to turn readers away. I myself would prefer doing that, as a reader!

Anyone figured out a workaround to this problem, anyone or is it not possible? I am also curious about the current status of the redirection messages for the users above?

@dadepo @andy

Blogger controls the blogspot domain, and all subdomains under it. Only they control how redirects on their domain are handled. I suggest you start bugging them to make it look better.

3 posts were merged into an existing topic: Immediate Support for Compromised Account

@tomasz.gomolka and @22arti,

Thanks for bumping this topic. It appears my initial findings from July 2017 are no longer accurate.

I will update my posts here to redact any misinformation that may lead folks astray.

Unfortunately this does not seem possible anymore / at this time :frowning:

A post was merged into an existing topic: Immediate Support for Compromised Account

I just tried this on my blog also hosted Blogspot.

I did a few things here.

  1. Set IP addresses to the same per Google’s support article
  2. Set my www as CNAME to
  3. Set SSL to Full mode (use the Flexible mode if it is breaking, as origin SSL we cannot upload an origin SSL for
  4. Set a Page Rule to redirect.

Google’s support article Set up a custom domain - Blogger Help

Set a Page Rule to redirect.*
Forwarding URL: 301 Permanent Redirect$1

a few same error:

  1. when I use custom domain for my blogger But I click don’t auto redirect to (show page: You’re about to be redirected, and must click “yes”)
  2. other my blog: when Turn on “HTTPS redirect” so don’t access (error too many redirects so Turn off “HTTPS redirect”)

All my domain use Cloudflare DNS (turn on orange)
Pls help me, thanks very much

#1 isn’t a Cloudflare issue. That’s completely the blogspot site that’s not automatically redirecting.

#2 is something on your server improperly redirecting HTTP to HTTPS (or the other way around). What’s your Cloudflare SSL option set to (flexible or full)?

1 Like

Thank you so much.
I changed from flexible to full and success for all my blog (include and
hihi thanks for help <3

1 Like

Agree #1 is a a Blogspot setting. Anytime the is accessed, with or without Cloudflare in front of it, it will show that warning message. This is to warn users who are on your custom domain and is something that Google BlogSpot team has set the system to highlight so users know they are being redirected to another website.

I also cannot remove the warning on or

Have learned some from reading the above, but not enough to fix my issue.

I have just switched over mysite(dot)com to Cloudflare and enabled flexible https and a page rule to force https for “*”. In the site host’s cpanel www is suppressed. Everything is working fine except for the site’s Blogger blog at the custom domain that includes www and blog before mysite(dot)com: it’s is no longer accessible. I am getting the message that Safari can’t find the server and can’t open the https page “blog(dot)mysite(dot)com” because Safari can’t find the server “www(dot)blog(dot)mysite(dot)com”.

In Blogger basic settings, attempting to enable HTTPS, I got the message that it is processing the change, but the processing hasn’t happened over a couple of days.

I then followed Blogger’s instructions to edit the Cloudflare DNS with two CNAMEs. To do this I had to delete an “A” www that pointed to an IP address. See the first and last item in the image below showing the two new CNAMES

I am still getting the same message when I attempt to open my Blogger blog page. Over at Blogger basic settings, in trying to convert to HTTPS, I am no longer getting the infinite wait for the process to complete. Instead I am getting this error message:

An error occurred (code MappingsService.Insert APP_ERROR). Please try again.

Any suggestions on how to get my blog displaying again, and being able to change it to https (although it could stay at http if necessary). Alternatively or additionally I could kill the custom domain if I could set up a redirect from it to the address.

On reading Google info more closely, I see what they want is not necessarily just www, but the subdomain name, and they gave examples of www or blog. I suspect that since my blog URL uses both www and blog — — I should therefore include both in the CNAME entry instead of entering just www. So I’ve entered as the CNAME.

Then I realized I had long ago probably listed these DNS CNAMEs at Dreamhost, my hosting company. So I took a look and found the CNAME which confirmed this direction. So I deleted this CNAME from Dreamhost as well as adding it in Cloudflare. We’ll wait a while and see how that works.

Please note that the free CF certificates will not cover, they cover * but can’t cover * . *

Is the implication is that CF cannot provide https to If so, is this a problem, as provides https and http suppression? Haven’t gotten it working yet, but from what I’ve read I suspect once I get my DNS settings worked out I will be able to set this.