-
-
Notifications
You must be signed in to change notification settings - Fork 503
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
Enable to connect ! invalid handshake #1461
Comments
From websockets' perspective, it never receives the first line of a WebSocket request. What is "our client" here? |
the client is |
This rules out a problem with the client. Could you try connecting to a server running locally? If that works, then it means that the problem is at the level of your AWS Network Load Balancer setup (and I suspect that it's there). |
Thank you for the response. It is working well when connecting with WS (not secured) directly to the IP address. |
If that's your question, one websockets server process cannot serve secure (wss://) and insecure (ws://) connections. I don't plan to add this feature either. There's two ways to handle secure connections:
|
Thank you. We moved the entire project to nodejs. Shame |
I'm sorry it didn't work for you 🥲 |
Hello. Thank you in advance for reading.
I have tested it with a small NodeJS WS service, and our client can open the connection.
When switching to
python-websockets,
I get an error.We are connecting to the WebSocket using AWS Network Load Balancer. (same load balancer working with node)
We are stuck on this for two weeks.
We are experiencing this error.
Thank you
The text was updated successfully, but these errors were encountered: