Google Meet now works for me in Firefox!

VPN
1

For a long time now I wasn’t able to use Google Meet or any other voice/video calling features on Firefox. It wasn’t an issue with the camera or microphone permissions as you can see in the screenshot below that they work fine. The issue was the page would get stuck on an endless “Getting Ready” loop.

\“Getting Ready\” Forever!

I had to use Microsoft Edge Chromium to attend my classes as my otherwise quirky, default browser, Firefox didn’t let me. And that was quite irritating to me :confused:

I was searching about the issue when I came to this thread on Bugzilla:https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwjT1OuFlLrqAhVSfSsKHc53C0gQFjACegQIAhAB&url=https%3A%2F%2Fbugzilla.mozilla.org%2Fshow_bug.cgi%3Fid%3D1607781&usg=AOvVaw3NGbrLhwXnpfw3ehfTDpgR

What I learnt from there was this issue could be resolved if you set the status of “resist.fingerprinting” in about:config to “false”. The funny thing was, that parameter was already set to “false” from the beginning! Next, I tried running Firefox with all my extensions disabled and it didn’t work then as well and frankly i was done…Yesterday, I downloaded the Nightly version to have a go at this again. Without any extensions Meet worked fine, but the thing was why didn’t it run on the default release when all the extensions were disabled then? Anyway, I downloaded my extensions which i download on any browser that I use: UBlock Origin, Nano Defender, Hoxx Vpn, webRTC Shield from Hoxx (and in this order). Every time I downloaded one, i checked Meet; it worked, until the WebRTC Shield.

And thus I recognised the culprit not letting me use Meet on Firefox…a quick read on Wikipedia made me understand why WebRTC was needed for communication anyway. And guess what happened when I disabled the Shield and went to Meet to start a meeting?

It works when i disable WebRTC extension (the extension at the extreme right)

TL;DR If you use any sort of WebRTC Shield extension (there are many) and the service you want to use requires WebRTC, you gotta disable it! As simple as that! :wink:

Edit: On suggestion from u/ExtraFoamMacchiato , I tried using Meet with “resist.fingerprinting” set to true. It works! So I can safely assume the error was caused only by the webRTC leak shield extension.

2

Google meet doesn’t work on my chromium but it works on Firefox for me(been using it for a couple of months), not sure why I didn’t work for you before.

3

Literally what happened to me yesterday!

4

As you have already suspected, Google Meet requires WebRTC enabled to be able to be used.

There’s really no need to use any webRTC extensions when you can just do the following in the about:config. This will completely disable webrtc.

media.peerconnection.enabled = false

media.peerconnection.turn.disable = true

media.peerconnection.use_document_iceservers = false

media.peerconnection.video.enabled = false

media.peerconnection.identity.timeout = 1

5

I’ve had the same issue for a long time, but didn’t have a webRTC addon installed nor did touch resist.fingerprinting help. In the end I managed to get meet.google.com to skip “Getting Ready” “You’ll be able to join in just a moment” by refreshing Firefox from about:support. Probably had some incompatible add-on or setting that lingered around. Keep in mind that this resets add-ons and settings, more info here.

6

It actually works for me with resistFingerprinting enabled, which is nice. I also run it in its own container :slight_smile:

7

It maybe that you don’t use any webRTC leak shield extension or your “resist.fingerprinting” parameter is set to false by default. Tinkering with these can break Google Meet on your Firefox.

and you mentioned Google Meet not working on Chromium right? well i gotta admit on Chrome itself, Google Maps wasn’t able to find my location whereas Firefox did that quite well…lol

8

woah man, you had the issue with webRTC or resist.fingerprinting?

9

thanks a lot, i need to save this comment

10

It is interesting to know that something other than those two factors can also break Meet. I downloaded Nightly specifically for testing this out with a new profile such that whatever i launched, be it Firefox or Nightly, it would ask me which profile to launch before starting everytime. Once the issue was solved, I found that the mic and camera floating indicator could be minimised in Nightly rather than the annoying one in stable Firefox. So my new config was: Nightly app+default profile and i removed Firefox Release app and the new experiment profile Nightly created…so no data loss

11

Just webRTC.
Off topic but how to get those icons beside your name?

12

Fingerprint resistance should not affect Google Meet. I’m also a Firefox - Google Meet user and I have it on.

13

Oh you mean the user flairs…you will find them under community options on the right…you get a few default flairs but you can edit them as you like…that’s the fun part…until now my flair had the Preview nightly + android logo

14

Just verified this; I can use Google Meet with “resist.fingerprinting” to true!

15

Thanks i was able to find for the firefox one. Where is the windows one?

16

You can add :windows: after :dev:

You can see the icon code when you hover over it