Bug 55050 - XMPP network error
Summary: XMPP network error
Status: RESOLVED INVALID
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: 5.6
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-18 12:45 UTC by Matthias Mailänder
Modified: 2013-04-10 16:33 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
meaningless error: "connection reset by peer" (21.13 KB, text/x-log)
2012-09-18 12:45 UTC, Matthias Mailänder
Details

Description Matthias Mailänder 2012-09-18 12:45:50 UTC
Created attachment 67326 [details]
meaningless error: "connection reset by peer"

via https://bugs.kde.org/show_bug.cgi?id=305857

telepathy-gabble 0.16.0
telepathy-mission-control 5.12.0
libtelepathy-glib 0.18.1
libtelepathy-qt4 0.9.3

on KDE Telepathy 0.5 but Empathy 3.4.2.3 shows the same error so I guess it's a telepathy error. Pidgin 2.10.6, Psi 0.14 and qutIM 0.3 work.

This happened on openSUSE 12.2 (and 12.1, too).
Comment 1 Simon McVittie 2012-09-18 13:05:00 UTC
"Connection reset by peer" comes from the operating system (it's the strerror() string for ECONNRESET). It means the server (in this case chat.facebook.com) rejected your attempt to connect to it. There isn't really anything telepathy-gabble can do about that...

The log says

(telepathy-gabble:7232): gabble-DEBUG: _gabble_connection_connect (connection.c:2205): disabling SRV because "server" or "old-ssl" was specified or port was not 5222, will connect to chat.facebook.com

It looks as though your account configuration is forcing the "server" parameter to "chat.facebook.com", which means it won't try a SRV lookup (automatic server detection). Facebook accounts set up via GNOME Online Accounts don't do that, which means Gabble would do the equivalent of this:

% host -t SRV _xmpp-client._tcp.chat.facebook.com
_xmpp-client._tcp.chat.facebook.com has SRV record 5 0 5222 chat.facebook.com.

... resulting in the same connection attempt that it's doing for you anyway (connecting to "chat.facebook.com", TCP port 5222).
Comment 2 Simon McVittie 2012-09-18 13:12:49 UTC
Try doing "telnet chat.facebook.com 5222" in a terminal? That's essentially the same TCP connection that telepathy-gabble is doing.

If you open that connection, type "x" and press Enter, if all goes well you should get something like this:

% telnet chat.facebook.com 5222
Trying 69.171.227.26...
Connected to chat.facebook.com.
Escape character is '^]'.
x
<?xml version="1.0"?><stream:stream id="none" from="chat.facebook.com" version="1.0" xmlns="jabber:client" xmlns:stream="http://etherx.jabber.org/streams"><stream:error><xml-not-well-formed xmlns="urn:ietf:params:xml:ns:xmpp-streams"/></stream:error></stream:stream>Connection closed by foreign host.

If you get "Connection reset by peer" or something else, then your network is probably interfering with the connection to Facebook.
Comment 3 Matthias Mailänder 2012-09-18 13:19:46 UTC
telnet chat.facebook.com 5222
Trying 69.171.241.10...
Connected to chat.facebook.com.
Escape character is '^]'.
x
<?xml version="1.0"?><stream:stream id="none" from="chat.facebook.com" version="1.0" xmlns="jabber:client" xmlns:stream="http://etherx.jabber.org/streams"><stream:error><xml-not-well-formed xmlns="urn:ietf:params:xml:ns:xmpp-streams"/></stream:error></stream:stream>Connection closed by foreign host.
Comment 4 Matthias Mailänder 2013-04-10 16:33:46 UTC
The problem was that KDE-Telepathy fetched proxy settings from an old GNOME installation which had some manual proxy settings set although all GUI programs using/configuring it were already gone for years.

gsettings reset-recursively org.gnome.system.proxy "fixed" it. Sorry.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.