@tony98ms I have the following: (I have my app running in a docker container, with Reverb running on, and exposed to the host on port 18020). My app is (naturally) being accessed via HTTPS

env config:

REVERB_APP_ID="######"
REVERB_APP_KEY="############"
REVERB_APP_SECRET="##############"
REVERB_HOST="your.domain.tld"
REVERB_PORT="18020"
REVERB_SCHEME="http"
VITE_REVERB_APP_KEY="############"
VITE_REVERB_HOST="your.domain.tld"
VITE_REVERB_PORT="443"
VITE_REVERB_SCHEME="http"

Important note here, the VITE_REVERB_PORT so that we can accept secure WS (wss) connections. If your app is being served over HTTPS (even if that's just behind a proxy doing the HTTPS), then the websockets will need to be handled by WSS rather than WS.

My nginx proxy config contains the following location (this is within my app's main server {} block:

location ~ /app/(?<reverbkey>.*) { # variable reverbkey
    proxy_pass http://0.0.0.0:18020/app/$reverbkey;
    proxy_http_version 1.1;
    proxy_set_header Host $http_host;
    proxy_set_header Scheme $scheme;
    proxy_set_header SERVER_PORT $server_port;
    proxy_set_header REMOTE_ADDR $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
}

Exploring Laravel Reverb