I have successfully setup a standalone self-host jitsi-meet with jibri together. All 3rd-party conference and recording are working well before jwt enabled
But when I enabled the JWT as the official guide
I found all functions of jitsi-meet worked well except jibir with following errors:
2022-09-12 16:48:40.882 INFO: [162] AbstractPageObject.visit#38: Waited 555ms for driver to load page
2022-09-12 16:48:40.900 FINE: [162] CallPage$visit$$inlined$measureTimedValue$lambda$1.apply#58: Not joined yet: Cannot read properties of undefined (reading âisJoinedâ)
2022-09-12 16:48:41.405 FINE: [162] CallPage$visit$$inlined$measureTimedValue$lambda$1.apply#58: Not joined yet: Cannot read properties of undefined (reading âisJoinedâ)
2022-09-12 16:48:42.415 FINE: [162] CallPage$visit$$inlined$measureTimedValue$lambda$1.apply#58: Not joined yet: APP is not defined
2022-09-12 16:48:42.920 FINE: [162] CallPage$visit$$inlined$measureTimedValue$lambda$1.apply#58: Not joined yet: APP is not defined
Looks like the recording also need the jwt token to join. but I already set âallow_empty_token = falseâ in prosody, I am not sure whether I missed any other jwt configuration for jibri recording feature, please help me to figure out, thanks a lot
Hi emrah,
Thanks for your light, I try to change it to ârecorder@recorder.domainâ in prosody configuration and jibri recording work well with jwt enabled.
Thanks a lot for your support so quickly