Multiple Problems with Video and/or Audio Not Working in Calls on via browser

Hi Jitsi team,

We’ve got a community of people using Jitsi to match up for calls and sessions, within the last few weeks users have had increasing problems using for these connections.

Everything from dropped connections, to video and audio not working on one side or the other, sometimes both sides.

My question is, has anything significant changed in the last couple weeks that would generate these types of issues using

These are often users who have had no problems or much fewer problems using the video sessions before now and it’s not clear yet if there’s a pattern to what is causing the issue.

Are you receiving other reports like this, I don’t seem to see much in the forums here about issues.

I’m wondering if variables we are passing in a url are part of the problem have or if there’s just an increase of usage that’s making the connections problematic.

I’d be interested if you have any insight into what might potentially be the issue here. We’ve got users on Mac and Windows, Firefox and Chrome, some mobile users as well but I haven’t heard any reports of issues with Mobile yet.

Sometimes it seems reloading helps, other times it doesn’t.

Any insight you might have into this issue, I know that I’m providing just general information at the moment but if there’s more I could do to provide helpful info for troubleshooting please let me know.

I will look at the chrome://webrtc-internals to try to investigate more as well, based on some info that was shared in another thread too.

Thanks for your help

@saghul Interested in your thoughts on this if possible, thanks!

Hi Natahn,

Thanks for taking the time to provide feedback, and sorry you’re running into trouble. Let’s see if there is anything I can do to help.

Dropped connections are hard to avoid, but we are actively working on being more relisient to those, in addition to improving the UX when it happens. Can you elaborate a bit on the audio / video not working on one side? What media types were people using? Was there screen-sharing involved?

We recently discovered a bug in Octo and disabled it. This might have had an impact if you have participants in multiple regions, is this your case?

We are aware of another issue that may have affected you, if you were using screen-sharing: it may cause audio degradation, because of a bug in our bandwidth allocation mechanism, this is also being worked on at the moment.

We are not receiving these kind of reports lately, but that doesn’t mean we are problem free :slight_smile:

What URL parameters are you passing? Regarding usage, while we do see growth, I don’t think it can explain what you are experiencing.

In this scenario there are 2 actors that may contribute to a subpar experience for the receiver: Firefox and Android devices. We don’t yet support simulcast on either of those (it’s coming to Android soon) so this means they’ll be sending 720p all the time, and there is nothing we can do about it on the server side.

1 Like

@saghul Thank you for the detailed reply! I’ll post some replies below and I have also sent you a DM to follow up with some private details.

Mainly we are doing 1 on 1 video sessions, no screensharing or additional group members involved. Various problems happen and it’s not consistent across users, I will try to document those specifically and share more details but essentially people who have had no problems in the past suddenly have issues with getting the camera/audio to work and I’ve also troubleshooted with them so it’s not specifically user error or permissions problems because even resetting them doesn’t resolve the issue.

Reloading often helps when dropped connections happen, I think this points to an issue with reconnecting after a drop on p2p connections specifically, not sure about JVB. I think I read something where others were having a similar problem in this scenario.

Definitely sounds like this would affect us, a huge percentage of sessions involve participants in multiple regions. Is this live on now?

Here’s one set of variables we’ve used, I was worried maybe something there was causing our issues or not helping the situation at least…

I know a lot of this was added to try and combat some issue people had reported in the past, there’s a % of user who find that Jitsi takes up too much resource wise on their systems and since the purpose of our sessions are to get work done, it becomes a real challenge. Anything we can do to limit the resource use we are trying. It seems in P2P sessions none of the url variables seem to be respected though so we have to direct people to manage call quality manually but still some people have too much resource usage.

This definitely seems like it would be a factor, some people in our community have switched to Firefox and mobile to try and deal with the resource usage problem or the connection issues they were having in Chrome.

Thanks again for your detailed replies, I really appreciate it!

Let me know if there’s anything else I can provide to get more insight. I also sent you a DM with some additional private info.

1 Like

Yes please document those and let us know. Knowing the involvied devices is also important: we don’t support P2P mode on Firefox, so traffic will needlessly go through the bridge even in 1-1 calls, for example. should be working ok now, in this regard.

Those options should be harmless. The “Manage Call Quality” options won’t apply to P2P calls, but the URL parameters should.


Same issue happening with us. We able to connect and hear audio and see video sometimes. But sometimes both doesn’t work. And for some users it’s not working at all.

@bhakti Is Firefox involved?

We are testing on Chrome.Currently Our application is chrome specific so we are not using firefox.


Same issue happening with me. Trying to connect to gymnasium class videoconference on For most participants it is working, for some sometimes, for some not at all. The meeting is usually around 11am on working day. I belong to the group of users, for which it is working nearly not at all.
In our family we have computers with Win7, Win8 and Win10. I know already, Jitsy supports Chrome only, so we try to connect mostly via Chrome. I also know, Jitsy requires fast internet connection. We have in our family 16Mbit/down, 2,5 Mbit/up really reliable. According my understanding, it shouldn’t be a problem.
Doesn’t matter, which computer I am trying to use to connect the meeting, the connection doesn’t work. I am always alone in the meeting. Sometimes error message appears about connectin error. Only twice, by fortune, one Win8 computer in our family connected via Opera browser, and second time (next week) one Win7 computer connected via Chrome browser. Refresh of the website doesn’t help.
All compuerts are beind a family router with Gigabit network. NAT and firewall on the router are switched off. The PCs have otherwise standard configuration and internet is working for all family members withut issue.
Because there seems to be more students having difficulties to connect, the teacher splitted the lessons to two groups (in the size around 15 students) in the hope to improve the connectivity. It didn’t help.
Any tips or hints, what it may cause, that for some of the participants the meeting is working without problems and not for me? Any possibilty to display any kind of a log in the browser, which would point out to a problem?

Thanks in advance for support

Do you see a message connection error, something like this:

But I remember this message only once. There was no further explanation nor additional details. In 99% cases just nothing happens. I am simple alone in the meeting room.

We found a bug in the deployment and a fix is coming, probably today.

Which version numbers include this fix? I want to check the jvb version via dpkg, since we’re using your apt mirror for all packets.


EDIT: Do you publish changelogs in any way? I didnt found nothing, except which is not up-to-date.

ii  jitsi-meet            2.0.4384-1          all          WebRTC JavaScript video conferences
ii  jitsi-meet-prosody    1.0.3969-1          all          Prosody configuration for Jitsi Meet
un  jitsi-meet-tokens     <none>              <none>       (no description available)
ii  jitsi-meet-turnserver 1.0.3969-1          all          Configures coturn to be used with Jitsi Meet
ii  jitsi-meet-web        1.0.3969-1          all          WebRTC JavaScript video conferences
ii  jitsi-meet-web-config 1.0.3969-1          all          Configuration for web serving of Jitsi Meet
un  jitsi-videobridge     <none>              <none>       (no description available)
ii  jitsi-videobridge2    2.1-164-gfdce823f-1 all          WebRTC compatible Selective Forwarding Unit (SFU)
ii  prosody               0.11.2-1            amd64        Lightweight Jabber/XMPP server
un  prosody-0.11          <none>              <none>       (no description available)
un  prosody-modules       <none>              <none>       (no description available)
un  prosody-trunk         <none>              <none>       (no description available)

We publish changelogs ()extracted commit messages) when we do a stable release
We did 3 releases in a row and maybe 4th is coming so not sure how useful are those …
About the connection error the fix is simple, but will not come on update: as we do not overwrite already existing prosody configurations.

Okay. Assuming I installed the versions above on a new system, are the prosody changes then there?

EDIT: I can confirm, the versions above include the fix when installing on a new system.

Some tests on our side showed, that a group with 10 participants using firefox lead more likely to a “crash” (video/audio problems) than another test group with Chrome as browser.

I dont know how to verify that. Does Firefox has issues with WebRTC? We are using at least the latest ESR version, up to stable 47.0.1.

Firefox doesn’t offer simulcast, and so offers a worse experience than Chrome / requires more bandwidth.


Ah, I just found that, based on your info regarding simulcast:

So it seems to be indeed a firefox issue.

I want to use Jitsi but I cannot successfully allow camera access on my MacBook Air. I see that many people are having this problem. Frustrated, to be honest, as this seems to be a great alternative to Zoom.

What browser are you using? If Safari, video is not supported at the moment.

Firefox works on macOS (subject to the usual caveats around Firefox), and I believe Chrome works too, but I haven’t tested it myself.

1 Like