Jibri recording not working as Prosody throws "Error verifying token err:not-allowed, reason:token required"

We are using jwt token for user authentication through our application. And external api call to connect to jitsi meeting. Meeting starts, then clicking on start recording says recording is starting and after a while says can’t record.

This is from prosody logs:

This is my jibri logs:
jibriLogs.txt (16.6 KB)

I have added recorder@recorder.meet.jitsi in admins in jibri config. Am I missing any config?

Try adding prosody config enable_domain_verification = false

I set the env variable enable_domain_verification = false, but still the same error remains. This is the jibri logs now:
jibriLogs.txt (28.6 KB)

Same error in prosody too:

New BOSH session, assigned it sid ‘eb1ce5c5-b386-42fd-854e-540f213e7da9’
general warn Error verifying token err:not-allowed, reason:token required
bosheb1ce5c5-b386-42fd-854e-540f213e7da9 info BOSH client disconnected: session close

Where did you add that? Put it under the main muc component.

I set it up in the EC2’s env variable. The screenshot is from before the value was changed to false. We are using docker to load image to EC2.

Which muc component should I add it to?

If you are using docker there is such variable already

Yes, the value for $JWT_ENABLE_DOMAIN_VERIFICATION is set under the task in EC2. I set it to false and restarted the task (jitsi instance). Jitsi and jibri are in the same instance.

Are there any other configs to check?

Set JWT_ENABLE_DOMAIN_VERIFICATION to false.

No luck with JWT_ENABLE_DOMAIN_VERIFICATION=false.

Do I need to add recorder@recorder.meet.jitsi under admins in prosody.cfg.lua?
admins = { recorder@recorder.meet.jitsi }

Try that

No. Prosody still throws the same error.

These are my jibri
JibriEnvVariables.txt (1002 Bytes)

and prosody env variables.
prosodyEnvVariables.txt (1.2 KB)

These are the errors:

From Jibri -
Jibri 2022-11-29 19:16:08.920 INFO: [103] [session_id=oalrixijdgbnxutl] JibriSelenium.onSeleniumStateChange#215: Transitioning from state Starting up to Error: FailedToJoinCall SESSION Failed to join the call
Jibri 2022-11-29 19:16:08.920 INFO: [103] [session_id=oalrixijdgbnxutl] StatefulJibriService.onServiceStateChange#39: File recording service transitioning from state Starting up to Error: FailedToJoinCall SESSION Failed to join the call
Jibri 2022-11-29 19:16:08.920 INFO: [103] XmppApi$createServiceStatusHandler$1.invoke#311: Current service had an error Error: FailedToJoinCall SESSION Failed to join the call, sending error iq <jibri xmlns=‘http://jitsi.org/protocol/jibri’ status=‘off’ failure_reason=‘error’

From prosody -
New BOSH session, assigned it sid ‘48dd9874-ce8e-4da8-bfa8-7af29d9bd807’
general warn Error verifying token err:not-allowed, reason:token required
bosh48dd9874-ce8e-4da8-bfa8-7af29d9bd807 info BOSH client disconnected: session close

From jicofo -
Jicofo 2022-11-29 19:15:35.675 INFO: [47] [room=93972111667805459233@muc.meet.jitsi meeting_id=062c5146-7165-4722-bd1d-665ea5776907] JibriSession.startInternal#319: Starting session with Jibri jibribrewery@internal-muc.meet.jitsi/jibri-983315834
Jicofo 2022-11-29 19:15:35.676 INFO: [47] [room=93972111667805459233@muc.meet.jitsi meeting_id=062c5146-7165-4722-bd1d-665ea5776907] JibriSession.sendJibriStartIq#473: Starting Jibri jibribrewery@internal-muc.meet.jitsi/jibri-983315834 for stream ID: null in room: 93972111667805459233@muc.meet.jitsi
Jicofo 2022-11-29 19:15:36.243 INFO: [47] [room=93972111667805459233@muc.meet.jitsi meeting_id=062c5146-7165-4722-bd1d-665ea5776907] JibriSession.processJibriIqFromJibri#434: Updating status from JIBRI: for 93972111667805459233@muc.meet.jitsi
Jicofo 2022-11-29 19:15:36.243 INFO: [47] [room=93972111667805459233@muc.meet.jitsi meeting_id=062c5146-7165-4722-bd1d-665ea5776907] JibriSession.handleJibriStatusUpdate#622: Got Jibri status update: Jibri jibribrewery@internal-muc.meet.jitsi/jibri-983315834 has status pending and failure reason null, current Jibri jid is jibribrewery@internal-muc.meet.jitsi/jibri-983315834
Jicofo 2022-11-29 19:15:36.244 INFO: [47] [room=93972111667805459233@muc.meet.jitsi meeting_id=062c5146-7165-4722-bd1d-665ea5776907] JibriRecorder.handleStartRequest#113: Started Jibri session
Jicofo 2022-11-29 19:15:39.610 INFO: [47] ConferenceIqHandler.handleConferenceIq#63: Focus request for room: 93972111667805459233@muc.muc.meet.jitsi
Jicofo 2022-11-29 19:15:44.774 INFO: [47] ConferenceIqHandler.handleConferenceIq#63: Focus request for room: 93972111667805459233@muc.muc.meet.jitsi
Jicofo 2022-11-29 19:15:49.840 INFO: [47] ConferenceIqHandler.handleConferenceIq#63: Focus request for room: 93972111667805459233@muc.muc.meet.jitsi
Jicofo 2022-11-29 19:15:54.925 INFO: [47] ConferenceIqHandler.handleConferenceIq#63: Focus request for room: 93972111667805459233@muc.muc.meet.jitsi
Jicofo 2022-11-29 19:15:59.993 INFO: [47] ConferenceIqHandler.handleConferenceIq#63: Focus request for room: 93972111667805459233@muc.muc.meet.jitsi
Jicofo 2022-11-29 19:16:05.100 INFO: [47] ConferenceIqHandler.handleConferenceIq#63: Focus request for room: 93972111667805459233@muc.muc.meet.jitsi
Jicofo 2022-11-29 19:16:08.922 INFO: [18] [room=93972111667805459233@muc.meet.jitsi meeting_id=062c5146-7165-4722-bd1d-665ea5776907] BaseJibri.handleJibriRequest#75: Accepted jibri request:
Jicofo 2022-11-29 19:16:08.923 INFO: [47] [room=93972111667805459233@muc.meet.jitsi meeting_id=062c5146-7165-4722-bd1d-665ea5776907] JibriSession.processJibriIqFromJibri#434: Updating status from JIBRI: for 93972111667805459233@muc.meet.jitsi
Jicofo 2022-11-29 19:16:08.923 INFO: [47] [room=93972111667805459233@muc.meet.jitsi meeting_id=062c5146-7165-4722-bd1d-665ea5776907] JibriSession.handleJibriStatusUpdate#622: Got Jibri status update: Jibri jibribrewery@internal-muc.meet.jitsi/jibri-983315834 has status off and failure reason error, current Jibri jid is jibribrewery@internal-muc.meet.jitsi/jibri-983315834
Jicofo 2022-11-29 19:16:08.924 INFO: [47] [room=93972111667805459233@muc.meet.jitsi meeting_id=062c5146-7165-4722-bd1d-665ea5776907] JibriSession.handleJibriStatusUpdate#661: Jibri failed, trying to fall back to another Jibri
Jicofo 2022-11-29 19:16:08.924 SEVERE: [47] [room=93972111667805459233@muc.meet.jitsi meeting_id=062c5146-7165-4722-bd1d-665ea5776907] JibriSession.startInternal#307: Unable to find an available Jibri, can’t start
Jicofo 2022-11-29 19:16:08.926 WARNING: [47] [room=93972111667805459233@muc.meet.jitsi meeting_id=062c5146-7165-4722-bd1d-665ea5776907] JibriSession.handleJibriStatusUpdate#672: Failed to fall back to another Jibri, this session has now failed: org.jitsi.jicofo.jibri.JibriSession$StartException$AllBusy: All jibri instances are busy
org.jitsi.jicofo.jibri.JibriSession$StartException$AllBusy: All jibri instances are busy
at org.jitsi.jicofo.jibri.JibriSession.startInternal(JibriSession.java:311)
at org.jitsi.jicofo.jibri.JibriSession.start(JibriSession.java:285)
at org.jitsi.jicofo.jibri.JibriSession.retryRequestWithAnotherJibri(JibriSession.java:598)
at org.jitsi.jicofo.jibri.JibriSession.handleJibriStatusUpdate(JibriSession.java:665)
at org.jitsi.jicofo.jibri.JibriSession.processJibriIqFromJibri(JibriSession.java:436)
at org.jitsi.jicofo.jibri.JibriSession.processJibriIqRequestFromJibri(JibriSession.java:420)
at org.jitsi.jicofo.jibri.BaseJibri.doHandleIQRequest(BaseJibri.kt:156)
at org.jitsi.jicofo.jibri.BaseJibri.incomingIqQueue$lambda-0(BaseJibri.kt:56)
at org.jitsi.utils.queue.PacketQueue$HandlerAdapter.handleItem(PacketQueue.java:416)
at org.jitsi.utils.queue.AsyncQueueHandler$1.run(AsyncQueueHandler.java:136)
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.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:829)
Jicofo 2022-11-29 19:16:08.927 INFO: [47] [room=93972111667805459233@muc.meet.jitsi meeting_id=062c5146-7165-4722-bd1d-665ea5776907] JibriRecorder.publishJibriRecordingStatus#158: Got jibri status off and failure error
Jicofo 2022-11-29 19:16:08.928 INFO: [47] [room=93972111667805459233@muc.meet.jitsi meeting_id=062c5146-7165-4722-bd1d-665ea5776907] JibriRecorder.publishJibriRecordingStatus#183: Publishing new jibri-recording-status: in: 93972111667805459233@muc.meet.jitsi

Any insight on what needs to be fixed here?