Websockets - Locally Hosted Alternative for Pusher (Now Free)

[deleted]

matteocontrini Very possible. My forum is quiet currently ! Out of curiosity, one simple workaround could be to stop and restart the service periodically with a CRON job. Primitive, but would terminate the process and re-spawn it at least.

matteocontrini

[deleted] yes, but I'll probably do that manually since it takes weeks to grow that much, and I have lots of free RAM.

But it should be investigated anyway... @Kyrne

Kyrne

matteocontrini Are you using the beta websocket server by chance?

Also for anyone on PHP 8 run composer require pusher/pusher-php-server 5.0.1 and you should be all good.

clarkwinkelmann

Kyrne blocking a dependency at one exact version in composer.json usually isn't a very good idea as it might block composer updates later on. Any reason not to use ^5.0.1 ? Also if it doesn't need to become a root dependency in composer.json, maybe just suggest updateing that package, or update the extension with all dependencies with composer update <your ext> --with--all-dependencies? Also, also, actually actually, wouldn't Composer already install the compatible version based on the platform requirements?

matteocontrini

Kyrne Are you using the beta websocket server by chance?

Kyrne

matteocontrini you might want to give it a try, it has significantly better performance. Shutdown your current websocket server and instead run

php flarum websocket:beta

If it doesn't work or anything goes wrong the old server is still available. Also check this post for an additional troubleshooting step: https://discuss.flarum.org/d/23473-websockets-locally-hosted-alternative-for-pusher/111

matteocontrini

Kyrne I'll give it a try when I have some time 🙂

matteocontrini

Kyrne it seems to be stable now, thanks. Still, it means there's a memory leak in the standard version.

Also, could you take a look at this issue? flarum/core2078 it's present in Websockets as well and it's quite annoying

Kyrne

2.5.0

Full beta 16 and PHP 8 support
Other stuff
If you ran the composer command above, remove it from your composer.json and simply run:

composer update kyrne/websocket -W

Kyrne

matteocontrini it's been an issue for a while and I'm having an extremely hard time pinning down the actual cause. In any case PHP is probably the last language you'd pick for a websocket server which is why I've introduced the new server built on Elixir and Erlang.

Glad to hear it's working

askvortsov

https://discuss.flarum.org/d/26845-bug-on-this-forum also seems to have been introduced recently

matteocontrini

Kyrne In any case PHP is probably the last language you'd pick for a websocket server

Ahaha that's true... 😆

matteocontrini

I just noticed an issue that started to appear after swapping the websocket server: it seems that the WebSocket connection is not attempted anymore when you're idle, after a while.

Here's what I see:

The connection was closed and nothing happened after that, so real-time features stopped working.

Kyrne

matteocontrini This is actually intended, literally a feature not a bug. Stale connections staying open is a part of the memory leak issue from the main server. Closing connections after a while is an industry-standard practice with websockets.

There's no good solution that works for everyone. If we leave the connection (channel) open after the client stops responding, the server will be eventually bogged down with connections and we can't guarantee the client won't attempt to open a new connection as opposed to the old one when it reconnects. If we close the connection after no response, the client will lose real-time features until they refresh the page.

[deleted]

Kyrne @matteocontrini this is also the same way that websockets operate in NodeBB. Very much a standard.

matteocontrini

Kyrne I don't think I get it. Why does the client stop responding? The client is alive and should respond/re-open the connection. I see real-time features stop working "permanently" after a couple of minutes just by leaving the page open, which makes the feature quite useless, honestly...

Wadera

I've noticed it too. I've got tab opened for few hours and sometimes it's just lose connection without any notification.

I would expect some "auto reconnect" feature when connection is broken for any reason and flarum tab is still open.

Could be really useful when you using it on mobile or when you sleep your PC. So after reopen browser with flarum tab it can reconnect by itself without requirement of refreshing page.

Also some indication of broken connection would be great. Something like "you are offline now, trying to reconnect..."

shaman79

Hello, when do you plan to upgrade for Flarum 1.0? Thanks!

Problem 1
    - kyrne/websocket[1.0, ..., 1.0.7] require flarum/core ^0.1.0-beta.11 -> found flarum/core[v0.1.0-beta.11, ..., v0.1.0-beta.16] but it conflicts with your root composer.json require (^1.0).
    - kyrne/websocket 1.0.8 requires flarum/core ^0.1.0-beta.14 -> found flarum/core[v0.1.0-beta.14, v0.1.0-beta.14.1, v0.1.0-beta.15, v0.1.0-beta.16] but it conflicts with your root composer.json require (^1.0).
    - kyrne/websocket 2.0.0 requires flarum/core ^0.1.0-beta.14.1 -> found flarum/core[v0.1.0-beta.14.1, v0.1.0-beta.15, v0.1.0-beta.16] but it conflicts with your root composer.json require (^1.0).
    - kyrne/websocket[2.1.0, ..., 2.4.2] require flarum/core ^0.1.0-beta.15 -> found flarum/core[v0.1.0-beta.15, v0.1.0-beta.16] but it conflicts with your root composer.json require (^1.0).
    - kyrne/websocket[2.4.3, ..., 2.5.0] require flarum/core ^0.1.0-beta.16 -> found flarum/core[v0.1.0-beta.16] but it conflicts with your root composer.json require (^1.0).
    - Root composer.json requires kyrne/websocket * -> satisfiable by kyrne/websocket[1.0, ..., 1.0.8, 2.0.0, ..., 2.5.0].

luceos

shaman79 premium extensions are required to be patched for the newest release within 4 weeks of that release as per the Extiverse premium extension developer terms: https://extiverse.com/terms/extension-developer

Darkle

[deleted] How could you force it to avoid this error? (shaman79 )

[deleted]

Websocket installed and activated without issue on my newly upgraded Flarum (1.02). Need to test it to ensure it works as planned, but no issues from what I see so far.

luceos

[deleted] it's running on discuss since this morning. No real issues found so far except for ignored discussions showing up on the index.

« Previous Page Next Page »