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 ?

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

      ornanovitch Log PHOTO

      Console PHOTO

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

          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.

                  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.

                        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.

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

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

                          Here is my Apache config that works:

                          RewriteEngine on
RewriteCond %{HTTP:Upgrade} websocket [NC]
RewriteRule /(.*) ws://127.0.0.1:2083/$1 [P,L]

ProxyPass /app/ http://127.0.0.1:2083/app/
ProxyPassReverse /app/ http://127.0.0.1:2083/app/
ProxyRequests off
                          • HD3D replied to this.

                            Kyrne

                             Problem 1
    - kyrne/websocket[2.8.0, ..., 2.8.5] require guzzlehttp/psr7 ^1.5 -> found guzzlehttp/psr7[1.5.0, ..., 1.8.2] but it conflicts with your root composer.json require (^2.0).
    - Root composer.json requires kyrne/websocket ^2.8 -> satisfiable by kyrne/websocket[2.8.0, ..., 2.8.5].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

                                3.0.0

                                👋 Presence Channels

                                • Websocket now features a presence channel that is automatically subscribed to when viewing individual discussions (logged in users only!)
                                  • Typing indicators for those replying to discussions at the bottom
                                  • Shows users that are currently viewing a discussion on the side bar
                                  • Easy extending (see dev guide below)

                                📈 Statistics (beta)

                                • See how things are going with your websocket server
                                  • Peak connection and websocket message counters now on the dashboard of your admin page
                                  • Configurable interval for statistics to cater to your forum's traffic
                                  • Stats are automatically deleted after 10 days
                                  • There will be a blank box on your dashboard until you have your first statistic

                                📓 Notes

                                • The api changed a bit in this release, if you hook into websocket, take a look at the guide below
                                • Statistics are only enabled for the non-Poxa server. While I didn't find any performance difference with stats on vs off, this is to keep Poxa as the most high-performance option
                                • The chart may need to be tweaked in the future depending on feedback. If you can't see some data, or the scale is wrong, feel free to reach out to me

                                ⬆️ Installing

                                1. Shutdown your running websocket server
                                2. Update the plugin composer update kyrne/websocket
                                3. Run the migrations php flarum migrate
                                4. Clear your cache php flarum cache:clear as well as any Cloudflare or other server caches
                                5. Configure the stats interval on the websocket admin page
                                6. Start the websocket server once again
                                7. Wait for the first interval to pass and check the graph!

                                🛠️ Dev Notes

                                • You now have a dedicated way to access the pusher instance. Simply resolve the app.pusher promise and you will find the pusher instance directly on the returned value's .pusher key
                                • Channels can now be found under that same value's .channel key
                                • The presence channel can be accessed via app.discussions.presence, it is automatically updated with the discussion that the user is currently viewing (don't forget to bind to an event each time a new discussion is viewed!)

                                  Kyrne really awesome updated. Installed and tested. So far working without flaw 😆

                                    Kyrne hey kyrne this is amazing. Thanks for the big update.
                                    I haven't seen any other problems with the mobile except for a minor issue.

                                        mekici

                                        3.0.1

                                        • Fix mobile display issue
                                        • Added stats interval timing message when starting the websocket server (visual only, no need to restart the server after updating)

                                            Kyrne did you turn off mobile viewing? Because it is no longer visible.