Realtime - self hosted websocket for instant updates

luceos

composer why-not pusher/pusher-php-server

Nodeloc

luceos Thanks, it's not work. It's may be conflict with flarum pusher. After remove flarum pusher, I install it normally.

Now another question is I get the WebSocket connection to 'wss://www.nodeloc.com:6001/app/a93ff319c2e9cdcd2816ce43e9f415bd?protocol=7&client=js&version=7.4.0&flash=false' failed error.

I run the realtime server with supervisor. It looks like work normally.

root@nl-ols:/var/www/www.nodeloc.com# ss -tuln
Netid          State           Recv-Q          Send-Q                    Local Address:Port                      Peer Address:Port          Process                         
tcp            LISTEN          0               511                             0.0.0.0:6001                           0.0.0.0:*                              
tcp            LISTEN          0               511                               [::1]:6379                              [::]:*                              
root@nl-ols:/var/www/www.nodeloc.com# supervisorctl status
queuework:queuework_00           RUNNING   pid 183787, uptime 0:18:11
realtime                         RUNNING   pid 184040, uptime 0:07:09
root@nl-ols:/var/www/www.nodeloc.com#

ernestdefoe

Nodeloc After remove flarum/pusher, I install it normally.

Yeah I had a feeling that was your issue installing Realtime. It should be part of the installation documentation (unless it is and I missed it) that you need to remove flarum/pusher first.

Nodeloc

rafaucau

I encountered the same issue as you, and I'm also using OpenLiteSpeed. I'm using the default configuration for realtime, and after adding it to the .htaccess file, I'm getting a 404 error. 😒

RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.*)$ ws://127.0.0.1:6001/$1 [P,L]

luceos

ernestdefoe I should probably add it as a conflict, that makes more sense 🤔

edit; that is already the case, added the removal instruction to OP and readme, good shout!

Nodeloc glad it worked out 👍️

Nodeloc

Okay, I'd solved the problem after I use SSL cert. 😆

HD3D

rafaucau Using OLS, Getting the following error after editing .htaccess file

Nodeloc My site is running SSL cert too, where did you use SSL cert?

@luceos any help?

Nodeloc

When using RealTime, I encountered two issues:

After reloading, the respondent's information is not refreshed.
Sometimes the user is displayed as "DELETED".

luceos

Nodeloc After reloading, the respondent's information is not refreshed

Care to explain this issue a bit more?

The deleted user issue is a known issue. I will plan in a day or two to fix issues on our extensions. I have been swamped so this and other extensions haven't gotten much attention.

luceos

0.3.0-beta.3 tagged

This should address some issues with missing last post data and author.

Nodeloc let me know if this version fixes things for you.

Nodeloc

luceos Care to explain this issue a bit more?

Autorefresh just highlight the discussion which have new reply, but the reply's author information haven't refresh.

luceos

Nodeloc so the issue is that realtime, when rendering new updates to the index, does not update who replied last in the thread, but keeps the old value.

Thanks for the video 😍 these things really help point out the issue 👍️

Nodeloc

luceos It fixed my issues, Thank you for your great job. 🥰

Nodeloc

There is a small problem, The content refreshed will appear above the stickied content.

neercsys

Why does Realtime not work for non-logged in users?
I am using the 0.3.0-beta.3 version

sylv38

Hi everybody !
I've read this topic, but I'm not sure the question has been asked.
I'm on a shared host, so there is a good chance that Realtime cannot be installed. But I'm not sure to understand everything that is required to make it work. Is there a way to test the extension or a way to be sure it could/couldn't work ?

Darkle

Hey, just to let you know, although it might already noticed, I wanted to try the @beta since I saw the design change for the typing indicator here (I like it!). And I came across an error that drove me a bit crazy, as I thought I had messed up some configuration on the server.

To reproduce the problem:

Enter the forum as a guest
Click on a discussion
You'll encounter the console error /api/websocket/auth 403 (Forbidden)

I just realised that it happens here also on discuss.

luceos

Darkle thanks, will check it out

luceos

I took the liberty of tagging 0.3.0, so far it seems stable enough now:

What's Changed

chore: switch ratchet, enable phpstan, begin patching by @imorland in blomstra/flarum-ext-realtime14
feat: move typing indicator to end of post stream for better visibility by @IanM blomstra/flarum-ext-realtime15
Prevent public discussions from being pushed to the private discussion list by @jaggy in blomstra/flarum-ext-realtime16
Fix issue where WS fails when the typing indicator is visible to everyone by @jaggy in blomstra/flarum-ext-realtime17
Remove error logging for when the request throws a 404 by @jaggy in blomstra/flarum-ext-realtime18

ernestdefoe

luceos definitely loving where the typing indicator is now. Looks much better in my opinion.

luceos

0.3.1

Fixed showing "& -1 others" when 2 people are typing.

Capybara

luceos Hi luceos, I want to buy this extension for the most part in order to show who is typing. Is it enough to install the extension or do I need to make a detailed configuration as in point b?

HD3D

luceos Can't I pay for it with paypal?

« Previous Page Next Page »