Discord.js: Error: RSV2 and RSV3 must be clear

Created on 9 Aug 2017 · 13Comments · Source: discordjs/discord.js

Please describe the problem you are having in as much detail as possible:
I don't exactly know how to explain it, but I also have no example code, because I don't know what is going on. It just started happening as soon as I tried to use disabledEvents on the client constructor, but it threw this error. I removed it and it's still giving me the same error. I moved the bot to my VPS and same error. It doesn't seem to be a port issue, because this is the only bot running. Anyone else having this error?

Include a reproducible code sample here, if possible:

Further details:

discord.js version: 12.0.0
node.js version: 8.2.1
Operating system: Debian 8.4
Priority this issue should have – please be realistic and elaborate if possible: Extremely High

[ ] I found this issue while running code on a __user account__
[x] I have also tested the issue on latest master, commit hash: 54ff8ce

dependencies gateway bug

Source

PassTheMayo

Most helpful comment

@devsnek I just did npm install uws, and restarted the bot. It was successful at login and did everything correctly.

PassTheMayo on 9 Aug 2017

👍2

All 13 comments

weeee we aren't sure how to fix this either. we believe it to be an upstream bug with ws, but we aren't sure. please try reproducing with uws and with/without bufferutil installed.

devsnek on 9 Aug 2017

@devsnek That seemed to fix the issue, thanks!

PassTheMayo on 9 Aug 2017

@PassTheMayo can you be specific on what fixed the issue, we aren't sure here how to fix it

devsnek on 9 Aug 2017

@devsnek I just did npm install uws, and restarted the bot. It was successful at login and did everything correctly.

PassTheMayo on 9 Aug 2017

👍2

Hmm thanks! I was having this issue too but was just ignoring it.

ShayBox on 9 Aug 2017

https://tools.ietf.org/html/rfc6455#section-5.2

https://github.com/websockets/ws/issues/1140#issuecomment-308016758

jaipradeesh on 1 Mar 2018

@jaipradeesh That explains nothing. Plus we already got this resolved anyways, thanks.

PassTheMayo on 1 Mar 2018

   RSV1, RSV2, RSV3:  1 bit each

      MUST be 0 unless an extension is negotiated that defines meanings
      for non-zero values.  If a nonzero value is received and none of
      the negotiated extensions defines the meaning of such a nonzero
      value, the receiving endpoint MUST _Fail the WebSocket
      Connection_.

This error means that the client is sending a compressed frame but the permessage-deflate extension is disabled.

jaipradeesh on 1 Mar 2018

👍1

@jaipradeesh - Your saying this, but I'm unsure what you mean.

This error means that the client is sending a compressed frame but the permessage-deflate extension is disabled.

I've got a self made bot, which connects to a remote API, and I just got an error saying Error: RSV2 and RSV3 must be clear as well. I'm using the regular node ws lib for the websocket, so I'm not sure how I as a client am wrong in sending a compressed frame.

Have you got any tips on debugging this?

kramer65 on 7 Aug 2018

I'm still getting this error, and when its a fatal one so my script crashes

lukeeey on 2 Sep 2018

@kramer65 @lukeeey As PassTheMayo did, just install uws and it should work.

advaith1 on 5 Sep 2018

Don't you think I did that

lukeeey on 5 Sep 2018

👎3

I'm getting this when I stream data from an arduino IoT nano, it streams for about a few seconds, data is good, then it hits this error. Since it sends good data prior to this error, I don't believe the error message is accurate, otherwise the error message would show up in the first message(s). It's a bit of a showstopper, cannot seem to stream websocket data using ws and uws is not a realistic option due to it's various issues.