On Wednesday, May 29, 2013 10:14:56 AM UTC-7, Ben Noordhuis wrote: > > On Wed, May 29, 2013 at 6:53 PM, dhruvbird <[email protected]<javascript:>> > wrote: > > Hello, > > > > I'm seeing intermittent SSL errors with this exception being thrown: > > > > events.js:48 > > throw arguments[1]; // Unhandled 'error' event > > ^ > > Error: 3072407248:error:14077438:SSL > routines:SSL23_GET_SERVER_HELLO:tlsv1 > > alert internal error:s23_clnt.c:741: > > > > at CleartextStream._puller (tls.js:501:24) > > at CleartextStream._pull (tls.js:432:19) > > at SecurePair.cycle (tls.js:727:20) > > at EncryptedStream.write (tls.js:130:13) > > at Socket.ondata (stream.js:38:26) > > at Socket.emit (events.js:67:17) > > at TCP.onread (net.js:372:14) > > > > > > Very few other people seem to be seeing it though. > > > https://www.google.com/search?q=node.js%20_GET_SERVER_HELLO%3Atlsv1%20alert%20internal%20error%3As23_clnt.c%3A741 > > > > > Using nodejs v0.6.21. Is this something that's been fixed in later > versions? > > Link to reported issue: > > https://github.com/dhruvbird/node-xmpp-bosh/issues/76 > > > > The reason that the OP is unable to use latest nodejs version is that > ::: > > (ipv6 style 0.0.0.0) doesn't seem to be working for him, when that > address > > is specified as the address to listen on (on the 0.10.x branch). > > That's because it's '::' (two colons), ':::' means the 'any' address > followed by a port number. >
You're right. My bad. Here's the original post. https://github.com/dhruvbird/node-xmpp-bosh/issues/75 > As to the TLS error, at the very least v0.10 should give you a more > descriptive error message. > Will try to repro. if listening on :: works out. According to the issue above, the http server just froze. > > If it's a server, it's possible you're not setting the certificate and > key properly. Before v0.10 that was allowed but you then ended up > with a server that couldn't accept connections. > The TLS connection is a client connection. So, I'm using this file https://github.com/dhruvbird/node-xmpp-bosh/blob/master/src/starttls.js to upgrade from a normal socket to a secure socket and am afraid that there might be a bug there. I couldn't any "standard library" method to do the same (similar to an HTTP upgrade). I haven't dug into the http client code to see if there are any parts of the std. lib. that do this already. An unsure if this https://github.com/mattcg/starttls/commit/f2b50dc024df212d51bde1d14d1d3faae5d1eb49 will fix the current bug, but will give it a shot as well. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
