-
-
Notifications
You must be signed in to change notification settings - Fork 252
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 connection failed, Error: Server responded with a non-101 status: 200 OK... #184
Comments
This has been driving me crazy all night. We didn't change anything on our end. The discord mentioned the signing signature had an issue but they said it was resolved. Unfortunately we are still getting the "illegal secret key" as well still. |
They just updated it with a possible fix. Give the 1.1.6 a try. |
Hi, please update to 1.1.6. Let me know the results. |
Thank you so much! I've just updated to 1.1.6 and it works much better but it's still happening from time to time... :( |
Hello.
From yesterday, I'm getting the following error: "Websocket connection failed, Error: Server responded with a non-101 status: 200 OK Response Headers Follow:content-length: 0 handshake-msg: illegal secret keyhandshake-status: 417tt_stable..."
v1.1.5
Any idea?
Best regards.
The text was updated successfully, but these errors were encountered: