I am experiencing the same exact issue discussed in this closed topic:
Google Sites with a subdomain: SSL handshake failed or ERR_TOO_MANY_REDIRECTS
The listed solution is to “be patient” but doesn’t clarify which SSL mode (Full/Flexible) to be patient with.
I’ve left the SSL mode as FULL overnight, but it still returns a 525 handshake failed error.
I am pointing the A records to Google’s ip addresses hosting my Google Site, so I don’t have server access to establish SSL cert rules.
Any advice or clarification on the closed topic I referenced is appreciated.
You don’t need to
establish any rules but you do need to make sure the server is properly configured to serve your site on a valid certificate. With a 525 that won’t be the case and is the first thing you need to address with your host as you need a proper certificate on your server in the first place.
So the ssl works with www subdomain, just not with the naked.
And I can’t seem to find any configuration setting for ssl on GoogleSites or the Google Workspace Admin Dashboard.
Any ideas where to go from here?
I appreciate your response
Ideally you’d make sure you have a valid certificate for the naked domain as well, but if that does not work for any reason the next best approach would be to redirect to “www”.
This tutorial covers redirecting example.com to www.example.com when using Cloudflare, to do the opposite, please see
Redirect www.example.com to example.com.
You should replace all instances of example.com in the screenshots with your domain.
Step 1, The DNS Record:
The first thing you will need is a DNS record for @, set to . This can point to any IP address as the redirection page rule will execute first. I would recommend pointing it to 192.0.2.1, a dummy IP.
Step 2, Th…
Just make sure your encryption mode is “Full strict”.
I went ahead and set up the page rule for the redirect.
That should work for now.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.