Laravel Reverb on Laravel Forge

I was also not able to make it work.

Here is what I have done:

• Register the ws-subdomain, so ws.xxx.de and point it to my application server (just like the main domain xxx.de does).
• Make sure that a certificate for both domains is installed in the SSL tab.
• Prepare my env file as follows:

REVERB_APP_ID=XXX REVERB_APP_KEY=XXX REVERB_APP_SECRET=XXX

VITE_REVERB_APP_KEY="${REVERB_APP_KEY}" VITE_REVERB_HOST="${REVERB_HOST}" VITE_REVERB_PORT="${REVERB_PORT}" VITE_REVERB_SCHEME="${REVERB_SCHEME}"

• Then hit the "Laravel Reverb" toggle on the "Laravel" panel. It promted the ws subdomain and the port 8080, as seen here https://forge.laravel.com/docs/sites/applications.html#laravel-reverb.

• I have then checked that the env has beed extended with: REVERB_HOST=ws.xxx.de REVERB_PORT=443 REVERB_SCHEME="https"

• Lastly I deployed my site so that npm run build makes use of the new port in the env.

But unfortunately, I still receive the following error in the frontend: app-Qkal0qg7.js:12 WebSocket connection to 'wss://ws.xxx.de/app/hwybqtva5n4dru43ayiz?protocol=7&client=js&version=8.4.0-rc2&flash=false' failed

I have also check the servers daemon for the reverb process and it has output the following: INFO Starting server on 0.0.0.0:8080 (ws.xxx.de).

My nginx config was not edited by forge in the process of activating reverb. Should it have been? EDIT: @brianhollenbach I have just received a message from Mohamed: "Forge adds the reverb nginx configuration inside /etc/nginx/forge-conf/site_name/after. It doesn't modify the original Nginx configuration file."

Okay so I have been trying a few different things but still not functioning.

In postman I get the following: Could not connect to wss://ws.xxxx.xxxx.xxx:8080/app/qwertyqwerrtysad Error: write EPROTO 5388810984:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:../../../../src/third_party/boringssl/src/ssl/tls_record.cc:594:SSL alert number 40 5388810984:error:1000009a:SSL routines:OPENSSL_internal:HANDSHAKE_FAILURE_ON_CLIENT_HELLO:../../../../src/third_party/boringssl/src/ssl/handshake.cc:644: Handshake Details Request URL: https://ws.xxxx.xxxx.xxx:8080/app/qwertyqwerrtysad Request Method: GET Request Headers Sec-WebSocket-Version: 13 Sec-WebSocket-Key: xxxxxxxxxxxxxxxx Connection: Upgrade Upgrade: websocket Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits Host: ws.xxxx.xxxx.xxx:8080

Also: Could not connect to wss://ws.xxxx.xxxx.xxx/app/qwertyqwerrtysad 21:08:38 Error: Unexpected server response: 502 Handshake Details Request URL: https://ws.xxxx.xxx/app/qwertyqwerrtysad Request Method: GET Status Code: 502 Bad Gateway Request Headers Sec-WebSocket-Version: 13 Sec-WebSocket-Key: xxxxxxxxxxxxxxxx Connection: Upgrade Upgrade: websocket Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits Host: ws.xxxx.xxxx.xxx Response Headers Server: nginx Date: Wed, 03 Apr 2024 19:08:38 GMT Content-Type: text/html; charset=utf-8 Content-Length: 150 Connection: keep-alive

I followed the steps that has been kindly provided by @marven but still no luck.

I have an ssl for both dns addresses and this is the env: REVERB_HOST=ws.xxxx.xxxx.xxx REVERB_PORT=443 REVERB_SERVER_PORT=8080 REVERB_SCHEME="https"

VITE_REVERB_APP_KEY="${REVERB_APP_KEY}" VITE_REVERB_HOST="${REVERB_HOST}" VITE_REVERB_PORT="${REVERB_PORT}" VITE_REVERB_SCHEME="${REVERB_SCHEME}"

The level of frustration is so unreal as my local environment is working and just mocking me

I've got it working on Laravel 10 deployed on Forge.

What finally seemed to get it to work was

• having the valid SSL cert for ws.mydomain.com verified in the Forge UI
• removing all the reverb related env variables and saving
• turning off reverb in the Forge UI
• turning reverb back on in the Forge UI

Some issues I encountered:

• Make sure you set up the subdomain as an A record and not a CNAME
• Don't forget to add "BROADCAST_CONNECTION=reverb BROADCAST_DRIVER=reverb" into your production env file

I highly recommend setting up the subdomain and A record, then verifying the SSL cert BEFORE you turn on reverb in the Forge UI. It seemed to handle the nginx and env variables correctly when done in that order.

I tried everything above, but I could still not get it to work.

I ended up getting it to work by following this guide (https://tonymasek.com/blog/how-to-make-laravel-reverb-work-on-laravel-forge) that I found here: https://laracasts.com/discuss/channels/reverb/problem-with-laravel-reverb-and-forge.

I have tried everything above but still doesnt work. it shows that it is connected but it is not broadcasting.

An chance anyone has a consistent solutions or cause of this issue? i really appreciate it. thanks

Just in case anyone else is still have problems, one of the things that tripped me up is that whilst npm run dev looks like it's updating if you change a .env file, it needs restarting if you are passing a variable through to vite (i.e. one starting VITE_)

I was having problems getting it working in production with forge and also in development with sail so in case its useful to anyone here is my settings:

javascript

import Echo from 'laravel-echo';
import Pusher from 'pusher-js';
window.Pusher = Pusher;

window.Echo = new Echo({
    broadcaster: 'pusher',
    wsHost: import.meta.env.VITE_REVERB_HOST || window.location.hostname,
    wsPort: import.meta.env.VITE_REVERB_PORT,
    wssPort: import.meta.env.VITE_REVERB_PORT,
    key: import.meta.env.VITE_REVERB_APP_KEY,
    cluster: import.meta.env.VITE_REVERB_CLUSTER,
    forceTLS: false,
    disableStats: false,
    enabledTransports: ['ws', 'wss'],
});

In sail

.env

REVERB_APP_ID=
REVERB_APP_KEY=
REVERB_APP_SECRET=

REVERB_CLUSTER=mt1
REVERB_SCHEME=http
REVERB_HOST=localhost
REVERB_PORT=8080
REVERB_SERVER_PORT=8080
REVERB_SERVER_HOST=0.0.0.0

VITE_REVERB_APP_KEY="${REVERB_APP_KEY}"
VITE_REVERB_HOST="${REVERB_HOST}"
VITE_REVERB_PORT="${REVERB_PORT}"
VITE_REVERB_SCHEME="${REVERB_SCHEME}"
VITE_REVERB_CLUSTER="${REVERB_CLUSTER}"

added to docker-compose.yml

services:
    laravel:
        build:
            context: ./vendor/laravel/sail/runtimes/8.2
            dockerfile: Dockerfile
            args:
                WWWGROUP: '${WWWGROUP}'
        image: sail-8.2/app
        extra_hosts:
            - 'host.docker.internal:host-gateway'
        ports:
            - '${APP_PORT:-80}:80'
            - '${VITE_PORT:-5173}:${VITE_PORT:-5173}'
            - '${REVERB_SERVER_PORT:-8080}:8080'
...

In production on forge

.env

REVERB_APP_ID=my-app-id
REVERB_APP_KEY=my-app-key
REVERB_APP_SECRET=my-app-secret

REVERB_CLUSTER=mt1
REVERB_SCHEME="https"
REVERB_HOST=ws.xxx.co.uk
REVERB_PORT=443
REVERB_SERVER_PORT=8080

VITE_REVERB_APP_KEY="${REVERB_APP_KEY}"
VITE_REVERB_HOST="${REVERB_HOST}"
VITE_REVERB_PORT="${REVERB_PORT}"
VITE_REVERB_SCHEME="${REVERB_SCHEME}"
VITE_REVERB_CLUSTER="${REVERB_CLUSTER}"

On forge I also ended up having to spin up a new server and start from scratch as my nginx config file had got so mangled, but once I'd done that I did just click on the reverb button under sites and it worked a dream (eventually)

The amount of time I have spent on this is crazy, but then I really don't know much about ports! Good Luck

Oh - and I can only get it working on a fresh DO droplet. Anything old just doesn't want to work.

For me the problem was that I was trying to use a CloudFlare origin certificate. I tried both the wildcard(*) version and I also tried adding each ws. subdomain separately. It seems that CloudFlare origin certificates just don't work with Laravel Forge's Reverb at the moment.

Using Letsencrypt worked fine, you just might need to generate a fresh certificate to ensure your ws subdomain is covered.