laravel-echo-api-gateway icon indicating copy to clipboard operation
laravel-echo-api-gateway copied to clipboard

Channel connected but message doesn't been received

Open nandorossetti opened this issue 2 years ago • 11 comments

Good evening,

I am following the steps as they come in the readme. I manage to do everything but when the time comes, it connects me to the channel but the messages through the "notify" event in my case does not arrive.

This is my stacktrace:

just set socketId to JIj6rfzuiGYCE5Q= Subscribing to channels App.User.211 Received event subscription_succeeded on channel App.User.211

Captura de pantalla 2021-11-21 a las 3 55 38

Please, help me. Thanks

nandorossetti avatar Nov 21 '21 02:11 nandorossetti

Morning!

I'm still debbuging with a "normal" channel and the websocket returns "Internal server error".

Captura de pantalla 2021-11-21 a las 11 05 04

nandorossetti avatar Nov 21 '21 10:11 nandorossetti

@nandorossetti any sucess ?

nenads avatar Dec 22 '21 17:12 nenads

I will try again in a few days, I think that could be a pusher and debugbar incompatibility issue, but I'm not 100% secure.

nandorossetti avatar Dec 23 '21 09:12 nandorossetti

Execution failed due to configuration error: Malformed Lambda proxy response

Do you have this errors in Cloud Watch ? Enable logging for API Gateway

nenads avatar Dec 23 '21 16:12 nenads

Hi @nenads Now, I get this error for private and presence channel.

Axios Error

nandorossetti avatar Jan 07 '22 23:01 nandorossetti

Morning!

I'm still debbuging with a "normal" channel and the websocket returns "Internal server error".

Captura de pantalla 2021-11-21 a las 11 05 04

@nandorossetti this is what I'm seeing at the moment. Did you manage to get past this?

icreatestuff avatar Feb 03 '22 16:02 icreatestuff

I still have this error. I'm on Pusher by the moment.

nandorossetti avatar Feb 03 '22 16:02 nandorossetti

@nandorossetti understood. I've just followed @nenads advice to enable CloudWatch logging for the API Gateway and that does show me a Execution failed due to configuration error: Malformed Lambda proxy response response.

One piece of the README that I wasn't 100% sure on was related to the setup of the API Gateway where it reads Create a new Websocket API. Enter a name and leave the route selection expression to what it is.. When I created the API Gateway this field had a placeholder value of $request.body.action, which I had to type in manually otherwise I couldn't progress through the setup process. Assuming I've got that right I can't see where I've got any of the setup steps wrong.

@georgeboot any clues to where we need to look to debug?

icreatestuff avatar Feb 03 '22 16:02 icreatestuff

Presance channel is not implemented if I understand.

Private one works.

nenads avatar Mar 01 '22 19:03 nenads

I also see this Internal Server Error with Execution failed due to configuration error: Malformed Lambda proxy response in the API Gateway logs. Everything works as expected, but how can we resolve this error? Where exactly is the malformed request coming from?

michaelaguiar avatar Sep 16 '22 19:09 michaelaguiar

This is still a thing, but it doesn't work at all for me now.

image

Any help appreciated.

tntsoft avatar Nov 16 '22 07:11 tntsoft