-
Notifications
You must be signed in to change notification settings - Fork 90
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
PusherBroadcaster 404 Error on Production Server #112
Comments
Hi @dysTOS, what does your Nginx (or equivalent) configuration look like? |
Thanks for your reply @joedixon ! I have upgraded laravel/framework to 11.0.8 and did some changes to my webserver-configuration and .env variables, but went back to settings i already had before in the end, so unfortunately I am not sure what solved this issue exactly. Here are my current configurations and relevant settings: Backend: api.example.com (running in a Plesk Environment with Apache + Nginx as reverse proxy) Frontend (Typescript)
Laravel .env
Laravel routes/channels.php
Laravel Providers/BroadcastServiceProvider.php
PLESK additional Nginx directives
Tried also with additional 'location /apps/', 'location /ws/', 'location /wss/' and same content, but it seems that /app/ is sufficient. BUT there is still one issue - from 10 sent notifications only an average of 2 to 3 messages are received by my frontend - found no log-entries or failed jobs. |
@joedixon please forget my last sentence - EVERY message is sent but it took up to 10 minutes until the last message was received by my frontend application. I will have a look on this and open a new issue if needed. Have a nice day! :-) |
Reverb Version
1.x
Laravel Version
11.0.7
PHP Version
8.2
Description
First, I already have a fully working reverb websocket connection when developing locally - Private-Channels, Authentication, Notifications, SSL - everything works like a charm. My frontend is a seperate angular-application running on a different subdomain.
On my production server the websocket connection is also established as it should be. BUT when firing a notification that should be broadcasted via reverb, the queued job fails with the following error:
I already thought of a problem in the .env file - but I could not find a solution so far...
Steps To Reproduce
sorry for missing out that
The text was updated successfully, but these errors were encountered: