-
Notifications
You must be signed in to change notification settings - Fork 6.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jitsi doesn't work in Firefox-based browsers #13839
Comments
Do you experience the same on meet.jit.si? Upload js console logs from the browser |
I have no idea how it is on meet.jit.si, it requires some weird login so I am not able to use it.
Sure, here is what I had in the console when I first opened a link with a meeting with a participant, activated video/audio, and joined the meeting:
|
Then what is the jitsi-meet version you use?
That is a pretty old version of Firefox, were you able to try something more recent? |
Absolutely not old, as mentioned in the initial post the browsers I use are of recent versions:
This comes from Mullvad v12.5.4 which was released a few days ago and is based on recent 102.15.1 ESR |
That link doesn't tell us what server version they installed. It would be best if you could test with meet.jit.si since it always runs the latest. |
I would do that with pleasure, however I don't know how:
|
Once you click on login you'll be presented with a site which allows you to login with either Google, Facebook or GitHub. After logging in you'll be redirected to the meeting, but authenticated. You only need to do this for the first participant which joins the meeting. |
Sorry, but I cannot do this.
|
You are using GitHub right now. |
This comment has been minimized.
This comment has been minimized.
I just tested the issue using MullVad on Windows, together with Firefox/Chrome too, specifically on meet.jit.si. Apart from a few bandwidth drops, which seem unrelated, both the microphone and camera worked as expected. I did notice that Firefox performed slightly better compared to Mullvad, which could be due to some requests being blocked by the VPN. If you're not using meet.jit.si and have customized your installation, could you please provide more details? It's possible that the issue isn't directly related to Jitsi but rather due to specific security settings in your environment. Otherwise, I think we should close this one. |
Wait, was it Mullvad Browser, or Mullvad the VPN thing?
You mean the meeting participants could see and hear you, and you could see and hear them?
Which VPN do you mean, there is no VPN, Mullvad is basically Tor browser without the Tor component
I have tested using default clean profiles in Mullvad Browser and Librewolf
Ok, later in a few days I will test and check the firewall logs again and report if there was something I didn't notice before |
Why did you close the issue? Could you open it? |
I'll reopen if you can provide logs of a failed meeting, otherwise theee is nothing actionable here. |
I already provided the log, see above. Moreover, in my response to Codeshark-NET I replied that I will check everything again later in a few days. So, could you open it? |
Mullvad browser.
Yep!
That's my mistake, I was referring to the browser and its security features. |
I remember I also disabled fingerprint resistance in about:config in Mullvad to see if it makes it work (it didn't), and double-checked that WebRTC feature is enabled (and it was enabled by default) (And the same issue was faced in Librewolf, which uses a different and non-ESR browser engine version) Anyway, this is very strange that you got it work in Mullvad Browser, did you alter any default parameters or was it a fresh vanilla profile? |
No, I installed it fresh to check this exact issue. Couldn't replicate. I'm afraid you may have to be open to it being something on your end. I'll keep an eye out for your further testing here, but until then, @saghul is right that there's not much we can do outside of this. |
I finally got to test it again. One more thing I wanted to check was my Firewall. Also, it seems like the remote video/audio-stream are just not allowed to play. |
I can confirm that Firefox under Linux OS (Debian, Fedora) does not work....audio and video are muted But a WIN 7 OS, Firefox 115 works |
I don't think the operating system is the problem but the version, can you confirm? |
Fedora 37 kernel 6.5.7-100, Firefox 118.0.2 --- works ok So maybe Firefox 115 => works Update: |
Ping @jallamsetty1 |
I tried FF 102esr and I confirm it does not work:
Test it on alpha. |
Thanks @damencho, I will try with FF 102 ESR. |
When RTCRtpReceiver.getCapabilities() is not supported by browser or if it returns an empty list. Fixes an issue where call doesn't get established in Firefox ESR 102. Fixes jitsi/jitsi-meet#13839.
What version of Firefox are you seeing this on? Are you seeing the same behavior on meet.jit.si as well? |
I have no more information for now but some customer using Firefox started to tell us that Jitsi (on prem) is not working anymore : continuous deconnexion . We will provide more details when we have them |
When RTCRtpReceiver.getCapabilities() is not supported by browser or if it returns an empty list. Fixes an issue where call doesn't get established in Firefox ESR 102. Fixes jitsi/jitsi-meet#13839.
When RTCRtpReceiver.getCapabilities() is not supported by browser or if it returns an empty list. Fixes an issue where call doesn't get established in Firefox ESR 102. Fixes jitsi/jitsi-meet#13839.
When RTCRtpReceiver.getCapabilities() is not supported by browser or if it returns an empty list. Fixes an issue where call doesn't get established in Firefox ESR 102. Fixes jitsi/jitsi-meet#13839.
When RTCRtpReceiver.getCapabilities() is not supported by browser or if it returns an empty list. Fixes an issue where call doesn't get established in Firefox ESR 102. Fixes jitsi/jitsi-meet#13839.
When RTCRtpReceiver.getCapabilities() is not supported by browser or if it returns an empty list. Fixes an issue where call doesn't get established in Firefox ESR 102. Fixes jitsi/jitsi-meet#13839.
When RTCRtpReceiver.getCapabilities() is not supported by browser or if it returns an empty list. Fixes an issue where call doesn't get established in Firefox ESR 102. Fixes jitsi/jitsi-meet#13839.
When RTCRtpReceiver.getCapabilities() is not supported by browser or if it returns an empty list. Fixes an issue where call doesn't get established in Firefox ESR 102. Fixes jitsi/jitsi-meet#13839.
Can confirm, firefox doesn't work. Tried on multiple systems. Using Firefox 128 on W11 & W10 Will fetch all the logs from my containers tomorrow, I've been troubleshooting this for a few hours now and didn't for ONCE think it could be the damn browser so I'mma just take the L and go home to my dog to make up. Be back in ~18 hours. |
@guemi Are you able to reproduce this issue on meet.jit.si? If you are not able to reproduce it there, we suggest you to update your deployments to the latest stable and test it again. |
I'll try, I updated to latest stable like a week ago as part of major update of infra. But I'll verify tomorrow and let you know.
Any specific things you want from the browser, or only the container logs?
I can connect, chat is working but no video or audio is coming through or received by other user.
|
Please try to reproduce the issue on meet.jit.si first. If you reproduce it there, please share the browser console logs. |
See #5230 (comment) |
meet.jit.si works splendid with the same systems, same browsers but not on the on premises solution. Just tried, I deleted all the images off the docker host and ran the stack again so it 100% pulled the images: But no dice. Firefox does not work, picture is available until someone joins, then it disappears. If I join the same meeting in Edge, it works flawlessly. Chat message from client1 and client2 works splendid. Attached is the console output from Firefox |
|
Can you pls compare meet.jit.si settings at https://meet.jit.si/config.js with that of your deployment and see what is different? |
These files are extremely different, the variable names and what not are not the same -is that to be expected? Here's a snippetof the on prem solution;
Is that correct? Many if statements seem completely missing from SaaS JITSI, but is present on on-premises. |
Can you pls add
and check if that makes any difference? |
Hi
Checked the solution Observation: Is there any specific config setting for latest version of firefox to fix the issue? Thanks! Note: Firefox version that tested up to 124 is working fine. |
Can someone please share the JVB log from their deployment? I am unable to reproduce the issue on meet.jit.si |
Are these logs from the latest stable? There seems to be some mixup with the upgrade process, as per the logs you are running a much older version of the client. |
What backend version are you using? |
Ugh, apparently the version variable in the docker compose was set to -stable-8252 rather than -stable. Fixed that now. And you're right, Firefox worked. I recommend the rest of you checking the same, I'm not sure why you'd specify a specific version but recommend you configure your docker-compose like this;
Rather than what I had before;
|
Hi, |
Hi jallamsetty1, Any update on my above comment. Thanks |
Both the versions are old, one is an year old and the other one is 6 months old. We suggest upgrading to the latest stable from July 2nd for the issue to be fixed. |
Hi, |
Does anyone have any idea what change/commit fixes this issue? Thanks. |
I believe it is this bridge commit - jitsi/jitsi-videobridge@573abcd |
Description:
Jitsi doesn't work in Firefox-based browsers.
Meanwhile, it works in Chromium-based browsers.
Steps to reproduce:
Expected behavior:
Everything works.
Actual behavior:
When I start a conference in Jitsi (with camera and mic enabled ofc), the situation is as follows:
Server information:
Client information:
Additional information:
The text was updated successfully, but these errors were encountered: