Custom domain with Blogger not working

@andy Can I ask something? When you type the old blogger URL does it seamlessly re-direct to the custom domain without a message page warning about the redirect?

This was the problem in my case.

Everything works fine if I type in the custom domain, it automatically loads the content from the old blogger URL
But if I type in the old blogger URL, it is expected to just redirect to the new domain without showing a warning page.

Yes, it does - no redirect message. My test setup is live if you want to see: blogger site (404ndy.blogspot.com) redirecting to my custom domain (blogger.404ndy.com). You can test the blogger URL to see that the redirect is seamless to the user.

Yes indeed! It redirects properly!
Can you maybe share the screenshot of your cloudfare DNS entries? So I can compare with what I have? Hopefully I will be able to spot what I am configuring wrong.

Danke je wel!

So, a piece of critical information that I didn’t realize initially may be the culprit here: my DNS records for this are grey-clouded. After a little more testing it appears that when you orange-cloud these entries Blogger pops up the redirect message. I can’t explain this, but it may be the discrepancy between our configurations.

[screenshot redacted]

1 Like

Thanks for this! It will be interesting if this is indeed the case…

I had to switch my Nameserver back to my domain provider…I will now switch back to cloudfare and confirm if what you mentioned about “grey-clouding” the DNS records is the culprit here…

@andy so the issue was indeed the DNS records that were grey-clouded. My domain is back on Cloudfare and now it seamlessly redirects with the message page from blogger…

Hovering on the clouds icon I see they are used to turn on (or off) HTTP proxy (CDN). It been turned on when the cloud is orange.

I am guessing introducing this proxy, this man in the middle, is what triggers blogger to scream with that message on redirect (Would appreciate if someone more knowledgeable than me will confirm/refute this).

So, I have now turned off the proxy and my redirects works seamlessly. But I think the repercussion of this, is that “https” no longer works :frowning: which kinda defeats the purpose of why I wanted to host the domain on Cloudfare :frowning:

Now I am not sure if this is a definitive situation: but it seems that I cannot have HTTPS for custom domain on blogger via Cloudfare (well unless I want to leave with the scary, annoying redirect message that blogger screams at visitors)

I agree with both points based on my tests, and this HTTPS restriction appears to be imposed by Blogger as you can see on the settings page. Unless anyone else can confirm, I think - regrettably - that you may have to choose between HTTPS and bypassing the Blogger redirect page. I.e. which is more important to you: SSL for your blog (always nice to have but possibly not needed?) or the seamless transition from your old URL to your new one?

2 Likes

Unfortunately so…

I will be going with the lesser evil of not having HTTPS…although recent push from browsers/search engines seems to indicate that this might come with some penalty, but I take that over that annoying, scary redirect page :smiley:

Thanks for noticing the effect of the orange/grey cloud icon :slight_smile: without that, would probably still be pulling at my hair!

1 Like

Some #Blogger blog owners want to provide blogs published to custom domains - and offer HTTPS connectivity. Since Blogger cannot provide custom domains with HTTPS right now, the blog owners are using Cloudflare, which provides an HTTPS proxy.

Unfortunately, a Cloudflare proxy looks like malicious redirection - and blogs using Cloudflare are being labeled as “Deceptive” sites.

http://blogging.nitecruzr.net/2016/03/Cloudflare-custom-domain-publishing-and.html

Late back to this topic but @andy your screenshot shows you grey-clouded both the verification record and the blogger record. Out of interest if you orange-cloud just the blogger record but leave the verify record grey-clouded, does this work?

I did some testing and the :grey: don’t seem to matter any longer. I :orange: the blogger subdomain and have HTTPS without a redirect page.


above no longer accurate as of March 2018.

So I suspect that’s because the verification record I mentioned needs to be checked once (or perhaps once every so often) by blogger. If anyone else is still having this issue try setting the cloud to :grey: next to the verification record only and leave the actual cname to ghs.google.com :orange: . I think that way the verification should always complete and you’ll still be powering your blog itself through Cloudflare.

Thanks @andy 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 redirecting “blog.hanxue.co” to “hanxue.blogspot.com”, 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 - https://blackcatwheels.blogspot.ch
I bought domain blackcatwheels.ch
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

Thanks
Tomasz

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. blackcatwheels.blogspot.ch) 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 - www.myyatradiary.com but when I open my old blog URL - www.myyatradiary.blogspot.com 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