laravel-echo-server | Socket server for laravel event broadcast | Socket library

For anyone who needs help with this problem, my above echo reconnection code seems to be pretty stable, along with a keepAlive function to determine the state of the HTTP connection. I am still a bit uncertain of the origin of the console errors I am seeing, but I suspect they have to do with connection loss during a sleep cycle, which is not something I am particularly worried about.

I'd still be interested in hearing other thoughts if anyone has any. I am somewhat inclined to believe long-term stability of an echo connection is possible, though it does appear you have to proactively monitor it with what tools you have available.

Laravel Mix 6 removes a number of options from the CLI. You will need to update the scripts section of your package.json file accordingly.

See Update Your NPM Scripts
https://laravel-mix.com/docs/6.0/upgrade#update-your-npm-scripts

Before:

Alright, this was fun solving. I decided to check how laravel-echo-server is requesting to "broadcasting/auth" and how its handling the response of that request.

You can have a look at here : https://github.com/tlaverdure/laravel-echo-server/blob/master/src/channels/private-channel.ts

So laravel-echo-server returns true if the response code of broadcasting/auth is 200 and returns false if the response code is not 200 or if there was an error requesting.

The problem here is that when you send a request to laravel api route handled by passport authentication , it does return "Unauthenticated" message but without 401 code due to which the laravel-echo-server thinks that the request was successful and allows the user to join the channel.

Solution:

1. Returning 401 Code With Passport Unauthenticated Response
2. Middleware for Channel Authentication

Returning 401 Code With Passport Unauthenticated Response

projectdir\app\Exceptions Handler.php

I was able to resolve my problem by placing this within my .htaccess

It so strange, however, I fixed it by downgrading the socket.io-client from 3.0.3 to 2.3.0

Not sure the exact reason but downgrading to v2.3.0 the solution for that situation. found the relevant issue and the solution here

I think it's not related to laravel but socket io

You can add this issue to the GitHub repository

By default, Echo will use the /broadcasting/auth endpoint to authorize channel access. If your client side is not on the same host you will have to customize the authEndpoint of pusher. You may specify your own authorization endpoint by passing the authEndpoint configuration option to your Echo instance:

I assume this is your issue.

I don't know what the problem is, but I found a solution. I've updated a lot: updated Nginx to 1.19.1, possibly installed some additional modules. Installed npm not globally, but locally. And it worked ...

Attention: this only works if you write location /socket.io.