Using CloudFlare with NodeBB

exodo

actually my problem is not with ssl @hek @yariplus i have similar config of your forum, but if you not setting transport then not using real websocket i think

actually with my test

first test, transports config empy, you can see many polling connections and 1 websocket, will be same if you put ["polling", "websocket"] as it takes the default, not sure what this mean @administrators

now with transport set with websocket only, then only websocket appears
last test setting [ "websocket","polling"] same result as before , only websocket happens

so last 2 options should be the correct one but testin with websocket disabler to see if it fallbacks to polling it doenst seem to be working

of course website works but you wont be able to write post etc

finally i checked this community and it seems it mixes polling and websocket like option 1, not sure why. @julianlam

if someone can make this test and test this plugin will be apreciated
https://addons.mozilla.org/en-US/firefox/addon/websocket-disabler/

yariplus

@exodo That is the correct way it is supposed to work. The reasons are described here. https://github.com/socketio/socket.io-client/issues/883#issuecomment-160106858

In short, if the app only used websockets, there's a good chance many users would get disconnected, or see long wait times as the connection attempts to downgrade.

exodo

@yariplus said in Using CloudFlare with NodeBB:

@exodo That is the correct way it is supposed to work. The reasons are described here. https://github.com/socketio/socket.io-client/issues/883#issuecomment-160106858

In short, if the app only used websockets, there's a good chance many users would get disconnected, or see long wait times as the connection attempts to downgrade.

i understand but if upgrade way is the correct one why "only websocket" is accepted? test 2 and 3.
also only websocket is way faster

yariplus

@exodo Hmm, I'm not sure. I just tried to duplicate your tests with the disabler, and for me, ['websocket', 'polling'] gracefully downgraded back to polling.

exodo

@yariplus said in Using CloudFlare with NodeBB:

@exodo Hmm, I'm not sure. I just tried to duplicate your tests with the disabler, and for me, ['websocket', 'polling'] gracefully downgraded back to polling.

wow that breaks my mind
do you have any special config on nginx or nodebb?
using cloudfare right? any setting there?

yariplus

@exodo Yep, cloudflare with nginx and SSL. No special settings, all orange clouds. Ngnix config is the recommended from nodebb docs.

exodo

@yariplus said in Using CloudFlare with NodeBB:

@exodo Yep, cloudflare with nginx and SSL. No special settings, all orange clouds. Ngnix config is the recommended from nodebb docs.

I see. So you able to disable websockets and write a post?
Nodebb version?

yariplus

@exodo Sorry, there appears to be an issue with the disabler extension. Although it worked when I first installed, now it only seems to work when it feels like it.

Anyway, when it did work. Yes, I was able to post without websockets, however, the downgrade process was extremely slow, every time I clicked a button there was a 5-10 second delay before I got a response.

nodebb v1.0.3/master

I'm guessing yours is different only because of the wonky extension.

julian

I'm inclined to blame the extension as well, though we cannot know for sure.

In general, XHR polling shouldn't be substantially slower. The idea behind it is it opens a connection to the server, and if data is exchanged, that message is sent immediately, and another connection is opened. So I don't quite know why you're seeing upwards of 5s+ between click and action @yariplus ...

yariplus

@julian Sorry, I was a little unclear. The delay only happened when I was using ['websocket', 'polling'] and had websockets artificially disabled on the client, and it attempts to downgrade to polling. Once it downgraded, everything happened at normal speed.

julian

@yariplus Right, that makes sense.

@exodo As @yariplus mentioned, socket.io will try polling first, and then "upgrade" to websockets.

Mikael Jenkler

It works great for me with Cloudflare since they activated websockets on free accounts Both with and without SSL works fine! No special config for NodeBB, just plug and play as it should be

yariplus

I was setting up a new site today an found out Cloudflare has some new thing in their SSL section called Flexible which is now the default.

You do not want this.

I cannot understand why anyone would want this. Set it to Full or Full (Strict)

It took me a while to figure out it sends all requests to port 80, including https, for reasons.

teh_g

@Jenkler Triple checking that all went well with CloudFlare supporting websockets now? I am looking to flip over to Cloudflare but want to make sure I won't break things if I just make the DNS switch

@yariplus said in Using CloudFlare with NodeBB:

I was setting up a new site today an found out Cloudflare has some new thing in their SSL section called Flexible which is now the default.

You do not want this.

I cannot understand why anyone would want this. Set it to Full or Full (Strict)

It took me a while to figure out it sends all requests to port 80, including https, for reasons.

Thanks for the heads up!

Mikael Jenkler

Check out https://www.nodebb.se <-- My site with cloudflare WS works !

teh_g

@Jenkler Cool, I will flip the switch tonight and hope for the best. I'll report back if I run into issues

Mikael Jenkler

Cool, I hope it works out well. I myself have no issues att all with CF and WS setup and no special settings is required.

teh_g

@Jenkler I flipped the switch on my forums and it seems to be working, https://gamingexodus.com/. I am pleased with an easy method over making config changes...

Mikael Jenkler

Looks nice, dark and private feeling. Glad that it worked

AOKP

To be honest, CloudFlare might be nice to use for sites with a small amount of visitors, but for bigger sites it can even result in a slower experience. For me CloudFlare managed to decrease site performance drastically due to an increased server response time on their end.