- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
ERROR Invalid WebSocket frame: invalid status code 22373 #1922
Comments
Duplicate of #1916? |
@lpinca yes, the same problem. I didn't see that issue as it was closed. Not sure where the status code is coming from, but whatever the case, I'd assume it shouldn't be crashing our entire ingest server? Also, I can't figure out how to catch this error. I tried what you suggested in that post and it doesn't seem to work. I am using a bit of async/await but have a pretty typical |
Did you see #1916 (comment)? That example triggers the error and the server does not crash. Make sure you have a listener for |
Are you removing the |
@lpinca thanks for the follow up, i followed your guide and redeployed last night. It might be working actually, no crashes over night. Getting errors caught like this one (is that the same issue?) |
Yes. That is not the same error but it is still caused by an invalid frame. |
FWIW, we've noticed Safari on iOS 15 beta ( |
Hi everyone, I've been able to replicate this issue specifically when using the It sounds like maybe this a bug in Safari then? |
Any input in this? The error listener was always there for years, it caught a lot of errors, but this specific |
@goktugyil see #1916 (comment). You can open a connection and send that frame to reproduce. It is like any other "invalid frame" error. |
RangeError: Invalid WebSocket frame: invalid status code 60015 crashing on this, any ideas ? |
@dhillon-lovey3110 Did you solve it? I am now stuck with the error of "60015" |
I have the same problem :( |
I solved this when I was having this problem with Angular 15, Node 18, Webpack Dev Server 4.11.1. Match the URL for WebSocket to the proxy configuration file. DO NOT USE use the top level
Below config which didn't work with Angular 15, Webpack Dev Server 4.11.1, but did work in my prior Angular 12, Webpack Dev Server 3.11.3 configuration. It was failing in upgrade and I had no idea why until I beat my head against the wall, the desk, the keyboard, ... and somehow tripped upon the above configuration.
Finally, in my shell I ran For Angular 15:
For Angular 12:
Incidentally, I found similar issues on GitHub http-proxy-middleware #476 and angular-cli #23155 when searching for this error code. Perhaps, this also helps in those. |
issue.
Description
This appears to be a new issue that is creeping up due to a change somewhere. There are only a few mentions of this code
22373
across the internet but it's been in the last month or so. To me this suggests are recent changes somewhere related to websockets.The error is
ERROR Invalid WebSocket frame: invalid status code 22373
This error has been completely crashing our analytics server whenever it occurs. Would suggest that WS has a way to catch errors like this as we are likely having data loss because of it.
Reproducible in:
Steps to reproduce:
The text was updated successfully, but these errors were encountered: