Skip to content
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

Open
esalvi opened this issue May 2, 2024 · 4 comments

Comments

@esalvi
Copy link

esalvi commented May 2, 2024

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.

@TTLiveStream
Copy link

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.

@TTLiveStream
Copy link

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.

They just updated it with a possible fix. Give the 1.1.6 a try.

@zerodytrash
Copy link
Owner

Hi, please update to 1.1.6. Let me know the results.

@esalvi
Copy link
Author

esalvi commented May 3, 2024

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... :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants