Closed thinkski closed 5 years ago
Now getting the same on my laptop (macOS Mojave 10.14.2, Chrome 71.0.3578.98 as well as Safari 12.0.2 (14606.3.4)). Suspecting upgrade to 10.14.2 on Mojave causes IPv6 candidates to be sent.
So looks like the IPv6 candidate is causing the connectivity check to fail, which is logged as fatal, but I don't think it should be -- making it non-fatal fixes the immediate issue (d237133). Created a new issue for adding IPv6 support (https://github.com/thinkski/webrtc/issues/26).
Looks like IPv6 wasn't an issue because of macOS but rather AT&T Uverse, which both Chris' and Nicole's parents use.
Asked Nicole to try connecting to my RPi from her parent's house in Florida. She is on Mac OS X, first tried in Chrome, once more in Chrome, then Safari, yielding the same result, a failure to send a connectivity check -- missing address. It did, however, work from her iPhone, which was connected to wifi, the last connection attempt below:
@jwgcarlson Could this be related to the IPv6 addresses? Would you have time to look into this while she is out there so we can test again?