Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#10095 closed defect (fixed)

Pidgin 2.6.1 and Openfire 3.6.1 (Jabber)

Reported by: bccocx Owned by: deryni
Milestone: Component: XMPP
Version: 2.6.1 Keywords: Openfire, Jabber, XMPP
Cc: belly917

Description

The University of Texas at Austin ITS (Information Technology Services) runs Openfire 3.6.1 for workplace communications. The newest version of Pidgin, 3.6.1, will not connect to the jabber server. I could not find anything in the Openfire logs about the connection failing. Pidgin never gives an error message....it just never connects....

Thanks!

Change History (7)

comment:1 Changed 10 years ago by maxim0512

I am experiencing a similar problem connecting to a jabberd2 server over SSL in my organization with Pidgin 2.6.1. I was previously using 2.5.x without incident. As the OP stated, I just get a continuous "Connecting..." message, no error.

comment:2 Changed 10 years ago by Ulysse3

I have exactly the same problem in my orgainization, but I don't the server they use. But I have no problem with other Jabber clients ... I am also experiencing some random crashes when trying to modify the config to try to make it work. It is not precised, but I use the Windows client.

comment:3 Changed 10 years ago by belly917

I am also experiencing this issue. Pidgin 2.6.1 on windows, Openfire 3.6.4 on Mac server.

comment:4 Changed 10 years ago by bccocx

  • Resolution set to fixed
  • Status changed from new to closed

Close pidgin

http://pidgin.im/~nosnilmot/2.6.1/srvfix/libpurple.dll <Copy this DLL into the Pidgin directory (C:\Program Files\Pidgin)

Now you can open Pidgin and get connected to Jabber.

comment:5 follow-up: Changed 10 years ago by Ulysse3

It seems better, but I have a new problem. I have an error saying the certificate of my server is not valid (actually expired):

(18:06:36) dnssrv: Couldn't look up SRV record. Le nom DNS n'existe pas. (9003).
(18:06:36) certificate/x509/tls_cached: Certificate ''<my_server>'' expired at Fri Mar 27 11:11:51 2009
(18:06:36) certificate: Failed to verify certificate for ''<my_server>''
(18:06:36) jabber: XML parser error for JabberStream 0216A008: Domain 1, code 5, level 3: Extra content at the end of the document

Is it normal that Pidgin is so restrictive (again, no problem with other clients)?

comment:6 Changed 10 years ago by maxim0512

The replacement .dll provided by bccocx solved the problem for me.

comment:7 in reply to: ↑ 5 Changed 10 years ago by darkrain42

Replying to Ulysse3:

It seems better, but I have a new problem. I have an error saying the certificate of my server is not valid (actually expired):

(18:06:36) dnssrv: Couldn't look up SRV record. Le nom DNS n'existe pas. (9003).
(18:06:36) certificate/x509/tls_cached: Certificate ''<my_server>'' expired at Fri Mar 27 11:11:51 2009
(18:06:36) certificate: Failed to verify certificate for ''<my_server>''
(18:06:36) jabber: XML parser error for JabberStream 0216A008: Domain 1, code 5, level 3: Extra content at the end of the document

Is it normal that Pidgin is so restrictive (again, no problem with other clients)?

This was new in 2.6.1 and will be fixed in 2.6.2, though I strongly recommend you convince the server operator to fix the server's certificate. Pidgin 2.6.2 will warn you during every connection that the SSL certificate is expired.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!