Cannot connect to local Jabber server (Wildfire 3.1.1) with Kopete nor Gaim

Bug #94756 reported by lefty.crupps
6
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

I set up our local users with Jabber clients all the time, so I have some idea of what I am doing. But both with Kopete and Gaim I cannot connect to our local Jabber/Wildfire 3.1.1 server.

With Kopete I get the error:
"There was an error authenticating with the server: Login failed with unknown reason."
Gaim gives:
"Couldn't connect to host"

I have Kopete set up and working with Google's GMail chat/Google Talk Jabber service, so that part works fine. Kopete now requires me to use a full email address :( which is not how our system is set up, but even when I change my Wildfire account to take this position, Kopete and Gaim both still fail.

ProblemType: Bug
Architecture: i386
Date: Thu Mar 22 08:48:18 2007
DistroRelease: Ubuntu 7.04
Uname: Linux jthomas-desktop 2.6.20-12-generic #2 SMP Sun Mar 18 03:07:14 UTC 2007 i686 GNU/Linux

Revision history for this message
Johan Walles (walles) wrote :

After upgrading from Edgy to Feisty, I get the attached error message when I try to connect. Since we're running Wildfire 3.1.1 over here as well, this is likely the same issue. We're using encrypted connections to the server.

The Swedish parts of the error message translates to:
"<email address hidden>/Work (Walles) (jabber) was disconnected"
"Not authorized / authenticated"

This bug was reported about two months ago. Any updates since that haven't been documented here?

Revision history for this message
Johan Walles (walles) wrote :

Confirming since I'm having very similar problems with a very similar setup.

Revision history for this message
Johan Walles (walles) wrote :

I don't see anything in the server logs when I run into this. Unlike Lefty I don't know much about how Wildfire works though, so that might be a server configuration issue in my case.

Revision history for this message
Johan Walles (walles) wrote :

Disabling TLS on the server side (but leaving "Old SSL" enabled) worked around this issue here. Good enough for me...

Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

Revision history for this message
Johan Walles (walles) wrote :

Pedro,

I have just read all the comments, and I don't see any unanswered questions.

What information is it that is missing?

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

From the comments above it appears to be a server issue. Wildfire is not provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.