Modify ↓
Opened at 2013-04-02T13:48:42Z
Closed at 2015-10-21T09:39:13Z
#1041 closed defect (moreinfo)
Jabber account connects, hangs after "Authentication Finished"
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | BitlBee | Version: | 3.0.6 |
Keywords: | Cc: | ||
IRC client+version: | Client-independent | Operating System: | Public server |
OS version/distro: |
Description (last modified by )
I've set up this particular server in clients outside of irssi/bitlbee without issue. But for some reason I can't get a connection here.
xmlconsole:
<xmlconsole> TX: <?xml version='1.0' ?><stream:stream to="chat.analytemedia.com" xmlns="jabber:client" xmlns:stream="http://etherx.jabber.org/streams" version="1.0"> <xmlconsole> RX: <stream:features><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"><required/></starttls><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>DIGEST-MD5</mechanism><mechanism>PLAIN</mechanism><mechanism>CRAM-MD5</mechanism></mechanisms></stream:features> <xmlconsole> TX: <starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/> <xmlconsole> RX: <proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"/> <xmlconsole> TX: <stream:stream to="chat.analytemedia.com" xmlns="jabber:client" xmlns:stream="http://etherx.jabber.org/streams" version="1.0"> <xmlconsole> RX: <stream:features><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>DIGEST-MD5</mechanism><mechanism>PLAIN</mechanism><mechanism>CRAM-MD5</mechanism></mechanisms><compression xmlns="http://jabber.org/features/compress"><method>zlib</method></compression><auth xmlns="http://jabber.org/features/iq-auth"/></stream:features> <xmlconsole> TX: <auth xmlns="urn:ietf:params:xml:ns:xmpp-sasl" mechanism="DIGEST-MD5"/> <xmlconsole> RX: <challenge xmlns="urn:ietf:params:xml:ns:xmpp-sasl">cmVhbG09ImNoYXQuYW5hbHl0ZW1lZGlhLmNvbSIsbm9uY2U9ImduQTJZVjVkVG5yZ2N0a1FLeXEyRm9NbGVIeUo4cXNkdHppUEt3Z3YiLHFvcD0iYXV0aCIsY2hhcnNldD11dGYtOCxhbGdvcml0aG09bWQ1LXNlc3M=</challenge> <xmlconsole> TX: <response xmlns="urn:ietf:params:xml:ns:xmpp-sasl">dXNlcm5hbWU9ImRhbm55LnBlY2siLHJlYWxtPSJjaGF0LmFuYWx5dGVtZWRpYS5jb20iLG5vbmNlPSJnbkEyWVY1ZFRucmdjdGtRS3lxMkZvTWxlSHlKOHFzZHR6aVBLd2d2Iixjbm9uY2U9IlZBdllvNURHeFg4amNaSjRWVUpNNXJPV3h5SmlNNmtkR094WmdKR1oiLG5jPTAwMDAwMDAxLHFvcD1hdXRoLGRpZ2VzdC11cmk9InhtcHAvY2hhdC5hbmFseXRlbWVkaWEuY29tIixyZXNwb25zZT0xYjAyNGVkMDYxNTk4ZjZlZTJkMjcxZTZiZGU2YmE0YixjaGFyc2V0PXV0Zi04</response> <xmlconsole> RX: <success xmlns="urn:ietf:params:xml:ns:xmpp-sasl">cnNwYXV0aD1hZGVjMjkyNWI2NDg4YzllMmFlMWI4YmNhZTExMTM4Nw==</success> <xmlconsole> TX: <stream:stream to="chat.analytemedia.com" xmlns="jabber:client" xmlns:stream="http://etherx.jabber.org/streams" version="1.0">
Connection settings:
<@root> auto_connect = `true' <@root> auto_reconnect = `true' <@root> nick_format is empty <@root> nick_source = `handle' <@root> password = `********' (hidden) <@root> tag = `jabber2' <@root> username = `first.last@chat.server.com' <@root> activity_timeout = `600' <@root> oauth = `false' <@root> port = `5222' <@root> priority = `0' <@root> proxy = `proxy.eu.jabber.org;5222' <@root> resource = `BitlBee' <@root> resource_select = `activity' <@root> server = `chat.server.com' <@root> ssl = `false' <@root> tls = `true' <@root> tls_verify = `true' <@root> user_agent = `analyte' <@root> xmlconsole = `true' <@root> away is empty <@root> status is empty
Attachments (0)
Change History (3)
comment:1 Changed at 2013-05-25T11:00:03Z by
comment:2 Changed at 2014-07-14T18:07:44Z by
Description: | modified (diff) |
---|
Adding code blocks to description
Also this one sounds vaguely familiar
comment:3 Changed at 2015-10-21T09:39:13Z by
Resolution: | → moreinfo |
---|---|
Status: | new → closed |
Can't do anything with this one without more info. This one didn't get a reply to a comment a few weeks after it was opened, I wouldn't expect one now. But who knows! Reopen if it still happens.
Note: See
TracTickets for help on using
tickets.
Is this with OpenSSL? Does 3.2 have the same problem?