GNOME Bugzilla – Bug 629209
Jabber Connection fails when using Override Server Settings and Certificate
Last modified: 2010-09-10 12:31:18 UTC
The scenarios are as follows: Jabber Account. The server uses a certificate, Encryption required. servername is: jabber.rwth-aachen.de Scenario 1: When using username@servername.net as Login ID and nothing for "Override server settings the error message is: "Disconnected - Network error" Scenario 2: Login ID is username without @servername.net. Instead the same server is set under "Override server settings" When trying to connect the error message is "Disconnected - Certificate hostname mismatch". Dirty Solution: Put both username@servername.net and put the same server for "Override server settings". Problem: Most normal users will give up before finding out this. It is really annoying. At least Scenario 1 should work as it is meant to be the default option without using advanced settings. Empathy should be able to connect the Login ID and Override server settings to a valid Jabber ID. All scenarios should work and give no error message as it most convenient.
Some work have been done recently to improve certificate checking. Could you try with Empathy 2.31.91 and telepathy-gabble 0.9.17 please?
I am actually running 2.31.91.1 on Ubuntu 10.10 beta.
Ah interesting. Could you please attach gabble logs when trying to connect with Scenario 1? You can grab them from the help - debug menu.
Created attachment 169928 [details] gabble log scenario 1
Created attachment 169929 [details] mission control log scenario 1
(In reply to comment #4) > Created an attachment (id=169928) [details] > gabble log scenario 1 Sorry the gabble log is the wrong one. I just found out that facebook is also using jabber. But I have problems with the other Jabber account.
Created attachment 169930 [details] gabble log scenario 1 this should be the correct one
Created attachment 169931 [details] gabble log scenario 2
_xmpp._tcp.jabber.rwth-aachen.de is a CNAME while it should be a SRV record. The server is probably miss-configured but gabble should do a better job and be able to connect anyway. The good news is, gabble master does as https://bugs.freedesktop.org/show_bug.cgi?id=28051 has been fixed. Closing the bug for now. Feel free to re-open if you still have this issue with the future release of gabble.
(In reply to comment #0) > Scenario 2: > Login ID is username without @servername.net. Instead the same server is set > under "Override server settings" You shouldn't be able to do that. I opened bug #629261 about this issue.