google meet on new M1 processor MacBook

the problem is the ethernet adaptor

Open Console Log and when you start a meet you will see a lot of

"com.apple.WebKit.Networking LibWebRTCSocketClient::sendTo failed with error 38"

Unplug ethernet cable and restart the meet on wifi.

I found this to be an IPv6 issue (but the tip to try wifi rather than ethernet helped my diagnose thanks ikarmax)

Setting the ethernet adapter to use IPv6 'locally only' sorted it for me. I'm guessing my ISPs implementation of IPv6 isn't quite right. I'm still investigating though as this isn't a satisfactory true fix.

@SpennyDave Open System Preferences → Network. Select the Ethernet adapter from the list on the left, then click Advanced…. Select the TCP/IP tab, and within the Configure IPv6 dropdown, select Link-local only. Click OK to dismiss this modal, and then click Apply back in the Network preference pane.

mbroughton, just to be clear: are you referring to this "Link-local only" option in the Configure iPv6 setting in Sys-Pref: Network? (see attached screen shot). And then you can leave the ethernet cable plugged in and Google Meet video works?

I'm well versed in Macs, but changing TCP/IP settings makes me break into a sweat.

HI. Did you find a solution?

I'm having the same problem with MBP 16" (2019)-Intel. Google Meet audio/video will work in Firefox but in Chrome/Brave/Safari it won't. I can see my own video in the preview, but I can't send/receive any audio or video. Thank you.

Unplugging the ethernet cable and using wifi works for me, but is there a solution to be able to use ethernet? I am using a 2018 MacBook Air, that I recently upgraded to the Big Sur OS version 11.1. I suspect that the issue may be with this new OS.

Thank you so much for this this. I changed the IPv6 and now it works! As a teacher the past two days were terrible. Now it works again. Thank you.

Apple- will this be a future issue with software updates or will it be changed internally and automatically with the future updates?

Thank you so much mbroughton! I spent hours trying to figure out the problem and realized it was the ethernet adapter but I could not figure out anything else. I am not that savvy in terms of software and hardware issues, especially those related to network. I am glad Apple discussions exist and that kind and knowledgable people like you help and post solutions for us. Thanks, again.

I had the same issue where I could preview my webcam in Google Meets but everyone else on the call could only see my avatar. I tried going through all these solutions and still nothing. I had previously disabled hardware acceleration in Chrome and went to re-enable and that seems to have done the trick for me

So this seems to now be fixed (by Google). I'm now running Chrome Version 88.0.4324.96 and I don't have any lacking video / sound in Google Meet with IPv6 enabled (tested on M1 and Intel based systems running Big Sur 11.1)

NOTE: I've also tested M1 and Intel Chrome versions on their intended architecture.

I'm now running fully on my M1 based system and have all my software packages (non-Apple) running smoothly. These are truly superb systems. The step up to my M1 MacPro 13 from my previous 2015 MacPro is astonishing. The performance is better than that of most of the desktop systems I have in circulation (Linux & MS based Intel Xeon Silvers mostly with GTX 1660 Supers).

I've been using Macs since they became BSD based with Mac OS X 10.0 (Cheetah) . This latest step to their own M1 chip had me worried but I'm more of a fan now than I was before (no financial incentive from Apple in my statement - but I'm willing to try out the Mac Pro M1 free of charge when you're ready Apple)!

What an amazing hidden fix. In a million years, I never would've guessed that it had something to do with the TCP/IP settings. Thanks to all in this thread for this. Google Meet now works on my new M1 Mini.

I did check to see if the setting stayed in a restart, and it did, and so far, Meet works great with the Ethernet cable plugged in, and no weirdness in Safari searches or other websites.

Thank you mbroughton, I spent 2 hours with Google Support today to solve this issue and your response here is what solved it for me! HNY 2021.

Thank you! Worked like a charm.

I have filed a ticket with Google and they have acknowledged the issue and working on figuring a solution. Will know in the next few weeks on the resolution.

This also happens with intel macbooks, so worth mentioning inside the ticket that this doesn't apply just to M1 processor MacBooks.