-
Notifications
You must be signed in to change notification settings - Fork 11
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 on secure port #5
Comments
Interesting. TBH, it's been a while since I played with this. I'll see if I can find some time tonight to look at this and try it out. |
I actually got it to work. First thing is I was connecting to the secure port but not using a Second thing is I set some of the tls connection options.
|
What were your TLS connection options? I'm running into the same problem: socket hangup even though I'm providing U/P. |
These are the options i set. I didn't do a lot of experimentation to see var options = On Wed, Nov 18, 2015 at 10:25 AM, awmcclain [email protected]
|
insecure connection works fine. Maybe an issue with old ssl versions or certificates on the XEP?
~/node $ node elktest.js
events.js:72
throw er; // Unhandled 'error' event
^
Error: socket hang up
at SecurePair.error (tls.js:1010:23)
at CleartextStream.read as _read
at CleartextStream.Readable.read (_stream_readable.js:340:10)
at EncryptedStream.write as _write
at doWrite (_stream_writable.js:225:10)
at writeOrBuffer (_stream_writable.js:215:5)
at EncryptedStream.Writable.write (_stream_writable.js:182:11)
at write (_stream_readable.js:601:24)
at flow (_stream_readable.js:610:7)
at Socket.pipeOnReadable (_stream_readable.js:642:5)
pi@raspberrypi ~/node $
The text was updated successfully, but these errors were encountered: