Google Site - Cloudflare - Namecheap domain

Answer these questions to help the Community help you get started.

What is the domain name?
learninglimitcom

Have you searched for an answer?
Yes

Please share your search results url:
community.cloudflarecom/search?q=google%20namecheap

When you tested your domain, what were the results?

Describe the issue you are having:
I cannot get my site to connect with my Namecheap domain when running through cloudflare. Looks like my domain redirects to Cloudflare, but then it can’t pass the second connection to the Google Site.

I have verified that in Namecheap, I have the two correct nameservers set for Cloudflare.
In Cloudflare, I have the correct CNAME added for google site
In Google site, I have added my domain via Custom Domain tool

What error message or number are you receiving?
from entering URL in browser:
Connection timed out Error code 522

In Google Site Custom Domain section:
Invalid DNS

What steps have you taken to resolve the issue?

  1. Swapping SSL from flexible to full and back in cloudflare
  2. Re-adding the DNS information for google into cloudflare
  3. Making sure I have correct NS assigned in NameCheap for my domain (I do)
  4. Removing and re-adding my custom domain on the google site
  5. Waiting 24 hours

Was the site working with SSL prior to adding it to Cloudflare?
Yes

What are the steps to reproduce the error:

  1. type any permutation of learninglimitcom into address bar
  2. click enter

Have you tried from another browser and/or incognito mode?
Yes - Chrome, Brave, Edge

Well, I can’t get your right. However, I believe you’re trying to use CF but facing the following err:

As far as I see, I tested the site & its loading on Chrome, Brave, Edge, Opera. I do not see the error mentioned. The site uses CF DNS. In case, you’re seeing the error, then I suppose, the page could have been cached. In this case, you may clear the browser cache. If you want to know more about that error, check the following community Tutorial

1 Like

Thank you for testing this! After seeing that you got it to work, I did some digging. Seems my upstream networking devices were serving me a cached error page.

I appreciate you and the community!

2 Likes

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