Re: Loqui IM doesn’t work with the XEP-198 by jabberd2
On Tue, May 26, 2015 at 06:08:20PM +0200, Matěj Cepl wrote: > (a follow-up to the issue > https://github.com/loqui/im/issues/732#issuecomment-105519240) BTW, I believe this is actually the same as discussed here some time ago http://thread.gmane.org/gmane.network.jabber.jabberd2/1454/focus=1458 Christof -- http://cmeerw.org sip:cmeerw at cmeerw.org mailto:cmeerw at cmeerw.org xmpp:cmeerw at cmeerw.org
Re: Loqui IM doesn’t work with the XEP-198 by jabberd2
On 5/26/15, 9:08 AM, "Matěj Cepl" wrote: >(a follow-up to the issue >https://github.com/loqui/im/issues/732#issuecomment-105519240) > >I have a jabberd2 XMPP server on domain ceplovi.cz and I would >like to connect to it with Loqui. It works perfectly well with >pidgin, bitlbee, empathy, displays well on IM Observatory, but >Loqui just ALWAYS ends with “Authentication failed” (it is not >a temporary failure). The strange thing is that jabberd2 logs on >the server don’t show any activity when I try to login. The "Authentication Failed” message is likely a standard canned response from Loqui when they can’t establish a connection with your jabberd2 server. >Loqui IM people do think that it is because of discrepancy >between the implementation of XEP-198 by jabberd2 and (they say) >more recent version of it expected by Loqui IM. Are you able to rebuild jabberd2 from source? Enabling the debug option and obtaining the detailed output can lead to better information about the exact cause of the failure. Once rebuilt, you can specify the file to send the debug output to in the component config files. I would enable debug on router, c2s and sm just in case. Streams codebase hasn’t changed in a while AFAIK. For more info: https://github.com/jabberd2/jabberd2/wiki/InstallGuide-Troubleshooting
Loqui IM doesn’t work with the XEP-198 by jabberd2
Hi, (a follow-up to the issue https://github.com/loqui/im/issues/732#issuecomment-105519240) I have a jabberd2 XMPP server on domain ceplovi.cz and I would like to connect to it with Loqui. It works perfectly well with pidgin, bitlbee, empathy, displays well on IM Observatory, but Loqui just ALWAYS ends with “Authentication failed” (it is not a temporary failure). The strange thing is that jabberd2 logs on the server don’t show any activity when I try to login. Loqui IM people do think that it is because of discrepancy between the implementation of XEP-198 by jabberd2 and (they say) more recent version of it expected by Loqui IM. Does anybody here understand what’s the problem? Would it be possible somehow to make jabberd2 compatible with Loqui? Best, Matěj -- http://www.ceplovi.cz/matej/, Jabber: mceplceplovi.cz GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC Finally, brethren, whatsoever things are true, whatsoever things are honest, whatsoever things are just, whatsoever things are pure, whatsoever things are lovely, whatsoever things are of good report; if there be any virtue, and if there be any praise, think on these things. -- Philipians 4:8 KJV