[LiveQuery]RangeError: Invalid WebSocket frame: invalid payload length 126 #6413
Comments
|
Is there a way you can view the frames or debug the socket? What client are you using? |
I use default socket on parse server. const api = new ParseServer({
databaseURI,
cloud: __dirname + '/src/cloud/', // location after tsc
appId: process.env.APP_ID,
masterKey: process.env.MASTER_KEY,
serverURL: 'http://localhost:1337/parse',
// enableAnonymousUsers: true,
liveQuery: {
classNames: ['A', 'B', 'C', 'D'],
},
auth: { apple: {
client_id: process.env.APPLE_SIGNIN_CLIENT_ID, // optional (for extra validation), use the Service ID from Apple.
},
},
maxUploadSize: '5mb',
logLevel: process.env.NODE_ENV !== 'local' ? 'warn' : undefined,
})And I did not debug frames of the socket. I will share it after digging. |
|
At least we can prevent the server from crashing when an error occurs, even if we can't replicate it. |
|
@dplewis |
|
Thanks for the feedback. Did your server crash? We can try to use the following to reverse engineer the payload that is failing. Knowing Also we should show the following for |
|
@dplewis I will attach the more samples to files. |
* Websocket: unhandle rejection Closes: parse-community#6413, parse-community#6173 Prevent crashing on websocket error. Bonus points to anybody who can post a specific payload that the client sends that returns an error. * log the socket * fix tests * fix payload reference link
|
Hello, I'm getting a similar issue with the livequery server (parse server & parse livequery server versions are I'm connecting to the livequery server from my Angular components and I sometimes get this error below, which then crashes the server and sends it into a restart loop since pm2 attempts to restart, which could last anywhere between 5 minutes to an hour after which it resolves by itself. Any ideas what this error means and how to solve it, or at least how to stop it from crashing the server without having to upgrade to a more recent parse-server version for the livequery server? If not, any idea if it's possible to run different versions of parse for the main server and the livequery server? |
|
@majidhassan Please note that Parse does not currently offer Long Terms Support and we only address issues that are reproducible with latest version of Parse Server.
LiveQuery is a feature of Parse Server, not an individual repository. Therefore I would generally recommend to use a single version of that repository. Mixing instances of different Parse Server versions using the same DB may or may not work. It is not officially documented as supported, therefore the compatibility is undefined and not recommended for production environments. |
|
@mtrezza thanks for your reply, and I understand that it's an older version. However, any ideas where to start on that error? |
|
To confirm that this is an issue we'd need to be able to reproduce this with the latest version of Parse Server and without mixing different versions of Parse Server. Then we can handle the issue here. If you need support for your custom deployment with older versions of Parse Server and/or mixed up Parse Server versions, you would post a topic in the Parse community forum or on StackOverflow. Code-level support is not provided in GitHub issues. |
Related to #6173
Issue Description
RangeError: Invalid WebSocket frame: invalid payload length 126This error occurs intermittently and stops the server when I use livequery.
Steps to reproduce
Expected Results
Parse Server should not terminate by the error.
Actual Outcome
Parse Server is terminated.
Environment Setup
Server
Database
The text was updated successfully, but these errors were encountered: