Debendra Oli
Debendra Oli
Got same problem during deployment. Do you have fix guys, it would be very helpful. @simoncolincap @janrenz @mvakert @wolfm89 ``` unable to recognize "STDIN": no matches for kind "Certificate" in...
Is there anything left to do? I would be happy to help. It would be very useful when this gets merged. Thanks
Is it docker-compose setup ?
Looks like jibri is not configured properly hence not available to jicofo.
I cannot really say without looking the jibri logs.
Those logs are not enough, you need to provide full jibri logs from `/var/logs/jitsi/jibri/log.0.log`. I am not sure about the exact filename but just to give you a gist.
There are no logs to look at. Use github interface to paste your logs.
> WARNING: [30] [hostname=35.223.189.86 id=35.223.189.86] MucClient.lambda$getConnectAndLoginCallable$7#630: Error connecting: org.jivesoftware.smack.SmackException$EndpointConnectionException: The following addresses failed: 'RFC 6120 A/AAAA Endpoint + [/35.223.189.86:5222] (/35.223.189.86:5222)' failed because: java.net.SocketTimeoutException: connect timed out You jibri is not...
Issue is with network port which is failing to reach to the destination. Logs clearly states that. There is no other way around. Try reaching your prosody from your jibri...