# Custom domain on a free static host - who should be issuing the cert?

**URL:** <https://community.letsencrypt.org/t/custom-domain-on-a-free-static-host-who-should-be-issuing-the-cert/252464>\
**Category:** Help\
**Created:** [October 26, 2026, 8:06pm UTC](https://community.letsencrypt.org/t/custom-domain-on-a-free-static-host-who-should-be-issuing-the-cert/252464 "2026-10-26T20:06:22Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![ekaputrigame](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/ekaputrigame/32/92395_2.png) [@ekaputrigame](https://community.letsencrypt.org/u/ekaputrigame)\
**Post date:** [October 26, 2026, 8:06pm UTC](https://community.letsencrypt.org/t/custom-domain-on-a-free-static-host-who-should-be-issuing-the-cert/252464/1 "2026-10-26T20:06:22Z")

</div>

My site is a handful of static HTML files sitting on Netlify's free plan. Two weeks ago I attached a domain I'd bought for it and let Netlify handle the HTTPS - that worked, the padlock was fine, and I stopped thinking about it.

Then I moved the nameservers over to Cloudflare for the caching and left the proxy on (orange cloud). Since then the site throws `526 Invalid SSL certificate`, and Netlify's dashboard shows the certificate as "waiting for DNS". My guess is that Cloudflare is answering the `/.well-known/acme-challenge/` request itself now, so the HTTP-01 check never reaches Netlify and the renewal quietly fails.

Is that what actually happens, or am I misreading it? And if it is: on a free static host where I can't run certbot at all, is it even reasonable to expect the host to keep renewing once a third party's proxy sits in front, or is the usual answer just to turn the proxy off and let the host do its thing?

I only need the site to load over HTTPS; I'm not attached to Cloudflare, I just wanted the caching. Tell me if I'm doing this backwards.

---

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [October 26, 2026, 8:20pm UTC](https://community.letsencrypt.org/t/custom-domain-on-a-free-static-host-who-should-be-issuing-the-cert/252464/2 "2026-10-26T20:20:54Z")

</div>

> [@ekaputrigame](#):
>
> I only need the site to load over HTTPS; I'm not attached to Cloudflare, I just wanted the caching. Tell me if I'm doing this backwards.

I don't know about "backwards" but not sure what kind of "caching" you are talking about. Do you mean just the caching of your static content?

If so, Netlify is a CDN so caches your content already. Proxying your Netlify setup at Cloudflare enables their CDN so you have one CDN in front of the other.

If you don't like Netlify's CDN you can switch over to Cloudflare "Pages" for a static site. Or setup an origin server for "regular" proxy from Cloudflare edge to your origin.

I just don't see why you'd want both. And, yes, it will be awkward to manage the cert because each CDN wants to handle the connection between the user-agent (ex: browser) and its edge.

---

<div class="post-metadata">

**Author:** ![ekaputrigame](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/ekaputrigame/32/92395_2.png) [@ekaputrigame](https://community.letsencrypt.org/u/ekaputrigame)\
**Post date:** [October 26, 2026, 10:01pm UTC](https://community.letsencrypt.org/t/custom-domain-on-a-free-static-host-who-should-be-issuing-the-cert/252464/3 "2026-10-26T22:01:41Z")

</div>

Following up on my own thread: turning the proxy off made the certificate issue almost immediately, which suggests the challenge never reached the host. I am still unsure who should own renewal in that setup.

---

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [October 26, 2026, 10:47pm UTC](https://community.letsencrypt.org/t/custom-domain-on-a-free-static-host-who-should-be-issuing-the-cert/252464/4 "2026-10-26T22:47:56Z")

</div>

> [@ekaputrigame](#):
>
> I am still unsure who should own renewal in that setup.

With Netlify as the origin server to Cloudflare's proxy both of them need a cert. Cloudflare handles the initial connection from the user-agent. As it needs data it makes a separate connection to Netlify, requests the data and passes it back to the user-agent. Usually that connection is HTTPS so both connections need a cert.

Cloudflare, as DNS provider, would use a DNS challenge in its Universal SSL used by its edge. There are various ways to redirect an HTTP challenge for a cert request by an origin server (Netlify here) back to the origin.

But, what do you expect to gain by having two CDNs involved? It's a duplication of the caching that each provides and extra HTTPS traffic.

You should review this Netlify support topic: [Proxy protection on sub-domains managed through Netlify - #2 by luke - Features - Netlify Support Forums](https://answers.netlify.com/t/proxy-protection-on-sub-domains-managed-through-netlify/30942/2)

---

<div class="post-metadata">

**Author:** ![ekaputrigame](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/ekaputrigame/32/92395_2.png) [@ekaputrigame](https://community.letsencrypt.org/u/ekaputrigame)\
**Post date:** [October 27, 2026, 4:52pm UTC](https://community.letsencrypt.org/t/custom-domain-on-a-free-static-host-who-should-be-issuing-the-cert/252464/5 "2026-10-27T16:52:48Z")

</div>

That clears it up — the 526 was the edge-to-origin leg, not the browser-to-edge one. Two renewals to think about, then: Cloudflare's Universal SSL (DNS-01, which I never touch) and Netlify's Let's Encrypt cert on the origin (HTTP-01, the one that sat on 'waiting for DNS').

What threw me was that both dashboards were telling the truth at the same time. The origin cert simply had not been issued yet, so the edge had nothing valid to talk to and reported it as a certificate error.

I wrote down the timings while I was going back and forth — how long propagation took, when each cert showed up here: [my measurement notes](https://ekagamenotes.blogspot.com)

Probably obvious to everyone here, but it was not to me last week.

---

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [October 27, 2026, 5:23pm UTC](https://community.letsencrypt.org/t/custom-domain-on-a-free-static-host-who-should-be-issuing-the-cert/252464/6 "2026-10-27T17:23:10Z")

</div>

> [@ekaputrigame](#):
>
> That clears it up — the 526 was the edge-to-origin leg

Yes. But more accurately you were trying an edge-to-edge as both Netlify and Cloudflare (when proxied) are CDNs 🙂

You would do well to avoid two CDNs and just use one. Netlify explains it well in the link I already provided (and the additional links that points to). Summary:

> 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

Even ignoring their advice have you planned how you would keep the two caches in sync? When using both you need to clear the cache at Cloudflare when you update files at Netlify. Otherwise you risk having your clients given a mis-matched set of files. That is only one of the reasons this dual CDN should be avoided.

I mentioned it earlier but research "Cloudflare Pages" if you prefer Cloudflare over Netlify for some reason. You'd get the same thing without the complexity and possibly worse performance.
