Closed skillcraft-io closed 5 years ago
Interestingly this went away when I set up the WebSocket server on a remote machine. Not entirely sure why it went away but is not an issue so I am closing. Perhaps this was a fallback call with something that was not configured correctly.
Pusher libs fallback to pusher.com if they can't connect.
You can stop that by setting the enabled transports to ws
& wss
like mentioned here for example: https://github.com/beyondcode/laravel-websockets/issues/96#issuecomment-455920950
It appears that there is still a call to socketjs.pusher.com... is this normal? Why is it this call, from the documentation this package replaces the need for a pusher account or did I miss something here?
My socket server is getting my requests, and my frontend is updating according to my expectations, I am just concerned with the push call.