Anyone running Write.as behind Cloudflare proxy successfully?

Help
1

Hey folks,

Quick question about using Cloudflare with a Write.as custom domain (I’m on the Pro plan).

Everything works fine when I leave DNS on Namecheap and just point the A record to 50.56.249.138 like the dashboard says. And I’m pretty sure it would also work if I moved DNS to Cloudflare but kept it “DNS only” enabled. The problem is that I specifically want Cloudflare proxied for the asset caching/perf/WAF stuff.

When I tried moving the domain to Cloudflare (switched Nameservers), with cloudflare proxy enabled, the site stopped loading. Switching back to Namecheap nameservers fixed it right away.

Is proxied Cloudflare supported with Write.as custom domains, and if so, what’s the correct setup? Any required Cloudflare SSL mode/settings to avoid fighting with whatever cert/HTTPS Write.as is doing on its end? I am assuming this might have to do with the fact that Cloudflare also generates SSL certificate, and write.as is also generating one.

Thanks!

2

@support

3

Hey @reveil ,

I’m going to forward this to engineer Matt to see if he can help you out. So he can get back to you in the close-future!

Peter

5

Thanks! I also emailed support@ last week and have not heard anything back yet.

6

Hey @reveil, sorry for the delay here! You’re correct about Cloudflare’s SSL certificate messing with how we generate certificates on our end (discussed in another thread). So yes, you can use Cloudflare in “DNS only” mode and it’ll all work fine.

But if you’d like to use Cloudflare’s proxy services with us, we’d need to manually add a custom configuration specifically for your domain on our end. We can do this, but would require an additional one-time fee (per domain) for the engineering time it takes to set this up and maintain it. I’ll respond to your email and we can figure out if this is something you’d be interested in.