-
Notifications
You must be signed in to change notification settings - Fork 7
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
Websocket Handshake error #26
Comments
I cannot judge that this gem's issue or not from your information. |
Hi unfortunately, we do not own the server and it is difficult to reproduce the issue as it occurs every now and then but it seems our connection refresh handles it. Although, I will see if I can get the error code still from server side. To pivot, I have another question: |
It was not easy for me to figure out how to do this. It might be feasible through inter-process communication, for example. Or you may need to use the websocket gem directly. |
Hi we are using a websocket API and have a thread that will refresh the connection every hour, and also another thread that will process the logs on a interval that is specified in our fluentd config
We integrated this gem into our fluentd plugin, but we are seeing the following handshake error where we notice afterwards it does not process logs as indicated in our container logs (although it does output one record constantly to our file and switches to another record and so and so)
DEBUG -- : --- WSS Error #<WebSocket::Error::Handshake::InvalidStatusCode: WebSocket::Error::Handshake::InvalidStatusCode>
Do you happen to have any insight on this particular error?
The text was updated successfully, but these errors were encountered: