Sudden loss of all broadcasts - have no idea what happened

[garrettboone]

This project is great - I started working with it only last week and everything was fine until today. I have no idea what happened and am looking for guidance.

• When I run the /laravel-websockets dashboard ALL the broadcasts are making it to the ledger
• I have channels like "UserJoined", "RoomCreated". "UserDisconnected", etc.
• But, when I run the websockets:serve it ONLY shows "New connection" and "Connection ###.### closed" along with pongs

The client side is getting nothing, reflects the Laravel job as described above. I've gone through my code and have confirmed it's making it all the way to event(new UserJoined('xyz')

I have restarted everything, cleared cache, and there are no Laravel errors. What should I look for next?

Thanks for any help.

[rennokki]

Package version 1.x or 2.x?

[garrettboone]

^1.8

I ran php artisan websockets:serve --debug and it caused the terminal readout to show the broadcasts again:

Connection id 801596624.223306496 sending message {"event":"log-message","channel":"private-websockets-dashboard-api-message","data":{"type":"api-message","time":"12:49:41","details":"Channel: 2c1bbbc5-50b8-4b1b-8b44-469ecb9e782c, Event: App\Events\UserDisconnected","data":"{"message":{"event":"userdisconnected","data":{"circle_user_id":"9c80a01b-d36a-4a5b-aa6b-c817f965731f","room_id":"0b41e451-58e6-477d-917d-dc32878dddcd","room_user_count":1,"total_room_count":1,"total_user_count":1}}}"}}

...but the clients are still not receiving them.

The websocket connection at the client shows the connection established, and my client-end logic to push the socketId to the backend is working fine. But only pongs are coming through.

Edit: terminal is now showing broadcasts without --debug
I'm using simple pusher setup as per docs, in Lavavel 6.x using ShouldBroadcast and BroadcastOn. Also using Laravel Echo.

[rennokki]

Show me the configurations for your broadcasting driver, Laravel Echo and your event.

[garrettboone]

broadcasting.php:

        'pusher' => [
            'driver' => 'pusher',
            'key' => env('PUSHER_APP_KEY'),
            'secret' => env('PUSHER_APP_SECRET'),
            'app_id' => env('PUSHER_APP_ID'),
            'options' => [
                'cluster' => env('PUSHER_APP_CLUSTER'),
                // 'useTLS' => true,
                'host' => '127.0.0.1',
                'port' => 6001,
                'scheme' => 'http',
                'curl_options' => [
                    CURLOPT_SSL_VERIFYHOST => 0,
                    CURLOPT_SSL_VERIFYPEER => 0,
                ]
            ],
        ],

bootstrap.js:

import Echo from 'laravel-echo';

window.Pusher = require('pusher-js');
window.Echo = new Echo({
    broadcaster: 'pusher',
    key: process.env.MIX_PUSHER_APP_KEY,
    cluster: process.env.MIX_PUSHER_APP_CLUSTER,
    forceTLS: true,
    wsHost: window.location.hostname,
    wsPort: 443,
    disableStats: true,
});

From the page script which works okay:

var echo = Echo;
socketId = echo.socketId();

The part that doesn't:

echo.channel(sponsorId)
    .listen('UserDisconnected', (e) => {
        [code redacted here]
    })
    .listen('UserJoinedRoom', (e) => {
       [code redacted here]
        }

The event would be triggered with something like this:

            $message = [
                    "event" => "userjoinedroom",
                    "data" => [
                        'circle_user_id' =>$request->circle_user_id,
                        'room_id' => $room_id,
                        'room_user_count' => $room_user_count,
                        'room_name' => $room_name_obj->room_name,
                        'user_full_name' => $user_full_name,
                        'total_room_count' => $total_room_count,
                        'total_user_count' => $total_user_count
                    ]
                ];

            event(new UserJoinedRoom($message));

UserJoinedRoom.php:

<?php

namespace App\Events;

use Illuminate\Broadcasting\Channel;
use Illuminate\Broadcasting\InteractsWithSockets;
use Illuminate\Broadcasting\PresenceChannel;
use Illuminate\Broadcasting\PrivateChannel;
use Illuminate\Contracts\Broadcasting\ShouldBroadcast;
use Illuminate\Foundation\Events\Dispatchable;
use Illuminate\Queue\SerializesModels;

class UserJoinedRoom implements ShouldBroadcast
{
    use Dispatchable, InteractsWithSockets, SerializesModels;

    public $message;

    /**
     * Create a new event instance.
     *
     * @return void
     */
    public function __construct($message)
    {
        $this->message = $message;
    }

    /**
     * Get the channels the event should broadcast on.
     *
     * @return Channel|array
     */
    public function broadcastOn()
    {
        return new Channel('2c1bbbc5-50b8-4b1b-8b44-469ecb9e782c');
    }
}

The channel names for all the events are all the same and hard-coded at the moment. Thank you for taking a look at this.

[garrettboone]

Also, I have it running behind an NGINX reverse proxy so it can be http locally.

[rennokki]

wsPort: 443 should match the 6001 port you set in broadcasting.php

[garrettboone]

But 6001 on the server is not open to the public, so I have 443, which redirects to 6001 via NGINX. And this has worked previously. Nothing changed with anything I showed above.

[garrettboone]

I have also attempted to troubleshoot by removing various listeners to see if that might work. But nothing. No errors in Laravel. No failed jobs. It's all very weird. I have no errors on the server...it's as if the browsers cannot hear...but the Dashboard is hearing fine.

[rennokki]

Okay, so you're terminating the SSL at the nginx level, while upgrading the request there to point from '/some-route' to :6001 ?

[garrettboone]

NGINX config:

upstream backend {
    server app:6001;
}

server {
    listen 80 default_server;
    listen [::]:80 default_server;

    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;
    server_name www.mydomain.com;
    return 301 https://mydomain.com;

    ssl_certificate         /etc/nginx/ssl/fullchain.crt;
    ssl_certificate_key     /etc/nginx/ssl/private.key;
}

server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;
    server_name mydomain.com;

    ssl_certificate         /etc/nginx/ssl/fullchain.crt;
    ssl_certificate_key     /etc/nginx/ssl/private.key;
    ssl_session_timeout     1d;
    ssl_session_cache       shared:MozSSL:10m;  # about 40000 sessions
    ssl_session_tickets     off;

    # curl https://ssl-config.mozilla.org/ffdhe2048.txt > /path/to/dhparam
    ssl_dhparam             /etc/nginx/ssl/dhparam.pem;

    # intermediate configuration
    ssl_protocols TLSv1.2 TLSv1.3;
    ssl_ciphers blah blah
    ssl_prefer_server_ciphers off;

    # HSTS (ngx_http_headers_module is required) (63072000 seconds)
    add_header Strict-Transport-Security "max-age=63072000" always;

    # OCSP stapling
    #ssl_stapling on;
    #ssl_stapling_verify on;

    # verify chain of trust of OCSP response using Root CA and Intermediate certs
    #ssl_trusted_certificate /path/to/root_CA_cert_plus_intermediates;

    root /var/www/public;

    index index.php index.html;

    error_log  /var/log/nginx/error.log;
    access_log /var/log/nginx/access.log;

    location ~ \.php$ {
        try_files $uri =404;
        fastcgi_split_path_info ^(.+\.php)(/.+)$;
        fastcgi_pass app:9000;
        fastcgi_index index.php;
        include fastcgi_params;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        fastcgi_param PATH_INFO $fastcgi_path_info;
    }

    location / {
        try_files $uri $uri/ /index.php?$query_string;
        gzip_static on;
    }


    # Laravel-Websockets
    location /app/ {
        proxy_pass              http://backend;
        proxy_set_header Host   $host;
        proxy_read_timeout      60;
        proxy_connect_timeout   60;
        proxy_redirect          off;

        # Allow the use of websockets
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
    }
}

[garrettboone]

"app" is a docker container in the same network as the NGINX container.

[garrettboone]

The Dashboard is connecting fine...and the terminal will display the message if the Dashboard is open. It will not display if the Dashboard is closed. Like when someone disconnects, I send out a message that they have.

After a user connects, it will push a UserJoinedRoom message.

But there's nothing to the client.

[garrettboone]

The connection is enough to tell the server the user is connected/disconnected. Not enough to receive anything.

From terminal:

New connection opened for app key G2EaV3X1J9o4FQNc15qccJf6WTD65Z0bno7VLhdchgkCJmK0MKLz9KawNZZ4.
Connection id 793860585.654826152 sending message {"event":"pusher:connection_established","data":"{\"socket_id\":\"793860585.654826152\",\"activity_timeout\":30}"}
Connection id 954020721.148366898 sending message {"event":"log-message","channel":"private-websockets-dashboard-connection","data":{"type":"connection","time":"15:31:24","details":"Origin: http:\/\/mydomain.co","socketId":"793860585.654826152"}}

[garrettboone]

@rennokki I resolved the problem - the call to a function got moved. This has been an error on my part. Thank you for your help - maybe my posting of NGINX template will help others. Everything in the package is working okay. I will try to pay it forward when I see a chance.

Is there anything you think I can help with right now?