• Community Rep

    @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.

  • GNU/Linux Admin

    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 ...

  • Community Rep

    @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.

  • GNU/Linux Admin

    @yariplus Right, that makes sense.

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

  • Swedes

    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 ❤

  • Community Rep

    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.


  • @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!

  • Swedes

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


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

  • Swedes

    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.


  • @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...

  • Swedes

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


  • 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.

  • Plugin & Theme Dev

    @AOKP said in Using CloudFlare with NodeBB:

    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.

    Reddit and many high traffic websites use cloudfare.
    How do you block ddos if you show everybody your server ip?


  • @exodo every provider of a proper size is capable to withstand DDoS attacks.
    By the past 5 years, I had like 2 DDoS attacks overall, resulting in a 0% service interference due to proper network setup and hardware of the ISP. The longest one took 2 days by the way.

  • Plugin & Theme Dev

    @AOKP said in Using CloudFlare with NodeBB:

    @exodo every provider of a proper size is capable to withstand DDoS attacks.
    By the past 5 years, I had like 2 DDoS attacks overall, resulting in a 0% service interference due to proper network setup and hardware of the ISP. The longest one took 2 days by the way.

    That would depend on the ddos attack size. Any provider can go down and providing your ip will let that attack and futures go direct to you


  • And what CloudFlare does then?
    I mean, sure it hides my real server IP, but they do the same as my ISP and to be honest I am afraid that CloudFlare is even worse than that, due to the shared use (ISP also has shared hardware, but usually there should be less servers connected to the systems).

    If you have problems with DDoS attacks you should move to a more serious provider it seems like.

  • Community Rep

    @AOKP I couldn't agree more. I've always been confused as to what cloudflare's target market is. The only thing I can think of is people that don't know any better. I'm only using them myself because I get so many damn questions about using it.

  • GNU/Linux Admin

    @yariplus said in Using CloudFlare with NodeBB:

    The only thing I can think of is people that don't know any better. I'm only using them myself because I get so many damn questions about using it.

    That does make sense. In a sense, CloudFlare sells "uptime-as-a-service" in response to DoS attacks, and if there's a demand for something, there's value in it. I don't see any problem with it.

    You could ask the same questions of nginx' premium service... why bother when you can configure nginx on your own (custom functionality notwithstanding...)... but it definitely is an asset if you'd rather pay them to manage your server infrastructure instead of paying somebody on your own.

  • Plugin & Theme Dev

    Recommendation

    Do NOT use cloudflare (at least not the free plan) on NodeBB when you have a moderate traffic to your forum. Cloudflare seems to silently throttle the traffic resulting in very strange NodeBB behaviour (for some clients) where the simply cut websockets.

    The throttled client will see a lot of popups "Looks like your connection to XXX Forum was lost, please wait while we try to reconnect."

    In the ngnix error log you will also see lots of:
    2017/01/25 09:56:15 [error] 13909#13909: *799654 upstream timed out (110: Connection timed out) while reading response header from upstream, client: xxxxxxxxxxxx.123, server: forum.mysensors.org, request: "GET /socket.io/?EIO=3&transport=polling&t=xxxxx&sid=xxxxxxxxx HTTP/1.1", upstream: "http://127.0.0.1:4568/socket.io/?EIO=3&transport=polling&t=xxxx&sid=xxxxxxx", host: "forum.mysensors.org", referrer: "https://forum.mysensors.org/topic/702/openhab-mqtt-example/2"

    It has been kind of hellish to find the root cause.

Suggested Topics

  • 1
  • 2
  • 1
  • 1
  • 5
| |