Ours is a self hosted Jitsi. Whie it has been working well, suddenly few participants oflate have started complaning of “Failed to Access Camera/Microphone due to an Unknown Reason. Queue has been Stopped.” error. It has started happening with one with whom we have had successful VC in past too.
Its working on my own Chrome browser Version 103.0.5060.114 but on another participant on same version its not working.
Cache/cookies cleared. All permissions revoked and regranted, Cookies allowed for All, even tried in Incognito mode. tried all different microphone and sound output. Even our VC link is in permitted links to open. However Google Meet works so camera and mic doesnt have issues.
Here is the Console log from MY Chrome Browser while in conference with the other person when other person’s camera and mic is NOT working. I can neither hear nor see him. Nor can he.
And this is the Chrome Console Log of the person whose camera and mic is not working in self hoste Jitsi while in conference with me. (Mine doesnt work with one more chap, but his didnt work with others. It works on mobile for bother of them.)
There is PFSense Firewall, I found out. How do Hangouts, Team, Zoom, Webex etc navigate it?
One correction: it works on wifi which is through same LAN but when wifi is switched off and it is sought to be connected thriugh LAN, it doesnt work. This seems strange in my opinion.
This is also experienced by another user who is not behind any firewall. But it works on his ipad and mobile but now on his windows laptop: same issue.
Uploaded images of both screens: one where audio and video doesnt come and other which is ok.
Also, if meet.jit.si works fine and our self hosted instance doesnt work on this network (works at other places), does it mean Jitsi uses different ports for itself whereas we are using different ports?
If its ok, I can send a meet link now in message where both of us are there and you can check it.
But we are able to hold conference with other participants across India. This issue has been found with users on one network. And another such issue was randomly found with an individual.
Hence wouldnt it mean TURN is correctly configured, if I am getting other users?