Hi, i have our site spread out across three servers, with Discourse on its own server. Right now the name server on the server hosting Discourse is set to use the default values (ns1.digitalocean.com, ns2, etc). As the entire site is connected and piped through cloudflare, should i update the nameservers on the server Discourse is running on using the cloudflare values instead? or leave it as it is now? Thank you.

In order for Cloudflare to be used at all, the nameserver for your domain name needs to be through Cloudflare.

My domain is registered at Namecheap. Namecheap points at Cloudflare nameservers. Cloudflare points at Digital Ocean droplet and Mailgun. Looks like this… be sure to turn off the orange cloud. [08]

[image] jameshahnii: be sure to turn off the orange cloud You can safely use the Cloudflare proxy after installation completes. Let’s Encrypt doesn’t like it initially, but it uses a different method to renew than enrol. There is a Cloudflare template which needs adding to the app.yml to get the correct source IPs.

Great. I didn’t know. Where can I find the template … or is that added automatically once you turn it back on?

It’s in /var/discourse/templates if memory serves.

Indeed it was. Copy/pasted into app.yml, ran ./launcher rebuild app and got this error… FAILED -------------------- Pups::ExecError: /tmp/add-cloudflare-ips failed with return #<Process::Status: pid 5910 exit 2> Location of failure: /pups/lib/pups/exec_command.rb:112:in `spawn' exec failed with the params "/tmp/add-cloudflare-ips" 2b27a4ac57cf9e8f76602ca570ebffce817a001e36a0c898195199d32c63a1d6 ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages Guessing I needed to do more than copy/paste the template?

I still would not recommend sending all traffic through cloudflare, unless you have a compelling reason to do so (as in you frequently get ddosed).

Noted. Turned off again. Thank you.

That’s very interesting @codinghorror, I’ve never heard that before. why would you recommend turning them all off? We have 6 subdomains across three servers, in a fairly complicated build, they all have the little cloud switched on. We’ve also had issues with not being able to auto-renew our Lets-Encrypt, is that likely to be the issue we’ve had?

Do a search for Cloudflare here on meta; there are periodic reports of one or the other of Cloudflare’s optimisations breaking Discourse (and probably other JavaScript-heavy applications).

Using Cloudflare, should the Name Server use Cloudflare settings, or stick with the host servers settings?

Product Support Self-hosting

Stephen (Stephen) September 1, 2018, 10:57pm 12

It’s easy to use a rule to disable any disruptive features.

Topic		Replies	Views
Query regarding adding Cloudflare Self-hosting	5	1072	March 5, 2020
Using Cloudflare Discourse IP works but not the url Product Support	4	1883	June 8, 2018
How to use Cloudflare to protect a Discourse site Self-hosting	4	1479	September 21, 2023
How Exactly should I add cloudflare CDN to discourse? Self-hosting cdn	5	5739	January 13, 2017
Trying to use Let's Encrypt + Cloudflare Product Support	19	3670	February 2, 2019

Using Cloudflare, should the Name Server use Cloudflare settings, or stick with the host servers settings?

Related topics