Reverb & Filament containers behind nginx - needing help

Hi, guys, please help? I'm at my wits end.
For the past couple of days I've been trying to configure Filament notification broadcasting with reverb.

The setup:
Running Laravel with Filament in a php-fpm container, behind an instance of nginx running in another container on the same docker network + a separate container for the db.

The nginx setup, I dare say, works well enough for the Filament application, and I managed to get connected using a separate instance of echo (it creates a wss connection w/ status 101 to the app/ endpoint, to a public channel I created, and there's ping/pong traffic)

HOWEVER, what I believe to be the inbuilt echo instance of Filament (because I haven't defined a channel like private-App.Model.User shown in the payload of the request) fails to connect, throwing 403 error (and returning a 403 page I can see in the response preview).

What am I missing? What am I doing wrong? Do I need to configure some middleware? I'm stuck and going nuts over this.

I have this in my .env
BROADCAST_CONNECTION=reverb 
BROADCAST_DRIVER=reverb
QUEUE_CONNECTION=sync
REVERB_PORT=443
REVERB_SCHEME=https
REVERB_SERVER_PORT=8080
REVERB_HOST=domain.tld
REVERB_APP_ID=[set]
REVERB_APP_KEY=[set]
REVERB_APP_SECRET=[set]
REVERB_APP_ID=428119
REVERB_APP_KEY=m74l7uldbuxdnk6m7wfk
REVERB_APP_SECRET=wx16wjrhlwj4b5ns4413

the relevant bits in filament.php are:
'broadcasting' => [
          'echo' => [
              'broadcaster' => 'reverb',
              'driver' => 'reverb',
              'key' => env('VITE_REVERB_APP_KEY'),
              'cluster' => env('VITE_REVERB_APP_CLUSTER'),
              'wsHost' => env('VITE_REVERB_HOST'),
              'wsPort' => env('VITE_REVERB_PORT'),
              'wssPort' => env('VITE_REVERB_PORT'),
              'authEndpoint' => '/broadcasting/auth',
              'disableStats' => true,
              'encrypted' => true,
              'forceTLS' => true,
 ],
],
Was this page helpful?