Recording unavailable

jibri log

2020-04-22 00:45:03.979 INFO: [1] org.jitsi.jibri.api.xmpp.XmppApi.start() The trustAllXmppCerts config is enabled for this domain, all XMPP server provided certificates will be accepted
2020-04-22 00:45:04.008 WARNING: [21] org.jitsi.xmpp.mucclient.MucClient.log() Disabling certificate verification!
2020-04-22 00:45:04.076 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime() A provider org.jitsi.jibri.api.http.HttpApi registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.jibri.api.http.HttpApi will be ignored.
2020-04-22 00:45:09.067 WARNING: [21] org.jitsi.xmpp.mucclient.MucClient.log() [MucClient id=XXXXX hostname=XXXXX] 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(
at org.jivesoftware.smack.SynchronizationPoint.checkForResponse(
at org.jivesoftware.smack.SynchronizationPoint.checkIfSuccessOrWait(
at org.jivesoftware.smack.SynchronizationPoint.checkIfSuccessOrWaitOrThrow(
at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectInternal(
at org.jivesoftware.smack.AbstractXMPPConnection.connect(
at org.jitsi.xmpp.mucclient.MucClient.lambda$getConnectAndLoginCallable$7(
at org.jitsi.retry.RetryStrategy$
at java.util.concurrent.Executors$
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(
at java.util.concurrent.ScheduledThreadPoolExecutor$
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$

jitsi & jibri server use java 8

jitsi SSL. is valid from let’s encrypt free ssl

Please help me.

why not have this error same me.
I’m searching 2 day ago.

:cry: :cry: :cry:

I solved this problem.
jibri record working now.
Thank you.


please can you help how you solve this problem

I encountered this problem at the security equipment (IPS).
I tried to check all config many times. But nothing is wrong.
So I asked the administrator to investigate and found the problem.
I request open the policy between jitsi and jibri servers so it works well.

what do you mean by policy , should i asked AWS adminsisterator to open the policy between two servers?

I do not use AWS. I use server in my office.
I recommend check config between jitsi-meet and jibri server.
Jibri server will try to connect jitsi with port 5222.
May be disable ufw.