Note that there are some explanatory texts on larger screens.

plurals
  1. POunable to connect to xmpp server using node-xmpp
    primarykey
    data
    text
    <p>Im working on getting node-xmpp working with a jabber server we have in house here. I was able to get it working with talk.google.com just fine, and i can connect to our internal server with adium or ichat just fine.</p> <ul> <li>Node v0.6.14</li> <li>CentOS 6.2 / 2.6.32</li> <li>node-xmpp 0.3.2</li> <li>OpenSSL 1.0.0</li> </ul> <p>connect code</p> <pre><code>var j = new xmpp.Client({ jid : 'user@domain', password : 'pass', host : 'chat.domain' }); </code></pre> <p>After tracing through the code, it seems it gets stuck right after it tries to upgrade the connection to a secure connection. This occurs in <strong>starttls.js</strong> in the <strong>starttls</strong> function.</p> <p>The <strong>pair.on('secure')</strong> event is never called, and even after i print out pair after a settimeout, its still not appearing to be authorized. At this point i dont see any data in or out.</p> <p>After a long time sitting there (several minites) it prints out an error that looks like this</p> <pre><code>throw arguments[1]; // Unhandled 'error' event ^ Error: 139644497663968:error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error:s23_clnt.c:674: at CleartextStream._pusher (tls.js:508:24) at CleartextStream._push (tls.js:334:25) at SecurePair.cycle (tls.js:734: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:367:14) </code></pre> <p>The server is using a self signed cert if that matters.</p> <p>Any ideas?</p> <p>Thanks!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload