#509 closed defect (duplicate)

TLS connectivity issue

Reported by: i.galic@… Owned by: wilmer
Priority: normal Milestone:
Component: Jabber Version: 1.2.3
Keywords: Cc:
IRC client+version: Client-independent Operating System: Public server
OS version/distro:


I'm experiencing trouble connecting via BitlBee to an XMPP service provided by a Zimbra Server:

jabber( - Logging in: Connecting
jabber( - Logging in: Connected to server, logging in
jabber( - Logging in: Converting stream to TLS
jabber( - Logging in: Connected to server, logging in
jabber( - Couldn't log in: XML stream error
jabber( - Logging in: Signing off..
jabber( - Logging in: Reconnecting in 900 seconds..

I have enabled xmlconsole:

TX: <?xml version='1.0' ?><stream:stream to="" xmlns="jabber:client" xmlns:stream="" 
RX: <stream:features><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"></starttls><mechanisms 
TX: <starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>
RX: <proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>
TX: <?xml version='1.0' ?><stream:stream to="" xmlns="jabber:client" xmlns:stream="" 
TX: </stream:stream>

At first I thought this was related to #437, but it seems not to be, as I'm not even able to login.

wilmer has looked into this on IRC, and asked me to open this ticket. To repro:

auto_connect = `true'
auto_reconnect = `true'
password is empty
username = `'
port = `5222'
priority = `0'
resource = `BitlBee'
resource_select = `priority'
server = `'
ssl = `false'
tls = `try'
xmlconsole = `true'

Attachments (0)

Change History (3)

comment:1 Changed at 2009-10-18T00:55:29Z by i.galic@…

I wanted to add, that it does work with the following settings:

02:52 <@root> auto_connect = `1'
02:52 <@root> auto_reconnect = `true'
02:52 <@root> password is empty
02:52 <@root> username = `'
02:52 <@root> port = `5223'
02:52 <@root> priority = `0'
02:52 <@root> resource = `BitlBee'
02:52 <@root> resource_select = `priority'
02:52 <@root> server = `'
02:52 <@root> ssl = `true'
02:52 <@root> tls = `try'
02:52 <@root> xmlconsole = `false'

comment:2 Changed at 2009-11-11T15:38:30Z by anonymous

I had the same problem. TLS worked fine with other clients, had to use SSL for bitlbee though.

comment:3 Changed at 2010-03-14T17:00:12Z by wilmer

Resolution: duplicate
Status: newclosed

Sorry for taking so long. In the end someone else came to #bitlbee with the same problem and I root-caused it (#547). The fix is now checked in, changeset:devel,504. Sorry for taking so long with the actual fix. :-(

Modify Ticket

as closed The owner will remain wilmer.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.