Laravel Reverb on Hestia Panel

[tayfunyazici]

I have created a sample laravel 11 project and in which I have configured all the requirements for the laravel reverb.

In local machine/setup reverb is working fine. when I deployed in production server (Hestia server using Nginx + Apache2 + PHP FPM) for testing I am getting the bellow error.

• tried with and without https for reverb hosting server
• tried reverb server host as '0.0.0.0'

.env

REVERB_HOST="website.com"
REVERB_PORT=443
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}"

config/reverb.php

  'default' => env('REVERB_SERVER', 'reverb'),

   'servers' => [

       'reverb' => [
           'host' => env('REVERB_SERVER_HOST', '127.0.0.1'),
           'port' => env('REVERB_SERVER_PORT', 8085),
           'path' => env('REVERB_SERVER_PATH', ''),
           'hostname' => env('REVERB_HOST'),
           'options' => [
               'tls' => [],
           ],
           'max_request_size' => env('REVERB_MAX_REQUEST_SIZE', 10_000),
           'scaling' => [
               'enabled' => env('REVERB_SCALING_ENABLED', false),
               'channel' => env('REVERB_SCALING_CHANNEL', 'reverb'),
               'server' => [
                   'url' => env('REDIS_URL'),
                   'host' => env('REDIS_HOST', '127.0.0.1'),
                   'port' => env('REDIS_PORT', '6379'),
                   'username' => env('REDIS_USERNAME'),
                   'password' => env('REDIS_PASSWORD'),
                   'database' => env('REDIS_DB', '0'),
                   'timeout' => env('REDIS_TIMEOUT', 60),
               ],
           ],
           'pulse_ingest_interval' => env('REVERB_PULSE_INGEST_INTERVAL', 15),
           'telescope_ingest_interval' => env('REVERB_TELESCOPE_INGEST_INTERVAL', 15),
       ],

   ],

   'apps' => [

       'provider' => 'config',

       'apps' => [
           [
               'key' => env('REVERB_APP_KEY'),
               'secret' => env('REVERB_APP_SECRET'),
               'app_id' => env('REVERB_APP_ID'),
               'options' => [
                   'host' => env('REVERB_HOST'),
                   'port' => env('REVERB_PORT', 443),
                   'scheme' => env('REVERB_SCHEME', 'https'),
                   'useTLS' => env('REVERB_SCHEME', 'https') === 'https',
               ],
               'allowed_origins' => ['*'],
               'ping_interval' => env('REVERB_APP_PING_INTERVAL', 60),
               'activity_timeout' => env('REVERB_APP_ACTIVITY_TIMEOUT', 30),
               'max_message_size' => env('REVERB_APP_MAX_MESSAGE_SIZE', 10_000),
           ],
       ],

   ],

];

nginx.ssl.conf

server {
        listen      IP ssl;
        server_name paraphly.com www.paraphly.com;
        error_log   /var/log/apache2/domains/paraphly.com.error.log error;

        ssl_certificate     /home/paraphly/conf/web/paraphly.com/ssl/paraphly.com.pem;
        ssl_certificate_key /home/paraphly/conf/web/paraphly.com/ssl/paraphly.com.key;
        ssl_stapling        on;
        ssl_stapling_verify on;

        # TLS 1.3 0-RTT anti-replay
        if ($anti_replay = 307) { return 307 https://$host$request_uri; }
        if ($anti_replay = 425) { return 425; }

        include /home/paraphly/conf/web/paraphly.com/nginx.hsts.conf*;

        location ~ /\.(?!well-known\/|file) {
                deny all;
                return 404;
        }

location /app {
        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";

        proxy_pass http://127.0.0.1:8085;
}

        location / {
                proxy_pass https://IP;

                location ~* ^.+\.(css|htm|html|js|mjs|json|xml|apng|avif|bmp|cur|gif|ico|jfif|jpg|jpeg|pjp|pjpeg|png|svg|tif|tiff|webp|aa>
                        try_files  $uri @fallback;

                        root       /home/paraphly/web/paraphly.com/public_html/public;
                        access_log /var/log/apache2/domains/paraphly.com.log combined;
                        access_log /var/log/apache2/domains/paraphly.com.bytes bytes;

                        expires    max;
                }
        }

        location @fallback {
                proxy_pass https://IP;
        }

        location /error/ {
                alias /home/paraphly/web/paraphly.com/document_errors/;
        }

        proxy_hide_header Upgrade;

        include /home/paraphly/conf/web/paraphly.com/nginx.ssl.conf_*;
}

[usamasaleem777]

We investigated the issue with Laravel Reverb failing to establish private channel connections behind the Nginx reverse proxy on a Hestia Panel-based VPS. After a thorough review, here’s a clear breakdown of the root cause and proposed fix:

Reverb Configuration Mismatch
Laravel Reverb was configured to connect over HTTPS and port 443, but the Reverb server was actually running locally on port 8085 without TLS. This mismatch caused connection failures from the frontend client.

Improper Reverse Proxy Setup in Nginx
While Nginx was set to proxy WebSocket connections at /app, it lacked some critical headers needed to upgrade HTTP to WebSocket, which are essential for real-time features like private channels.

Frontend WebSocket URL Conflict
The JavaScript client was attempting to connect securely (wss://) directly to Reverb, but Reverb itself wasn’t using SSL — instead, the SSL termination was happening at Nginx. This caused the browser to block the connection.

Authorization Endpoint Not Accessible or Misconfigured
Laravel Echo’s attempt to authenticate private channels failed due to the server not correctly handling or protecting the /broadcasting/auth endpoint.

[drsdre]

According to the Laravel Reverb documentation "Reverb listens for WebSocket connections at /app and handles API requests at /apps.".

Therefore I propose to use the following location definition:
location ~ ^/apps?(/.*)?$ {

[tayfunyazici]

I couldn't resolve the issue and preferred docker instead

[usamasaleem777]

If you want I will resolve your issue but I charge small amount and I will resolve the issue in 1 day only