Community

@pitaj said in How to use websocket notifications from external app?:

@reinier-pupo okay so you want to listen for notifications.

You essentially want something like this:
https://github.com/NodeBB/NodeBB/blob/b46d2f93e64e6546fb295d396b830dcab9f0cbbd/employee monitoring software/public/src/client/header/notifications.js#L25

Yeah, thank you!! Exactly what i was looking for!

Yup, ignore me. I had two configs open and was looking at the wrong one.

what is the value of uid

https://github.com/NodeBB/NodeBB/issues/3793

Try removing the SPDY support and see if it works. I had to disable SPDY with SSL to get it to towork.

Hi folks,

I used the 2.4 proxy instructions from the docs. But it's not working correctly for me. I assume because I want the proxy to only work on '/community'.

Here's my current setup:

I have a proxy here: https://openrct2.com/community (HTTPS) NodeBB actually runs on: http://delia.limetric.com:4567/community/ (just normal HTTP)

The proxy itself works great, but socket.io keeps complaining about not being able to connect using websockets: "WebSocket connection to 'wss://openrct2.com/community/socket.io/?EIO=3&transport=websocket&sid=OORktGqFRszzHMQNAAWr' failed: Error during WebSocket handshake: Unexpected response code: 400"

Here's a pastebin to my Apache config: http://pastebin.com/UMMadXVR

What should I change to my config to make websockets work correctly?

Thanks in advance.

Resolved in https://github.com/NodeBB/NodeBB/issues/2554

This was a setting under admin>settings>sockets it has been moved to config.json.

Old name was websocketAddress now its just address under the socket.io object.

Sample config.json

{ "url":"yourforum.com", "socket.io": { "address": "", //or url to socket.io server "transports": ["websocket", "polling"] } }

Relevant commit: https://github.com/NodeBB/NodeBB/commit/14e46a87a63f5e983a58a73109710027297924f3

The reason is if you put a invalid value here sockets will not connect and since the admin page uses sockets to save settings you can't change it back. 😆

Hey @src1988, is this the same issue that you're having here? https://github.com/NodeBB/NodeBB/issues/1878

If yes, then I think it's because you're running an incompatible version of widget-essentials with NodeBB. Let us know on that GitHub thread if you're still running into this problem 🙂

If the socket.io/tools.js module was deleted, then this won't work since the plugin was depending on that. I saw that there's a plugins.js module in the same place now, so i can amend it to user that instead. However I've just pulled the latest and can't get it to connect to redis, starting a separate thread...

Sounds like great news, looking forward to seeing NodeBB bloom using it 🙂