Open icreatestuff opened 2 years ago
Have you set the Echo's authEndpoint in your window.Echo params?
@nandorossetti It's using the default /broadcasting/auth
at the moment, should it be set to something else when using this package?
Specify explicitly the authEndpoint and test by logging the authEndpoint path in case it happens to be failing.
I was using a Presence Channel and have since simplified things for testing to use a regular Channel. I'm still getting Internal Server Error
messages in the websocket responses after a successful connection similar to @nandorossetti issue here .
I had this happen when connecting from my local machine and my APP_KEY did not match the one deployed.
Do you still experience this issue ?
@Adesin-fr I've never experienced this one myself :)
We're using Laravel Vapor and have followed the installation and setup instructions in the README.md to setup the DynamoDB table, API Gateway and updated IAM role as well as include the 4 .env variables to set the broadcast drive, DB table, Gateway API ID and stage.
Having installed both the composer and NPM packages we've then setup our JS with the following:
Our
BrodcastServiceProvider.php
containsand our
routes/channels.php
hasWhen viewing the developer console we're seeing a few logged messages and then an
Invalid auth signature
error. The console logs read as:Looking at the Network activity I can see the request to
/broadcasting/auth
sends thechannel_name
andsocket_id
and returns withauth
andchannel_data
.Inspecting the WebSocket network activity I see a request to our configured
wss://{api-ip}.execute-api.{region}.amazonaws.com/{stage}
Gateway API (with the variables replaced). This returns with the following data:For what it's worth we're running:
I'm not sure where things are going wrong so any help would be greatly appreciated. Many thanks.