# Cloudflare preventing plugin connection

**URL:** https://meta.discourse.org/t/cloudflare-preventing-plugin-connection/125306
**Category:** WordPress
**Created:** [August 9, 2019, 8:05am UTC](https://meta.discourse.org/t/cloudflare-preventing-plugin-connection/125306 "2019-08-09T08:05:45Z")
**Posts on this page:** 10
**Page:** 1

<div class="post-metadata">

### Author: ![undeadcorvid](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/undeadcorvid/32/151889_2.png) [@undeadcorvid](https://meta.discourse.org/u/undeadcorvid)
#### Post date: [August 9, 2019, 8:05am UTC](https://meta.discourse.org/t/cloudflare-preventing-plugin-connection/125306/1 "2019-08-09T08:05:46Z")

</div>

Hi there!

I’ve been struggling to get the plugin to connect to my Discourse - though all the API information was correct, the plugin couldn’t find my forum. On a wild guess I removed my reverse proxy through Cloudflare, and now it’s working perfectly. Is there a certain Cloudflare setting that interferes with how this plugin works? I’m completely stumped. Not using Cloudflare isn’t an option for me.

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [August 9, 2019, 12:37pm UTC](https://meta.discourse.org/t/cloudflare-preventing-plugin-connection/125306/2 "2019-08-09T12:37:08Z")

</div>

Turn off the rocket loader.

There are dozens of topics about problems with cloudflare that you can read.

---

<div class="post-metadata">

### Author: ![michaeld](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/michaeld/32/1594_2.png) [@michaeld](https://meta.discourse.org/u/michaeld)
#### Post date: [August 9, 2019, 1:26pm UTC](https://meta.discourse.org/t/cloudflare-preventing-plugin-connection/125306/3 "2019-08-09T13:26:42Z")

</div>

Rocket loader modifies the Javascript while the plugin will connect to the API … so I doubt that this has anything to do with rocket loader?

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [August 9, 2019, 2:00pm UTC](https://meta.discourse.org/t/cloudflare-preventing-plugin-connection/125306/4 "2019-08-09T14:00:47Z")

</div>

I defer to @michaeld pretty much always. This time I even understand what he’s saying.

It’s not the Rocket Loader, as it just breaks Javascript. It’s something else.

> [@undeadcorvid](#):
>
> Is there a certain Cloudflare setting that interferes with how this plugin works?

It looks like it. There are dozens of topics where people describe problems and a very few where people say that it’s “easy.”

---

<div class="post-metadata">

### Author: ![undeadcorvid](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/undeadcorvid/32/151889_2.png) [@undeadcorvid](https://meta.discourse.org/u/undeadcorvid)
#### Post date: [August 9, 2019, 7:55pm UTC](https://meta.discourse.org/t/cloudflare-preventing-plugin-connection/125306/5 "2019-08-09T19:55:04Z")

</div>

Yeah, I have gone through a few posts I found on here on this same problem and none of them have so far fixed it - looked into TLS settings, ect. And Rocket Loader definitely isn’t the culprit, I haven’t ever had it on. Never felt the need to turn it on.

I’ll keep trying and will report back if I find the solution in my case. It’s a shame they don’t play nice together very easily.

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [August 9, 2019, 7:57pm UTC](https://meta.discourse.org/t/cloudflare-preventing-plugin-connection/125306/6 "2019-08-09T19:57:51Z")

</div>

Make the little cloud next to the DNS entry gray instead of orange.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [August 10, 2019, 4:14am UTC](https://meta.discourse.org/t/cloudflare-preventing-plugin-connection/125306/7 "2019-08-10T04:14:48Z")

</div>

Unless you have reason to believe your site will be the victim of a massive DDoS, you don’t need Cloudflare.

---

<div class="post-metadata">

### Author: ![undeadcorvid](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/undeadcorvid/32/151889_2.png) [@undeadcorvid](https://meta.discourse.org/u/undeadcorvid)
#### Post date: [August 10, 2019, 6:53am UTC](https://meta.discourse.org/t/cloudflare-preventing-plugin-connection/125306/8 "2019-08-10T06:53:50Z")

</div>

I run a political forum, unfortunately. Or, more accurately, some of the work I do invites the nastier side of the Internet. It’s common for people who do what I do to get DDoS’d, doxxed, ect. It’s why I like the way Discourse works and I’m not taking chances on security.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [August 11, 2019, 10:53am UTC](https://meta.discourse.org/t/cloudflare-preventing-plugin-connection/125306/9 "2019-08-11T10:53:53Z")

</div>

Be sure you enable the cloudflare template in `app.yml` if using it is a requirement.

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [August 11, 2019, 1:16pm UTC](https://meta.discourse.org/t/cloudflare-preventing-plugin-connection/125306/10 "2019-08-11T13:16:56Z")

</div>

Bear in mind Cloudflare only protects one path to your server. If the origin IP is found you’re still wide open.
