You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
I'm working with redis, laravel-echo-server, and laravel. I'm trying to listen on private channels from another computer, i have my "laravel-echo-server.json" in one computer. When i'm trying to listen on my private channels from my other computer i automatically have this error :
Client can not be authenticated, got HTTP status 403
Even if i have just a 'return true;' on both of my "channels.php" files.
This package seems to be abandoned. I have initially forked the app, but I found out how inefficient is Socket.IO, and managed to create an open-source Pusher alternative (that doesn't require Pusher credentials) that can be deployed anywhere for free. This does require the driver to be switched from Socket.IO to Pusher. Not sure if it helps, but I wanted to spread the word about it. 😁 Read more about it here.
I'm working with redis, laravel-echo-server, and laravel. I'm trying to listen on private channels from another computer, i have my "laravel-echo-server.json" in one computer. When i'm trying to listen on my private channels from my other computer i automatically have this error :
Even if i have just a 'return true;' on both of my "channels.php" files.
Here's my laravel-echo-server.json file :
PS : I have no problem with public channels (only with private channels).
The text was updated successfully, but these errors were encountered: