Sites down, Awaiting Netlify DNS

[webdigga]

Hello.

I have a few sites on Netlify and they have been running fine for a few months now.

At some point today all of my sites are down. They all use Cloudflare as the CDN.

Cloudflare points to the host which led me to check DNS in Netlify which has led me here.
In every site it now says “Awaiting Netlify DNS”.

I haven’t made any changes at all, everything was fine for the last few months. So I am just wondering if there has been a change somewhere that I am not aware of?

This is an example of one of my sites - https://divorce-coaching.com/

But the issue is the same for all of them, and just today.

Thanks
David

[Rio-0912]

I also faced the same thing. I panicked I deleted and pointed my domain nameserver directly to netlify. Hope so we will get the update asap.

[webdigga]

Well for a minute there I thought I was the only one… Thankfully I am not

I can’t leave it much longer like it is, so if it’s not working in the morning I will have to see what else I can do.

[digitalcolony]

All my domain hosted sites are down. I can still access them with the .netlify.app path.

[of-dev]

Exact thing going for me as well, support not answering

[nathanmartin]

Yeah, I’m not sure if Netlify have noticed the common threads yet.

The one we’re in, and these others, appear at face value to be related:

Site Accessibility Issue

Hi there, I’m having trouble accessing my site (ID: f9558776-f0fe-44e5-8340-deca57816cc3). I get a Cloudflare error page stating: “Contact your hosting provider letting them know your web server is not completing requests. An Error 522 means that the request was able to connect to your web server, but that the request didn’t finish. The most likely cause is that something on your server is hogging resources.” I haven’t made any recent changes to the site, and it has been up and running for us…

Netlify not being compatible with cloudflare getting 522 error

First time asking a question on forum PLEASE help See I have created an Ecom website using mern. Deployed it in netlify. Working fine. Brought a custom domain from hostinger myname.com. Now at this point I wanted to use cloudflare DNS in middle (free version of cloud flare) for security and monitoring reasons. What I did was i added the nameservers of cloudflare to my domain hostinger and I forgot what I did but at that time it was working fine. With the help of myname.com I was able to go to …

Edit, another one:

Personal site getting error that's it says host error

PLEASE help us help you by writing a good post! We need to know your netlify site name. Example: gifted-antelope-58b104.netlify.app DNS issues? Tell us the custom domain, tell us the error message! We can’t help if we don’t know your domain. Build problems? Link or paste the FULL build log & build settings screenshot Did you try Ask Netlify, our generative AI chatbot, before posting? It pulls info from Support Guides and recent solved forums posts. The better the post - the faster the answer. …

[Josephadam]

Same here. I also have the same issue but so far only on one website.

[webdigga]

Interesting. Is the only site of yours that is being affected the only one with Cloudflare as a CDN?

[nathanmartin]

You’re probably all already aware, but I figure I should mention it anyway, Netlify don’t recommend using Cloudflare in front of Netlify.

I believe the main thread explaining some of the possible issues is here:

[Support Guide] What problems could occur when using Cloudflare in front of Netlify?

Last reviewed by Netlify Support - June, 2024 Note: We recommend not using both Cloudflare’s CDN (“Accelerate and Protect”, the orange cloud in their UI) and Netlify for the same site at the same time. Why? Read on! Netlify’s web service is not designed to work optimally with another CDN “in front of” our CDN. Proxying to our service is in general not supported and we advise you not to do it for best hosting results. Cloudflare has made similar statements that it doesn’t recommend this usage…

[Josephadam]

. No that one has cloud flare as well.

[Josephadam]

That doesn’t make sense. Especially since it’s never been a problem for so long and woked fine but out of the blue now we’re all having the same problem. Seems fishy to me. Also only one of my sites are doing it. My other site with cloud flare is working fine

[nathanmartin]

@Josephadam In what way doesn’t it make sense to you?

I’ve only included it as additional information, not as a precise explanation for the issue you’re facing today.

The thread is 5 years old, it’s been Netlify’s recommendation for as long as I can remember.

As it says:

@luke

If you still want to proxy from Cloudflare, we can’t stop you.

@luke

and occasionally, catastrophic failures have been observed using this setup

There’s also this other thread:

[Support Guide] Why not proxy to Netlify?

Last reviewed by Netlify Support in May 2024 Netlify’s CDN automatically routes your web visitors’ traffic to a network-nearby server to give them the fastest possible response time…as long as you let their browsers talk directly to our CDN! We know you want your your web traffic to be fast; your deploys and rollbacks to be atomic; and your Analytics data to be useful. If you proxy to Netlify, you’ll have problems with all of the above - since those features of our service are only possible i…

---

@Josephadam

it’s never been a problem for so long and woked fine

Which is fine, if it works it works.
I’m only pointing out that it’s not what they currently recommend.
For specific details as to why you’d have to read those threads and ask further questions for them to clarify.

I also included it since as it mentions:

@luke

In these cases the only effective, quick fix has been disabling Cloudflare’s proxying as shown below.

That may do something, it may not
But if your site is currently down, and it’s an option for you, it may be worth a try.

[of-dev]

Yeah but you guys made a change since it’s been working for year+ for me and now it broke for many of us simultaneously.

Anyways, it seems the main thread has a solution to our problem. Is just weird that it broke for us all.

[nathanmartin]

@of-dev

Yeah but you guys made a change

To be clear, I haven’t done anything but provide you some info I’m aware of, I don’t work for Netlify.

[of-dev]

oh sorry haha! you were so knowledgeable i just assumed you work for netlify. have a nice day

[nathanmartin]

Another user experiencing the 522 error has posted here:

[Support Guide] What problems could occur when using Cloudflare in front of Netlify?

Hi everyone, I am also having a 522 connection timeout on getaiblogarticles.com. Weirdly enough, it was working until yesterday around 5PM (no changes from my side). I have removed the Proxied option in Cloudflare, but still have the same 522. No sign of DDoS from what I see in Cloudflare: [image] Do you have any idea on what might be happening? The server and frontend deployments show no errors, it seems to be something between Cloudflare and Netlify.

[rbatista191]

Thanks @nathanmartin - I am relieved to see this is not something I did, but rather a Netlify problem. I will shout a bit on Twitter to see if we get their attention.

[Josephadam]

Im not saying you don’t make sense, sorry. I’m saying this doesn’t make sense because they obviously pushed out something as to why a lot of us are having the same issue.

[webdigga]

I’ve removed all my sites from Cloudflare and changed nameservers to get everything working again.

I know it’s not supported so there doesn’t need to be an update. But I guess I’d like to know if this was an intentional change, or if this is something that might work again in the future, so I can reimplement.

[Josephadam]

I changed everything to dns only and my website still isn’t working. What else should I do? Just take it off cloud flare?