Using CloudFlare with NodeBB

Pinned Tutorials
  • #74

    @wolfman2g1 honestly CloudFlare is pretty senseless regarding DDoS protection. With a proper host the chance of a DDoS is close to 0. I am running a top 100K Alexa site without CloudFlare protection (just DNS for faster resolving) and never ran into any issues in the past 4 years.

  • #75

    I think I'm fine with not using cloudflare. At the moment I'm just trying to get the site stable. I'm still getting disconnects even without using Cloudflare.

  • Swedes

    Seams to work great with cloudflare for me 🙂 I like the ssl support and DNS gui. But i guess I would not die without it 😛

  • #77

    @Jenkler Are you using ssl between your server and cloud flare?

  • Swedes

    Yes I do 😉 check out for usecase! Plz notify me if something seams broken! I am using Cloudflares own certs.

  • #79

    @Jenkler looks great man. I'm still trying to understand why I'm getting 400 errors for socket io.

  • Swedes

    I guess you have som configuration issues in nginx!

    Here is my config! Maybe this will help you 😉

    Server block

                    listen 443 ssl;
                    location @nodebb
                            proxy_pass http://www-nodebb-se:4567;
                    location ~ ^\/assets\/(.*)
                            root /server/nodejs/;
                            try_files /build/public/$1 /public/$1 @nodebb;
                    location /plugins/
                            root /server/nodejs/;
                            try_files $uri @nodebb;
                    location /
                            proxy_pass http://www-nodebb-se:4567;
                    proxy_http_version 1.1;
                    proxy_redirect off;
                    proxy_set_header Connection "upgrade";
                    proxy_set_header Host $http_host;
                    proxy_set_header Upgrade $http_upgrade;
                    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                    proxy_set_header X-Forwarded-Proto $scheme;
                    proxy_set_header X-NginX-Proxy true;
                    proxy_set_header X-Real-IP $remote_addr;
                    ssl_certificate /server/nginx/ssl/;
                    ssl_certificate_key /server/nginx/ssl/;
                    if ($host != '')
                            rewrite ^/(.*)$$1 permanent;

    Global block

          ssl_ciphers EECDH+CHACHA20:EECDH+AES128:RSA+AES128:EECDH+AES256:RSA+AES256:EECDH+3DES:RSA+3DES:!MD5;
            ssl_prefer_server_ciphers on;
            ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
            ssl_session_cache shared:SSL:10m;
            ssl_session_timeout 10m;

    BTW, if someone know any tweeks please advice 😛 And plz explain why!

  • #81

    @hek said in Using CloudFlare with NodeBB:


    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:, request: "GET / HTTP/1.1", upstream: "", host: "", referrer: ""

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

    I wonder if anyone was able to find a solution to this? Or is the recommendation still not using NodeBB with CloudFare?

    We recently started to use CloudFare (before seeing this topic) and it looks like when the forum traffic is high, we keep losing the connection to the forum, which never happened before CloudFare.

  • #82

    @crazycells personally, I believe this to be true. CF will land up causing more issues then it sets out to "resolve".

  • GNU/Linux

    @phenomlab @crazycells That is very weird, we used to recommend against using CF, but then found that the more egregious issues had been resolved.

    I will say that if you're using any of their caching technologies (e.g. rocket loader, etc.) then you might see issues where the incorrect cached file may be sent to the wrong users.

Suggested Topics

| | | |