Recording Failed to Start

Hello,

We’ve successfully been able to use Jitsi to meet with multiple participants, adding recording has been unsuccessful. Your help is greatly appreciated. I’ve read a great deal of the posts related to this topic - none have helped much.

Jitsi-meet installed on Ubuntu 18.04. Worked with 4+ participants - without any problems

Installed Jibri on Ubuntu 16.04 - https://github.com/jitsi/jibri
jibri/stable,now 8.0-14-g0ccc3f6-1 all [installed]

jitsi/stable 2.10.5550-1 amd64 on both servers

Both servers running Java 1.8

Click “Start Recording”, immediately am told “Recording Failed to Start”

Both servers have required open ports. Jitsi is in DNS, Jibri is not. I can see that Jibri is successfully connecting, but Jitsi (prosody) doesn’t seem to be delgating to Jibri

JS console:

Jicofo log says:
Jicofo 2020-04-16 19:26:48.201 INFO: [27] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Member recordingsix@conference.theater-staging.lifetales.com/7e63aedd is leaving

Jicofo 2020-04-16 19:26:48.201 WARNING: [27] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Participant not found for recordingsix@conference.theater-staging.lifetales.com/7e63aedd terminated already or never started ?

Jicofo 2020-04-16 19:26:48.206 INFO: [27] org.jitsi.jicofo.FocusManager.log() Disposed conference for room: recordingsix@conference.theater-staging.lifetales.com conference count: 0

Jicofo 2020-04-16 19:26:55.031 INFO: [84] org.jitsi.jicofo.xmpp.FocusComponent.handleConferenceIq().401 Focus request for room: seven@conference.theater-staging.lifetales.com

Jicofo 2020-04-16 19:26:55.032 INFO: [84] org.jitsi.jicofo.FocusManager.log() Created new focus for seven@conference.theater-staging.lifetales.com@auth.theater-staging.lifetales.com. Conference count 1,options:

Jicofo 2020-04-16 19:26:55.032 INFO: [84] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Lip-sync enabled in seven@conference.theater-staging.lifetales.com

Jicofo 2020-04-16 19:26:55.032 INFO: [84] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Joining the room: seven@conference.theater-staging.lifetales.com

Jicofo 2020-04-16 19:26:55.185 INFO: [27] org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Chat room event ChatRoomMemberPresenceChangeEvent[type=MemberJoined sourceRoom=org.jitsi.impl.protocol.xmpp.ChatRoomImpl@1351cccf member=ChatMember[seven@conference.theater-staging.lifetales.com/ced5226f, jid: null]@192879207]

Jicofo 2020-04-16 19:26:55.188 INFO: [27] org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Granted owner to seven@conference.theater-staging.lifetales.com/ced5226f

Jicofo 2020-04-16 19:26:55.188 INFO: [27] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Member seven@conference.theater-staging.lifetales.com/ced5226f joined.

Jibri log:
JibriConfig(recordingDirectory=/home/jibri/recordings, singleUseMode=false, enabledStatsD=true, finalizeRecordingScriptPath=/home/jibri/bin/finalize_recording.sh, xmppEnvironments=[XmppEnvironmentConfig(name=staging environment, xmppServerHosts=[34.195.80.169], xmppDomain=theater-staging.lifetales.com, controlLogin=XmppCredentials(domain=auth.theater-staging.lifetales.com, username=jibri, password=dddd), controlMuc=XmppMuc(domain=internal.auth.theater-staging.lifetales.com, roomName=JibriBrewery, nickname=jibri-nickname), sipControlMuc=null, callLogin=XmppCredentials(domain=recorder.theater-staging.lifetales.com, username=recorder, password=dddddd), stripFromRoomDomain=conference., usageTimeoutMins=0, trustAllXmppCerts=true)])

2020-04-16 19:19:50.644 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime() A provider org.jitsi.jibri.api.http.internal.InternalHttpApi 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.internal.InternalHttpApi will be ignored.

2020-04-16 19:19:50.815 INFO: [1] org.jitsi.jibri.api.xmpp.XmppApi.updatePresence() Jibri reports its status is now JibriStatus(busyStatus=IDLE, health=OverallHealth(healthStatus=HEALTHY, details={})), publishing presence to connections

2020-04-16 19:19:50.817 INFO: [1] org.jitsi.xmpp.mucclient.MucClientManager.log() Setting a presence extension: org.jitsi.xmpp.extensions.jibri.JibriStatusPacketExt@771158fb

2020-04-16 19:19:50.821 INFO: [1] org.jitsi.jibri.api.xmpp.XmppApi.start() Connecting to xmpp environment on 34.195.80.169 with config XmppEnvironmentConfig(name=staging environment, xmppServerHosts=[34.195.80.169], xmppDomain=theater-staging.lifetales.com, controlLogin=XmppCredentials(domain=auth.theater-staging.lifetales.com, username=jibri, password=*ddd), controlMuc=XmppMuc(domain=internal.auth.theater-staging.lifetales.com, roomName=JibriBrewery, nickname=jibri-nickname), sipControlMuc=null, callLogin=XmppCredentials(domain=recorder.theater-staging.lifetales.com, username=recorder, password=dddd), stripFromRoomDomain=conference., usageTimeoutMins=0, trustAllXmppCerts=true)

2020-04-16 19:19:50.821 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-16 19:19:50.836 WARNING: [20] org.jitsi.xmpp.mucclient.MucClient.log() Disabling certificate verification!

2020-04-16 19:19:50.865 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-16 19:19:51.052 INFO: [20] org.jitsi.xmpp.mucclient.MucClient.log() [MucClient id=34.195.80.169 hostname=34.195.80.169] connected

2020-04-16 19:19:51.127 INFO: [20] org.jitsi.xmpp.mucclient.MucClient.log() Joined MUC: jibribrewery@internal.auth.theater-staging.lifetales.com

Prosody error log (but research says these are not problems?)

Apr 16 19:19:35 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
Apr 16 19:19:35 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281

Apr 16 19:19:35 speakerstats.theater-staging.lifetales.com:speakerstats_component warn speaker stats will not work with Prosody version 0.10 or less.
Apr 16 19:19:35 portmanager info Activated service ‘c2s’ on [::]:5222, []:5222
Apr 16 19:19:35 portmanager info Activated service ‘legacy_ssl’ on no ports
Apr 16 19:19:35 mod_posix info Prosody is about to detach from the console, disabling further console output
Apr 16 19:19:35 mod_posix info Successfully daemonized to PID 18822
Apr 16 19:19:35 conferenceduration.theater-staging.lifetales.com:conference_duration_component warn conference duration will not work with Prosody version 0.10 or less.
Apr 16 19:19:35 portmanager info Activated service ‘http’ on [::]:5280, [
]:5280
Apr 16 19:19:35 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
Apr 16 19:19:35 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
Apr 16 19:19:35 portmanager info Activated service ‘https’ on no ports
Apr 16 19:19:35 conference.theater-staging.lifetales.com:muc_domain_mapper info Loading mod_muc_domain_mapper for host focus.theater-staging.lifetales.com!
Apr 16 19:19:35 conference.theater-staging.lifetales.com:muc_domain_mapper info Loading mod_muc_domain_mapper for host speakerstats.theater-staging.lifetales.com!
Apr 16 19:19:35 conference.theater-staging.lifetales.com:muc_domain_mapper info Loading mod_muc_domain_mapper for host recorder.theater-staging.lifetales.com!
Apr 16 19:19:35 conference.theater-staging.lifetales.com:muc_domain_mapper info Loading mod_muc_domain_mapper for host internal.auth.theater-staging.lifetales.com!
Apr 16 19:19:35 conference.theater-staging.lifetales.com:muc_domain_mapper info Loading mod_muc_domain_mapper for host localhost!
Apr 16 19:19:35 conference.theater-staging.lifetales.com:muc_domain_mapper info Loading mod_muc_domain_mapper for host conferenceduration.theater-staging.lifetales.com!
Apr 16 19:19:35 conference.theater-staging.lifetales.com:muc_domain_mapper info Loading mod_muc_domain_mapper for host theater-staging.lifetales.com!
Apr 16 19:19:35 conference.theater-staging.lifetales.com:muc_domain_mapper info Loading mod_muc_domain_mapper for host auth.theater-staging.lifetales.com!
Apr 16 19:19:35 conference.theater-staging.lifetales.com:muc_domain_mapper info Loading mod_muc_domain_mapper for host conference.theater-staging.lifetales.com!
Apr 16 19:19:40 conference.theater-staging.lifetales.com:muc_domain_mapper warn Session filters applied
Apr 16 19:19:40 c2s5616e9129e10 info Client connected
Apr 16 19:19:41 c2s5616e9129e10 info Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
Apr 16 19:19:41 c2s5616e9129e10 info Authenticated as focus@auth.theater-staging.lifetales.com
Apr 16 19:19:41 focus.theater-staging.lifetales.com:component warn Component not connected, bouncing error for:
Apr 16 19:19:42 jcp5616e9192790 info Incoming Jabber component connection
Apr 16 19:19:42 focus.theater-staging.lifetales.com:component info External component successfully authenticated
Apr 16 19:19:43 mod_bosh info Client tried to use sid ‘8ff1ebfb-b222-461a-8f58-cea21588f957’ which we don’t know about
Apr 16 19:19:43 mod_bosh info Client tried to use sid ‘8ff1ebfb-b222-461a-8f58-cea21588f957’ which we don’t know about
Apr 16 19:19:43 mod_bosh info Client tried to use sid ‘8ff1ebfb-b222-461a-8f58-cea21588f957’ which we don’t know about
Apr 16 19:19:43 mod_bosh info Client tried to use sid ‘8ff1ebfb-b222-461a-8f58-cea21588f957’ which we don’t know about
Apr 16 19:19:43 mod_bosh info Client tried to use sid ‘8ff1ebfb-b222-461a-8f58-cea21588f957’ which we don’t know about
Apr 16 19:19:43 mod_bosh info Client tried to use sid ‘8ff1ebfb-b222-461a-8f58-cea21588f957’ which we don’t know about

please follow this guide, you wont encounter problems: docs.easyjitsi.com

thank you Joel - I scanned the instructions, other than OS version I did not see any differences. I am scrubbing the current install, building a new recorder box. I may be back :slight_smile: