Any Reprts of Some People's Difficulty with Video

I have one person said that they could not get it to recognize her camera or microphone.

I have no problem and connect without issue.

I see the following warning in prosody.log.1

Nov 03 14:28:15 conference.meet.politea.us:muc_domain_mapper    warn    Session filters applied
Nov 03 14:28:15 mod_bosh        info    New BOSH session, assigned it sid '8c5ce780-b47a-4018-a2d9-ae39cdfaa015'
Nov 03 14:28:16 bosh8c5ce780-b47a-4018-a2d9-ae39cdfaa015        info    Authenticated as hvx1bpyqrnmdfblv@meet.politea.us
Nov 03 14:28:25 bosh8c5ce780-b47a-4018-a2d9-ae39cdfaa015        info    BOSH client disconnected: session close
Nov 03 14:28:25 speakerstats.meet.politea.us:speakerstats_component     warn    A module has been configured that triggers external events.
Nov 03 14:28:25 speakerstats.meet.politea.us:speakerstats_component     warn    Implement this lib to trigger external events.

What action do I need to take if any?

Is this on your own Jitsi server or on meet.jit.si?

This is on self hosted,Ubuntu 20.04.1 LTS, Prosody 0.11.7, Lua 5.2, LuaRocks 2.4.2, Jicofo 1.0-644-1, and jitsi-videobbridge2 2 2.1-376

Get that person to do a test on test.webrtc.org. That will help troubleshoot issues with their camera and mic.

Freddie, what about those warnings

Nov 03 14:28:15 conference.meet.politea.us:muc_domain_mapper    warn    Session filters applied
Nov 03 14:28:25 speakerstats.meet.politea.us:speakerstats_component     warn    A module has been configured that triggers external events.
Nov 03 14:28:25 speakerstats.meet.politea.us:speakerstats_component     warn    Implement this lib to trigger external events.

speakerstats.meet.politea.us in defined in meet.politea.us.cfg.lua

Component "speakerstats.meet.politea.us" "speakerstats_component"
    muc_component = "conference.meet.politea.us"

By the way, thanks for the rapid fire responses.

Since everyone else connected without problems, I would first focus on the client’s environment. Usually when people have connection issues like this on Jitsi (and it’s not general - meaning, affecting all participants), it’s because they have issues on their end. Let them test to confirm webrtc detects their camera and microphone first and then you can consider other things after that.

Thanks a ton Freddie.