[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

Dmitry bugzilla_noreply at kde.org
Thu Feb 16 08:00:20 GMT 2017


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

--- Comment #29 from Dmitry <dmitry.a.kuzmenko at gmail.com> ---
This is what I see now in the server log when I'm trying to connect to
ejabberd:

2017-02-16 10:55:13.743 [info] <0.961.0>@ejabberd_listener:accept:333
(#Port<0.85220>) Accepted connection <client_ip>:45668 -> <server_ip>:5222
2017-02-16 10:55:13.828 [info]
<0.13203.19>@ejabberd_c2s:wait_for_feature_request:723
({socket_state,fast_tls,{tlssock,#Port<0.85220>,#Port<0.85221>},<0.13202.19>})
Failed authentication for <user>@<domain> from <client_ip>: Invalid token

I've tried to remove and configure the jabber connection again, tried with and
without "require ssl" option.
Both ends are running ArchLinux, efabberd 17.01, kde telepathy 16.12.2.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Kde-telepathy-bugs mailing list