Skip to content

How to fix "RangeError: Invalid Websocket frame: invalid payload length 126" In NestJS GraphQL Subscription (graphql-ws) #243

Answered by enisdenjo
omizha asked this question in Q&A
Discussion options

You must be logged in to vote

An error occurred during the massage handling phase and its message is too long. Luckily, with v5.5.1, the transmitted error message is limited and is logged to the console. You should update graphql-ws to prevent the length exception and see the original error.

Additionally, with v5.5.4, all emitted errors events (both on the WebSocket server and each distinct socket) will have the transmitted messages limited and errors will be logged to the console. Please update the graphql-ws version.

Replies: 4 comments 14 replies

Comment options

You must be logged in to vote
2 replies
@omizha
Comment options

@enisdenjo
Comment options

Comment options

You must be logged in to vote
1 reply
@omizha
Comment options

Comment options

You must be logged in to vote
9 replies
@CristianCiubancan
Comment options

@CristianCiubancan
Comment options

@enisdenjo
Comment options

@enisdenjo
Comment options

@enisdenjo
Comment options

Comment options

You must be logged in to vote
2 replies
@CristianCiubancan
Comment options

@CristianCiubancan
Comment options

Answer selected by enisdenjo
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
bug Something isn't working
3 participants