SSL handshake failed on some pages only

Hi!

I’ve already read several posts on this error and followed advice but keep getting the same error no matter what I change!

The domain is sanctuarywithsarah com and it’s on Google Site (purchased domain from GoDaddy if this matters). Most of the website works but there are some pages that don’t and I get SSL handshake failed. Example:

https://sanctuarywithsarah.com/about
but it works when i add www to it
This applies also to all pages that pop up when i google for sanctuary with sarah, except when I click on the result with the homepage.

http://sanctuarywithsara.com doesn’t work.

I can’t identify the issue as I can’t identify a pattern in the error I receive from the different pages!

The CNAME are DNS only as all the rest of the DNS entries. The only DNS entries that are proxied are the two A (why do I have two?).

I spent days on this! Any advice would be soooo welcome!

Your www subdomain is not proxied so requests go direct to Google and the SSL certificate you will use is there.

Your apex domain is proxied so I can’t see what you have set in your DNS. If those point at Google it’s likely you haven’t set your Google hosting to use your apex domain, hence the SSL error when Cloudflare tries to connect to Google. Or Google needs to see the DNS record so you need to set it to “DNS only” instead of “Proxied”.
https://cf.sjr.org.uk/tools/check?f0cceb20b5e646ce80d4447ec9f43ae2#dns

Either make sure Google can answer requests for sanctuarywithsarah.com or you can set up a redirect on Cloudflare to redirect sanctuarywithsarah.com to www.sanctuarywithsarah.com. See here for how to do that…

1 Like

thank you!
I tried to follow the option to set up a redirect on Cloudflare following the instructions in the article. So far, nothing has changed, but I understand it might take some time.

as for the rest of your message, should I set everything as dns only?

Can you check which 2 Cloudflare nameservers are given at the bottom of the DNS page. There are an extra set for your domain which means either you are in the wrong account for your domain, or have deleted and re-added the site recently.
https://cf.sjr.org.uk/tools/check?840895299155413b985ce98becb14e8b#dns

These are the two cloudflare nameservers: |
NS| jasper.ns.cloudflare.com|
|NS| kiki.ns.cloudflare.com|

I don’t know what you mean for wrong account for my domain. The site was originally on fotomat. I removed fotomat and created a googlesite. The domain is from godaddy so I tried to change the dns directly in godaddy, but didn’t manage. That’s why I created an account here on cloudflare. Maybe that counts as delete and re-add?

(By the way, thank you so much for your help!)

Your nameservers look good. The ones in your screenshot match the ones shown in your whois data as well as in the parent zone.

If the apex name (the domain name by itself) is going to be used for a redirect to www, you don’t the two A records at the top of your screenshot. Just retain the AAAA that is set to 100:: and keep it :orange: proxied or the redirect will not work.

1 Like

Your nameservers are correct then.

If you have implemented the redirect, then remove the 2 A records, keep the AAAA 100:: record.

Can you show a screenshot of the Redirect Rule you created.

2 Likes

thanks both.

I removed the 2 A records and kept the AAAA 100:: record (proxied). The problem seems to be still there, but on top of that also https://sanctuarywithsarah.com/ doesn’t work now.

This is the rule I created.

update: now it’s not the handshake problem anymore. Now it’s 522 (connection timed out)

Can you show your current DNS records now.

Sorry, missed this in your redirect rule screenshot. The hostname should be sanctuarywithsarah.com, you just have sanctuarywithsarah.

DNS records are ok.

1 Like

then i’m a total idiot! can’t believe it… it all works now! THANK YOU SOOOOOO MUCH!!!

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.