Cname @ cannot be proxied

Hi CF support,

Today we hit an incident suddenly since this early morning (about GMT 0:00) Basically all traffic to our @ cname can no longer be proxied. But all other cnames still works with the proxy being turned on.

Can you pls help to find out the root cause for us?

Thanks,
R

Can you share the domain?

@hi.com

Our current temporary solution is to redirect hi.com to www.hi.com but we must find out what caused the issue. Thanks~

any update so far? anxiously waiting…

When I make requests through Cloudflare for your domain I see a few headers I do not recognise:

% curl "https://hi.com/?community=cache-buster1" --connect-to ::104.16.123.96 --dump-header - -o /dev/null --silent 
HTTP/2 404
date: Wed, 25 Aug 2021 08:24:37 GMT
content-type: text/html; charset=utf-8
cc-failed-domain: hi.com
cc-cache-group: default
x-robots-tag: noindex, nofollow
vary: Accept-Encoding
cc-cache-status: HIT
cf-cache-status: MISS

Do you recognise those cc- headers? Is it CloudCannon? If you are a customer of theirs, they may be using Cloudflare for SaaS. If you were a customer of theirs, but no longer are, you should ask them to deprovision your domain. Cloudflare for SaaS will take priority over the settings in your Cloudflare account.

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