Google Sites with a subdomain: SSL handshake failed or ERR_TOO_MANY_REDIRECTS

[cico]

Hello, everyone:

I am running a Google site with a subdomain from Cloudflare as the custom URL.

If SSL is in FULL mode, I encountered “SSL handshake failed”
IF SSL is in FLEXIBLE mode, I encountered ERR_TOO_MANY_REDIRECTS.

What should I do to resolve this issue?

Thanks in advance.

[francesco]

@cico

If SSL is in FULL mode, I encountered “SSL handshake failed”

If you have just added your site on CF, it’s normal, you just have to wait some minutes.

@cico

IF SSL is in FLEXIBLE mode, I encountered ERR_TOO_MANY_REDIRECTS.

Your server is redirecting incoming traffic on port 80 to https. You need to disable this if you want to use the flexible mode (which is not recommended, anyway)

[cico]

Thanks for the reply. I will wait for a couple of hours.

[cico]

It still does not work; I have set up another subdomain for Google sites from Google domain, after waiting for 10-15 minutes, that URL is up and running.
Should I make some change in Cloudflare to support Google Site? I have another site running in Gitlab pages, which works correctly.

[sdayman]

A 525 means you don’t have a valid SSL certificate on your web server. You’re probably running Full (Strict) SSL.

The Too Many Redirects in your Flexible mode meant the website was redirecting to HTTPS, but Flexible mode needs to operate in HTTP on your web server, without a redirect to HTTPS. In this case, it’s better to just leave SSL set to Off.

[cico]

Thank you for the reply. I am using Google sites,
https://sites.google.com/, it seems that I cannot do much about that, can I?

[francesco]

Ok, your site can’t work with “Full”, it doesn’t accept connections on 443.

So you have to use flexible, but remove the rule that redirects to https. Maybe some rule you added to .htaccess? Or are you using Wordpress?

[cico]

From Google sites, it says “Invalid DNS”.

But actually, it’s been set up for two days:

[cloonan]

Hi @cico, I think the input on this thread netted it out pretty well. I don’t think you’ll get this working without addressing the redirect @francesco points out and the certificate issues @sdayman mentioned. I see a cert on the origin, but with an invalid name.

[cico]

Thank you and everyone else for the kind help. It works finally after 5 hours. The only thing I need to do is being patient.