-
-
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
Can't connect from ws client to ws server: TLS handshake failure #1227
Comments
What happens if you try to connect to your const https = require('https');
const request = https.get({
hostname: 'websocket.example.com',
headers: {
upgrade: 'websocket',
connection: 'Upgrade',
'Sec-WebSocket-Key': 'rfeGe1izPRq2JyonWunAQw==',
'Sec-WebSocket-Version': 13
}
});
request.on('error', (err) => console.error(err));
request.on('upgrade', () => console.log('upgraded')); |
Does not work too. Debug output:
Should I open an issue at node repo or do you have an idea? |
Yes, I think it makes sense to open an issue in the node repo. |
I got it working with the
Unfortunately Should it be added to Anyway |
Yes, it should. Do you want to open a PR? |
I will try to implement this. |
Support ecdhCurve option as discussed in #1227.
Support ecdhCurve option as discussed in #1227.
Description
If I try to connect with the attached ws client to the attached ws server I get the following error:
But Chrome and Firefox can connect to the ws server, so the problem must be in the ws client.
Reproducible in:
version: 3.2.0
Node.js version(s): 9.0.0
OS version(s): elementary OS 0.4.1 Loki, based on Ubuntu 16.04.3 LTS
Steps to reproduce:
Expected result:
Connecting to websocket without error.
Actual result:
Not connecting to websocket, producing an error.
Attachments:
Debug output:
Websocket Server:
Websocket client:
The text was updated successfully, but these errors were encountered: