Laravel Web-sockets and Chrome `SameSite` attribute
Firstly we have to understand workflow on this operation.
Here is example;
Your laravel backend ▼[pub/sub service (can be redis pusher etc..)] ▼laravel echo server ▼websocket client ( mostly laravel echo client)On client side
Websocket (mostly laravel echo client) ▼Laravel echo server ▼http request to laravel backendIf you are trying to find trace from client side to pusher website this is not possible your client react with laravel echo server.
If you want to trace laravel echo server to pusher then you have to debug laravel echo server.
On your case, most likely pusher works fine (i been using their service for a while never seen a issue) if you want to debug that. You can use redis server and connect laravel echo to redis (and its works on your local network, way way faster then pusher)
I hope its helps.