Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Channel connected but message doesn't been received #14

Open
nandorossetti opened this issue Nov 21, 2021 · 11 comments
Open

Channel connected but message doesn't been received #14

nandorossetti opened this issue Nov 21, 2021 · 11 comments

Comments

@nandorossetti
Copy link

nandorossetti commented Nov 21, 2021

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
Copy link
Author

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

@nenads
Copy link
Contributor

nenads commented Dec 22, 2021

@nandorossetti any sucess ?

@nandorossetti
Copy link
Author

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.

@nenads
Copy link
Contributor

nenads commented Dec 23, 2021

Execution failed due to configuration error: Malformed Lambda proxy response

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

@nandorossetti
Copy link
Author

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

Axios Error

@icreatestuff
Copy link

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?

@nandorossetti
Copy link
Author

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

@icreatestuff
Copy link

@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?

@nenads
Copy link
Contributor

nenads commented Mar 1, 2022

Presance channel is not implemented if I understand.

Private one works.

@michaelaguiar
Copy link

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?

@tntsoft
Copy link

tntsoft commented Nov 16, 2022

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

image

Any help appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants