Websockets - Locally Hosted Alternative for Pusher (Now Free)

[deleted]

mekici Same here. @Kyrne is aware.

ornanovitch

Thank you very much for this open source releasing, it's a great feature!

A little feedback. It didn't work at all for me on 2.8.2. On 2.8.3, it seems to work pretty well on the server side (no error in the output of websocket:serve. On the front side, it works perfectly for posts into discussions. But there is a problem regarding the discussion list. Whenever I publish a new discussion, the index empties and I have this message into the console (and the ones who are connected too):

TypeError: e.recipientUsers().find is not a function
    Pt Discussion.js:98
    e extend.js:35
    e extend.js:33
    controls DiscussionControls.js:28
    controls DiscussionControls.js:27
    view DiscussionListItem.js:68
    a render.js:30
    l render.js:155
    l render.js:160
    l render.js:66
 [...]
    exports render.js:964
    a mount-redraw.js:14
    c mount-redraw.js:25
mount-redraw.js:15:23
    a mount-redraw.js:15
    c mount-redraw.js:25

recipientUsers... it seems to be directly related to byobu, but I have no problem with byobu otherwise.

Kyrne

ornanovitch let's find out. Disable byobu and see if that fixes it. If not, try disabling other extensions. I've seen this problem before but it isn't directly caused by websocket.

ornanovitch

Kyrne I didn't even try, sorry 😅 I give a try!

ornanovitch

Kyrne Disable byobu and see if that fixes it

affirmative 👍️ so there is something wrong with byobu w/ websocket.

The only bug I notice now is the absence of tags on the appearing discussion, but without error in console, only debug:

Pusher :  : ["State changed","initialized -> connecting"] pusher.min.js:8:40297
Pusher :  : ["Connecting",{"transport":"ws","url":"wss://XXXXXXXXX:443/app/TmOsZcQ7pcqgULKbpkC8nFtfD3TSBCGQ?protocol=7&client=js&version=5.1.1&flash=false"}] pusher.min.js:8:40297
Pusher :  : ["State changed","connecting -> connected with new socket ID 357746542.251121011"] pusher.min.js:8:40297
Pusher :  : ["Event sent",{"event":"pusher:subscribe","data":{"auth":"","channel":"public"}}] pusher.min.js:8:40297
Pusher :  : ["Event recd",{"event":"pusher_internal:subscription_succeeded","channel":"public"}] pusher.min.js:8:40297
Pusher :  : ["No callbacks on public for pusher:subscription_succeeded"] pusher.min.js:8:40297
Pusher :  : ["Event sent",{"event":"pusher:subscribe","data":{"auth":"[auth]","channel":"private-user7"}}] pusher.min.js:8:40297
Pusher :  : ["Event recd",{"event":"pusher_internal:subscription_succeeded","channel":"private-user7"}] pusher.min.js:8:40297
Pusher :  : ["No callbacks on private-user7 for pusher:subscription_succeeded"] pusher.min.js:8:40297
Pusher :  : ["Event recd",{"event":"newPost","channel":"private-user7","data":{"postId":1860,"discussionId":293,"tagIds":[1,7]}}] pusher.min.js:8:40297

ornanovitch

Do you encounter any problem with byobu & websocket? With the Kyrne's one, I got a js bug each time I publish a new discussion (byobu or not). Quoting myself from ornanovitch on the Websockets thread:

[...] On the front side, it works perfectly for posts into discussions. But there is a problem regarding the discussion list. Whenever I publish a new discussion, the index empties and I have this message into the console (and the ones who are connected too):
TypeError: e.recipientUsers().find is not a function
    Pt Discussion.js:98
    e extend.js:35
    e extend.js:33
    controls DiscussionControls.js:28
    controls DiscussionControls.js:27
    view DiscussionListItem.js:68
    a render.js:30
    l render.js:155
    l render.js:160
    l render.js:66
 [...]
    exports render.js:964
    a mount-redraw.js:14
    c mount-redraw.js:25
mount-redraw.js:15:23
    a mount-redraw.js:15
    c mount-redraw.js:25
recipientUsers... it seems to be directly related to byobu, but I have no problem with byobu otherwise.

FYI desactivating byobu resolves this problem.

Kyrne

Just pushed two quick updates, main fix is the only logged in users may connect switch. (2.8.5)

mekici

There, it is done. Now everything works as it should. Thanks @Kyrne

ornanovitch

mekici everything works as it should

I updated to 2.8.5, am I the only one with this the tags issue?

mekici

ornanovitch Unfortunately the byobu plugin is not working. I disabled this plugin.

ornanovitch

mekici Ok thanks, I guess it's more complicated for byobu but I was refering to this:

The only bug I notice now is the absence of tags on the appearing discussion, but without error in console

Visually, when a new discussion comes up in the discussion list, it is as if it had no tags at all.

custom_user

Hello I am having an issue, that it doesn't seems to work I seen GitHub readme in order to configure my nginx, checked it also enable proxy checkbox pp in settings, enabled debug mode in config then ran php flarum websocket:serve but nothing happens I checked it posts are not showing in real-time so I checked storage/logs I see connection refused and sometimes 200 to the url 127.0.0.1:2083/apps/channels/?someprivatekeys.

So can you help me out

ornanovitch

custom_user I checked storage/logs I see connection refused and sometimes 200 to the url 127.0.0.1:2083/apps/channels/?someprivatekeys.

can you be more specific regarding the "connection refused"? 200 is good, that means the request passed without error. Do you have any output of the websocket:serve command and from your browser console ?

ornanovitch

custom_user It's clear that you have a backend problem, the websocket isn't accessible. What configuration method have you followed? You seem to have followed the first one (proxy) when you say:

custom_user I seen GitHub readme in order to configure my nginx, checked it also enable proxy checkbox pp in setting

But you seems to have followed the second one (port forwarding) when you say:

custom_user I checked that my port forwarding as well as firewall is allowing connections over 443, 80 and 2083.

custom_user

ornanovitch Log PHOTO

Console PHOTO

I checked that my port forwarding as well as firewall is allowing connections over 443, 80 and 2083.

troymccann

I'm trying to give this a go but I'm getting an 'invalid credentials' error. Any tips? 🤔

custom_user

Hello matteocontrini I would like to Thank You as your configuration helped me to configure and get real-time up thanks a lot. 😁

But sometimes it stops I have to run php flarum websocket:serve again but the thing a bit of code you shared to automatically enable websocket again so where to add that code please tell.

ornanovitch
It's sorted out thanks for your support.

matteocontrini

custom_user take a look here (it's an example, adapt file names, etc.): https://discuss.flarum.org/d/21873-redis-sessions-cache-queues/54

Kyrne

Here's some common fixes for common problems:

If you use the nginx method and it doesn't work, try replacing the @web with just / and the @ws with /app

If the websocket server keeps turning off, you will need to daemonize it, nohup is a good and simple method for doing this.

streaps

or start it as a systemd service (if you are running a full linux distibution).

Mark73

composer require kyrne/websocket and I'm ready to go? no setup needed?

[deleted]

Mark73 unfortunately, no. There's quite a bit of configuration required here. See
https://extiverse.com/extension/kyrne/websocket

« Previous Page Next Page »