Realtime - self hosted websocket for instant updates: Page 3

Realtime - self hosted websocket for instant updates

luceos

mekici 'websocket' => [
'server-port' => 2083,
'js-client-port' => 443,
'php-client-host' => '127.0.0.1',
'php-client-port' => 2083,
'php-client-secure' => false,
]

This all looks fine, have you restarted nginx? Other than that:

are you using cloudflare?
pusher provides more debugging information when debug is enabled in your config.php for this extension

mekici

luceos of course I restarted nginx. Yes, I'm using Cloudflare. Updated Kyrne Websocket plugin (v 2.8.4). I tried it it worked.

mekici

[deleted] How are you? were you able to run it?

[deleted]

mekici No, I haven't tried. Was going to try tomorrow now

[deleted]

mekici can you contact me on discord - phenomlab#4801

mekici

[deleted] I added it on discord.

pkernstock

Just to add, if someone's using systemd, you can use:
/etc/systemd/system/flarum-realtime.service:

[Unit]
Description=flarum-realtime
StartLimitIntervalSec=0

[Service]
Type=simple
User=flarum-user
WorkingDirectory=/var/www/flarum
ExecStart=/usr/bin/php7.4 flarum realtime:serve
Restart=always
RestartSec=5

[Install]
WantedBy=multi-user.target

luceos

I decided to remove our plans for now, people who paid for a subscription have received or can request a refund.

We will keep working on this extension for our own customers and for sponsored communities. In the meantime we will look at setting up some documentation and use cases.

luceos

Several issues found with the extension while going over errors from our hosted communities:

Queue jobs would hit the timeout because the default timeout is 60s, which has now been increased. Sending took a long time because it loops over all recipients then dispatches the websocket event synchronously, with the:
upgrade of the pusher php library events are now dispatched asynchronously
events send to guest users would never arrived, realtime switched from channel public to guests a while ago
duplicate events would be sent for events for non public discussions and the likes

luceos

A while ago I removed all plans from this extension as configuring it seems to be very problematic. Now that our Blomstra hosting platform has been released, I want to move forward in making this extension stable. For this I need a couple of patient people willing to install, configure and run the extension. We'll do this so that we can improve the documentation and ready the extension up for wider use.

If you have an interest in helping out, please contact me on discord, I will grant you a free lifetime license of this extension in return for active bug reporting, testing and patience.

Edit: I have sufficient testers, thanks for your interest everyone. Will ship a new version soon.

rafaucau

Will it be possible to configure this under a path (e.g. /scoket) on hosts that do not allow open ports and the only ports available are 80 and 443?

pkernstock

rafaucau You can just use a reverse proxy to do this job.

I'm personally using this configuration:

        location ^~ /app/REPLACE_APP_KEY_HERE {
                proxy_pass http://127.0.0.1:6001;
                proxy_http_version 1.1;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection "Upgrade";
                proxy_set_header Host $host;
        }

rafaucau

pkernstock I have hosting where their administrators manage the server. The client doesn't have access to advanced features there (so as not to break something).
The site is on a Litespeed server, so I can use .htaccess, but I don't think I can do a reverse proxy there.

Thanks for the reverse proxy idea. I will ask the hosting support if they would do that.
When I asked about opening ports, they said that for security reasons they can't do it.

pkernstock

rafaucau Ah, I see. No, then it won't work out, unfortunately.

« Previous Page