I've been reading several times that NodeBB uses websockets and therefore only CF enterprise customers may use it. However my instance of NodeBB works quite fine with CF's free plan (no websocket support apparently). I also don't get any errors in my log. Why does NodeBB still work then?

If you have acceleration turned off then it works, that's probably what you have going on right now. Otherwise you'd need an Enterprise account (although I believe they are rolling it to lower plans in future). There are some other companies, one which we have worked with in the past, that also offer DDoS protection (with websocket support) with a lower price point than CF's enterprise plan

In addition, even with acceleration, the site still works, but errors show up in the server and client logs, as socket.io keeps trying to re-establish a websocket connection. The fallback connection (ajax polling) does work.

Yep, you were right. It was fallbacking to ajax polling. I guess I'm just going to use CF in DNS only mode until they release their web socket support to other plans.

Is this still an issue? I cannot find any more info in the docs and I would like to use CF with Nodebb...

@darkpollo said in NodeBB and Cloudflare:

Is this still an issue? I cannot find any more info in the docs and I would like to use CF with Nodebb...

We are using NodeBB on a alternative Xenforo support site.
We are also using it behind CloudFlare successfully. I had numerous issues before I realized I websockets were in use and remembered it was an option in CloudFlare.
Currently their free plan does allow the use of WebSockets, but you have to turn it on as it is off by default.

It is located under your Network tab in the CF control panel.

@Tracy That is amazing! Thank you!
I had it ON so that is why I was not seeing any issues.

Thanks!

Just a note for those that are using CloudFlare. You may find your site CSS gets wonky after removing some plug-ins. Mine was some that dealt with the editor. No matter what I removed/added back in and rebuilt the editor was really displaying in bad form.
Then it dawned on me that CloudFlare does caching. Flushed the CF cache and the editor looks like it is supposed to.