-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Laravel reverb not working with SSL on production with apache #288
Comments
Facing the same issue. It works with the "root" user. |
Could you please explain how you did with the root user? I also have root access. I also tried using root access but it didn't work. |
I just ran npm install and npm run build on production, and the problem is solved. |
Running above is not working. I've configured it with SSL (Self Signed Certificate) Configure Echo:
broadcasting.php
reverb.php
ssl.conf
BroadcastOnUi.php
app.js
|
Hi there, Thanks for reporting the problem you are encountering, but it looks like this is a question which may be better suited for a support channel. We only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repository you can try one of the following channels: However, this issue will not be locked and everyone is still free to discuss solutions to your problem! Thanks. |
Reverb Version
1.0
Laravel Version
11.29
PHP Version
8.3.12
Description
I am using Let's Encrypt SSL. PHP 8.3.12 — Laravel 11.29.0
In terminal after running: php artisan reverb:start --debug
It shows: Starting server on 0.0.0.0:8080 (example.com).
Getting this error in the console of the receive-notification blade file.
WebSocket connection to 'wss://localhost:8080/app/m0ym3fxag51pkwyz7n6u?protocol=7&client=js&version=8.4.0-rc2&flash=false' failed:
Steps To Reproduce
My event code
.env file
echo.js file
receive-notification.blade.php JavaScript code
virtual host conf file
The text was updated successfully, but these errors were encountered: