[jitsi-dev] Jitsi client only connects to jit.si, but not to jabber.ccc.de and jabbim.com on Debian testing


#1

Dear All,
I have asked my colleague who has same connection issues with Jitsi
client on ArchLinux to send logfiles, I have sent recently now new
logfiles to support@bluejimp.com

we both cannot connect with Jitsi using a jabbim account.

jabbim connects on both systems (Debian and Arch) normally with same
settings using Pidgin, but not with Jitsi.

I have contacted jabbim support, everything normal on their side, they
suggest "maybe bad certificates for Starttls?"
I updated also cacert as indicated here, no change:
http://wiki.cacert.org/FAQ/ImportRootCert#Debian

However, connecting to jit.si account WORKS, but not to jabber.ccc.de

any ideas would be highly appreciated!

I have sent both logs to support@bluejimp.com

it is quite strange, because few updates ago (on both Jitsi and Debian)
everything was going smoothly...

best greetings, MS

arch linux:
Linux SubOrbitalChestnut 4.4.5-1-ARCH #1 SMP PREEMPT Thu Mar 10 07:38:19
CET 2016 x86_64 GNU/Linux

Debian:
Linux debian 4.4.0-1-amd64 #1 SMP Debian 4.4.6-1 (2016-03-17) x86_64
GNU/Linux


#2

I have asked my colleague who has same connection issues with Jitsi
client on ArchLinux to send logfiles, I have sent recently now new
logfiles to support@bluejimp.com

I don't have access to that address.

we both cannot connect with Jitsi using a jabbim account.

jabbim connects on both systems (Debian and Arch) normally with same
settings using Pidgin, but not with Jitsi.

I have contacted jabbim support, everything normal on their side, they
suggest "maybe bad certificates for Starttls?" I updated also cacert as
indicated here, no change:
http://wiki.cacert.org/FAQ/ImportRootCert#Debian

I'd revert that ASAP. The CACert Root CA (at least the one used by jabbim) uses MD5 - which is known to be broken for a long time now.

While Jitsi would still connect to this service (and does on Windows), it would be possibly that the Java configuration on Debian etc. doesn't allow MD5 anymore. But I can't really tell.

However, connecting to jit.si account WORKS, but not to jabber.ccc.de

any ideas would be highly appreciated!

All I can say is that jit.si is not treated differently in Jitsi than any other XMPP service. In fact, jit.si is simply an Openfire instance.

I have sent both logs to support@bluejimp.com

it is quite strange, because few updates ago (on both Jitsi and Debian)
everything was going smoothly...

best greetings, MS

Ingo