please check the logs to find more details about the problem. check the server side and see if the reverb is broadcasting fine. first check with public channel. if the public channel is working then go to private channel
Hello Sir, my websocket connection is being established, and the command is running successfully, but the event is not being triggered on the frontend. backend event trigger successfully There are no issues in the console or the Laravel log file.
@@WildNatureNP will it's hard to say. because I don't have much information about your hosting or projects. but normally it won't change or affect anything else
@@eraufi hmm. interesting. the thing is this is running perfectly fine in local, but when i put it on server, always getting this same error. websocket is closed before connection is established
@@eraufi Yes, I watched it and was very happy to see that you had the same problem as me. However, when I replicated the solution just like you, I was not successful. When I am using HTTP, everything works. Reverb works over WS. But when I activate the site's SSL, Reverb stops working over HTTP and forces it to use WSS. And then I did the procedure for the certificates and SSL correctly, just like in the video (but with my domain and files). And now the site is in HTTPS and Reverb is also in WSS. However, it is not connecting. Same problem as in your video.
@@lksccb thanks for the replay. I faced this problem before and I had a tough time finding the solution. after finding the solution i made a video about it so for others it should be easy to solve it. could you please share the solution in here when ever you solve it?
@@eraufi Yes, I can come back. I also had this problem in production once. Before Reverb, back in the Pusher era. And I remember that I had a hard time solving it. Honestly, I'm almost giving up on this. It seems to be a chronic problem with Laravel when it comes to configuring Websockets with SSL. Unfortunately, I don't remember how I solved it, but if I manage to solve my problem, I'll come back here to explain. As I said, if the project is running on SSL, the browser forces the use of WSS even if you want to use WS.
@@lksccb thanks you very much. one time i remembered in one of my laravel 10 projects i faced this problem. after searching a lot i solved it just by opening websocket link and port in the browser. for example like this www.myproject.come:8080 it registered the SSL in the browser and everything worked fine
@ I am using Nginx in production on a VPS server. However, it connects on some devices but not on others. For example, in the current situation: • On iOS: Reverb works perfectly in all browsers. • On desktop: It connects only on Firefox. • On Android: It does not connect on any browser. (wss) I believe it might be something specific to the browser. Do you know what could be causing this?
thanks for pointing this. you don't have to use additional certificate for reverb websocket you only need one certificate which should not be self singed certificate
I have done all these things
It is always showing this error message `Pusher error: Not found..` whenever the code hits broadcasting
please check the logs to find more details about the problem.
check the server side and see if the reverb is broadcasting fine.
first check with public channel.
if the public channel is working then go to private channel
I like that thanks 😮😮😮
thanks
Hello Sir, my websocket connection is being established, and the command is running successfully, but the event is not being triggered on the frontend. backend event trigger successfully There are no issues in the console or the Laravel log file.
have you watched and tried the 41:10 Solving Common Problems ?
because if every thing is working fine from the backed then these will solve it
Laravel reverb work fine in web using Laravel Echo. But How can we use Laravel Reverb Socket Notification in Mobile Application Android/iOS?
i am sorry but i don't have any experience with mobile applications
i am getting the error
WebSocket is closed before the connection is established.
when deployed on server.
try adding a timeout for 300 or 500 milliseconds in the client side if the problem is not solved please watch
41:10 Solving Common Problems
@@eraufi thanks for the reply
i see our private hosting have more than 2 websites running already on it. will it change or affect anything?
@@WildNatureNP will it's hard to say. because I don't have much information about your hosting or projects. but normally it won't change or affect anything else
@@eraufi hmm. interesting.
the thing is this is running perfectly fine in local, but when i put it on server, always getting this same error.
websocket is closed before connection is established
i am not able to get the not found when put on domainname:port
Sh!t. for me not works. CloudPanel. Installed certificates, and wss problem like on video. but not working with solution.
sorry to hear that. but have you watched and applied 41:10 Solving Common Problems
@@eraufi Yes, I watched it and was very happy to see that you had the same problem as me. However, when I replicated the solution just like you, I was not successful.
When I am using HTTP, everything works. Reverb works over WS.
But when I activate the site's SSL, Reverb stops working over HTTP and forces it to use WSS. And then I did the procedure for the certificates and SSL correctly, just like in the video (but with my domain and files). And now the site is in HTTPS and Reverb is also in WSS. However, it is not connecting. Same problem as in your video.
@@lksccb thanks for the replay.
I faced this problem before and I had a tough time finding the solution. after finding the solution i made a video about it so for others it should be easy to solve it.
could you please share the solution in here when ever you solve it?
@@eraufi Yes, I can come back. I also had this problem in production once. Before Reverb, back in the Pusher era. And I remember that I had a hard time solving it. Honestly, I'm almost giving up on this. It seems to be a chronic problem with Laravel when it comes to configuring Websockets with SSL. Unfortunately, I don't remember how I solved it, but if I manage to solve my problem, I'll come back here to explain.
As I said, if the project is running on SSL, the browser forces the use of WSS even if you want to use WS.
@@lksccb thanks you very much.
one time i remembered in one of my laravel 10 projects i faced this problem. after searching a lot i solved it just by opening websocket link and port in the browser.
for example like this
www.myproject.come:8080
it registered the SSL in the browser and everything worked fine
How to host run this same linux server any other server without whm, plz make video on this
hi .
thanks a lot for the comment. i will make it in the future
@eraufi how much
Please, do it on Nginx! The connection isn't working!
And Nginx uses ports 8080 and 443
i am sorry but i don't have a vps. the one the i used for this video was provided by one of my viewers.
@ I am using Nginx in production on a VPS server.
However, it connects on some devices but not on others. For example, in the current situation:
• On iOS: Reverb works perfectly in all browsers.
• On desktop: It connects only on Firefox.
• On Android: It does not connect on any browser. (wss)
I believe it might be something specific to the browser. Do you know what could be causing this?
@@KesleyWp thanks for telling me about this i will do some research and I will let you know if i find anything
Can I have your apache2 configuration file
I am sorry but now i don't have access to it now
😞🥹
please how did you host it
brother all the steps are in the video
Use additional certificate for 90 days its bad idea, Pls explore question with port 443 and proxy
thanks for pointing this.
you don't have to use additional certificate for reverb websocket you only need one certificate which should not be self singed certificate