No response received within reply timeout - While waiting for establishing TLS

I’m using the quick-install version on my Debian Buster server.

When I change something in the config file: /etc/jitsi/meet/www.mydomain.de-config.js and initiate a restart of services to take effect:

service jicofo restart
service jitsi-videobridge2 restart
service prosody restart
service nginx restart

I get this error message in jvb.log:

2020-04-09 15:04:51.539 WARNUNG: [34] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$7#643: [MucClient id=shard hostname=localhost] error connecting org.jivesoftware.smack.SmackException$NoResponseException: No response received within reply timeout. Timeout was 5000ms (~5s). While waiting for establishing TLS at org.jivesoftware.smack.SmackException$NoResponseException.newWith(SmackException.java:93) at org.jivesoftware.smack.SynchronizationPoint.checkForResponse(SynchronizationPoint.java:272) at org.jivesoftware.smack.SynchronizationPoint.checkIfSuccessOrWait(SynchronizationPoint.java:157) at org.jivesoftware.smack.SynchronizationPoint.checkIfSuccessOrWaitOrThrow(SynchronizationPoint.java:128) at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectInternal(XMPPTCPConnection.java:908) at org.jivesoftware.smack.AbstractXMPPConnection.connect(AbstractXMPPConnection.java:383) at org.jitsi.xmpp.mucclient.MucClient.lambda$getConnectAndLoginCallable$7(MucClient.java:638) at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:193) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834) 2020-04-09 15:04:56.490 WARNUNG: [36] org.jivesoftware.smackx.ping.PingManager.pingServerIfNecessary: XMPPConnection was not authenticated

JVB stops working. Even after a restart. What helps: update-ca-certificates -f

Everything starts working as expected. Any ideas?

[damencho]

You may have another error before that which is the source of the problem XMPPConnection was not authenticated. There is a known installation problem with Debian 10, which is now fixed in debian unstable packages (which will soon go into stable). The problem was with re-order of the install sequence (asking for jvb password where it shouldn’t) and having wrong jvb password in sip-communicator.properties and in prosody.

[Mebus]

You may have another error before that which is the source of the problem XMPPConnection was not authenticated. There is a known installation problem with Debian 10, which is now fixed in debian unstable packages (which will soon go into stable). The problem was with re-order of the install sequence (asking for jvb password where it shouldn’t) and having wrong jvb password in sip-communicator.properties and in prosody.

The current unstable update (2.0.4456-1) fixed this strange issue for me. Thanks! 😊