search

xmppo / node-xmpp-bosh

An XMPP BOSH & WebSocket server (connection manager) written on node.js using Javascript
https://github.com/xmppo/node-xmpp-bosh
263 stars 85 forks source link

Can't connect to jabberd2 server #86

Open bluszcz opened 11 years ago

bluszcz commented 11 years ago 
[2013-07-22 12:50:38.829] [DEBUG] [http-  server.js:_unwrapped_on_end_callback:137] - RECD: <body rid="1362917403094589" sid="625b3186-fd36-4e05-b712-dd4064834e9e" to="jabberpl.org" xml:lang="en" xmlns="http://jabber.org/protocol/httpbind" xmlns:xmpp="urn:xmpp:xbosh"/>
[2013-07-22 12:50:38.830] [INFO] [session.js:Object.Session.send_invalid_packet_terminate_response:581] - 625b3186-fd36-4e05-b712-dd4064834e9e send_invalid_packet_terminate_response -- will terminate
[2013-07-22 12:50:38.830] [DEBUG] [xmpp-proxy-connector.js:Object.XMPPProxyConnector.stream_terminate:205] - 625b3186-fd36-4e05-b712-dd4064834e9e 054dd0c8-4366-4097-ba85-a04d1f638ce5 stream_terminate
[2013-07-22 12:50:38.831] [DEBUG] [xmpp-proxy.js:XMPPProxy.dutil.copy.terminate:236] - 625b3186-fd36-4e05-b712-dd4064834e9e 054dd0c8-4366-4097-ba85-a04d1f638ce5 - terminating
[2013-07-22 12:50:38.832] [DEBUG] [session.js:Object.Session.send_terminate_response:606] - 625b3186-fd36-4e05-b712-dd4064834e9e send_terminate_response - ro: false, condition: item-not-found
[2013-07-22 12:50:38.835] [DEBUG] [response.js:Object.Response.send_response:87] - 625b3186-fd36-4e05-b712-dd4064834e9e SENT(null): <body xmlns="http://jabber.org/protocol/httpbind" condition="item-not-found" message="Invalid packet" type="terminate"/>
bluszcz commented 11 years ago

As a client I am using Pidgin with pidgin compatible = true.

bluszcz commented 11 years ago

However, authentication works. Its disconnected later.

PLAIN authentication succeeded: XXXX@jabberpl.org 188.40.54.140:46347 TLS

bluszcz commented 11 years ago

I have made another tests replacing the node solution with punjab - it works. So there must be a bug here, or misconfiguration problem, at least.

dhruvbird commented 11 years ago

I'm seeing a different error. For some reason, the jabber server isn't recognizing the starttls request. In fact, from what I see, the response is sent even before the starttls request reached the jabber server.

http://pastebin.com/uBdukt52

[2013-09-24 16:18:26.428] [TRACE] [xmpp-proxy.js:XMPPProxy.dutil.copy._on_stanza:167] - e76605ee-824e-48e5-a428-53f9cc80c731 fa93c7c6-fcc9-42e6-bcdc-2fc9c3a1f179 _on_stanza parsed: <stream:features xmlns:stream="http://etherx.jabber.org/streams"><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"><required/></starttls><address xmlns="http://affinix.com/jabber/address">166.137.178.207</address><auth xmlns="http://jabber.org/features/iq-... [83 more characters]

[2013-09-24 16:18:26.428] [TRACE] [xmpp-proxy.js:XMPPProxy.dutil.copy._on_stanza:190] - e76605ee-824e-48e5-a428-53f9cc80c731 fa93c7c6-fcc9-42e6-bcdc-2fc9c3a1f179 STARTTLS requested

[2013-09-24 16:18:26.429] [TRACE] [xmpp-proxy.js:XMPPProxy.dutil.copy._on_stanza:195] - e76605ee-824e-48e5-a428-53f9cc80c731 fa93c7c6-fcc9-42e6-bcdc-2fc9c3a1f179 Writing out STARTTLS

[2013-09-24 16:18:26.429] [TRACE] [xmpp-proxy.js:XMPPProxy.dutil.copy.send:264] - e76605ee-824e-48e5-a428-53f9cc80c731 fa93c7c6-fcc9-42e6-bcdc-2fc9c3a1f179 Sent: <starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>

[2013-09-24 16:18:26.430] [TRACE] [xmpp-proxy.js:XMPPProxy.dutil.copy._on_stanza:167] - e76605ee-824e-48e5-a428-53f9cc80c731 fa93c7c6-fcc9-42e6-bcdc-2fc9c3a1f179 _on_stanza parsed: <stream:error xmlns:stream="http://etherx.jabber.org/streams"><policy-violation xmlns="urn:ietf:params:xml:ns:xmpp-streams"/><text xmlns="urn:ietf:params:xml:ns:xmpp-streams">STARTTLS is required for this stream</text></stream:error>

[2013-09-24 16:18:26.431] [TRACE] [xmpp-proxy-connector.js:Object.<anonymous>:86] - e76605ee-824e-48e5-a428-53f9cc80c731 fa93c7c6-fcc9-42e6-bcdc-2fc9c3a1f179 _on_stanza_received