websocket domain

lenovouser

Create these DNS records with grey clouds, which means you disable CF proxying:

A live.domain.tld <000.000.000.000>
AAAA live.domain.tld <0000:0000:0000:0000:0000:0000:0000:0000>

And put this in your NodeBB configuration:

"socket.io": {
    "transports": ["websocket", "polling"],
    "address": "live.domain.tld"
}

Then get a free SSL certificate from Let's Encrypt or StartCom, and add this to your NGINX configuration:

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    ssl_certificate <your>.crt;
    ssl_certificate_key <your>.key;
    server_name live.domain.tld;
    location / {
        proxy_set_header X-Real-IP       $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header Host            $http_host;
        proxy_set_header X-NginX-Proxy   true;
        proxy_set_header Upgrade         $http_upgrade;
        proxy_set_header Connection      "upgrade";
        proxy_redirect                   off;
        proxy_http_version               1.1;
        proxy_pass                       http://localhost:<port>;
    }
}

bitspook

That is helpful! Thank you

cloudflare + peer5 = almost no bandwidth costs

Robert

@bitspook Sounds amazing too be fair, you're on that Developer package?

bitspook

One TB of offloaded data made me a fanboy. Just trying to dodge all the costs that I can in dev for an efficient production.

scottalanmiller

@Константин-Носов I'm getting a 503 from your domain.

Константин Носов

@scottalanmiller yep, it's dead due to update. Can't fix it will try to update on a week

hieudang

Thanks @lenovouser and @Ko
Or just moving to Incapsula. They supported Websocket on free plan.

scottalanmiller

@hieudang said:

Thanks @lenovouser and @Ko
Or just moving to Incapsula. They supported Websocket on free plan.

But not SSL

scottalanmiller

@lenovouser said:

And put this in your NodeBB configuration:
"socket.io": {
    "transports": ["websocket", "polling"],
    "address": "live.domain.tld"
}

Is this still working in 0.9.3, when I do this NodeBB cannot start.

exodo

@hieudang said:

Thanks @lenovouser and @Ko
Or just moving to Incapsula. They supported Websocket on free plan.

No. They dont

scottalanmiller

@scottalanmiller said:

@lenovouser said:
And put this in your NodeBB configuration:
"socket.io": {
    "transports": ["websocket", "polling"],
    "address": "live.domain.tld"
}
Is this still working in 0.9.3, when I do this NodeBB cannot start.

Got it to restart now, must have been a typo, but sockets are still not connecting

lenovouser

@scottalanmiller I don't know if they changed the configuration in one of the last minor releases. Maybe some of the @administrators can chime in here.

hek

No. They dont

@exodo

I just had a chat with their support. Websockets enabled on all plans. Someone should do a comparison with Cloudflare pros/cons when running nodebb.

exodo

@hek said:

No. They dont

@exodo

I just had a chat with their support. Websockets enabled on all plans. Someone should do a comparison with Cloudflare pros/cons when running nodebb.

i had chat some months ago and they only support web sockets on higher plans
tested nodebb and web sockets didn't work
would be nice if they changed this now but i have my doubts

julian

A bit worrysome that we're getting conflicting information from the Incapsula sales team...

? Offline

Just spoke to an Incapsula support agent who verified that they support websockets in their paid plans, but not the free one.