Jitsi no longer works
Categories
(Core :: WebRTC, defect)
Tracking
()
Tracking | Status | |
---|---|---|
thunderbird_esr60 | --- | unaffected |
thunderbird_esr68 | --- | unaffected |
firefox-esr68 | --- | unaffected |
firefox74 | --- | unaffected |
firefox75 | --- | fixed |
firefox76 | --- | fixed |
People
(Reporter: emilio, Unassigned)
References
(Regression)
Details
(Keywords: regression)
See https://github.com/webcompat/web-bugs/issues/50333, where OP claims this is a regression from the dtls changes.
Updated•5 years ago
|
Comment 1•5 years ago
|
||
hi, i filed this as webcompat issue since i was unsure where such issues (intersection of browser changes and 3rd-party site compat issues) should live.
in the current situation where teleworking and videoconferencing are increasingly the way to go, jitsi meet is an option that is often recommended (among others also in my educational organisation with close to 100k students and staff), therefore it would be slightly concerning if that stops working in firefox 75.
Comment 2•5 years ago
|
||
Comment 3•5 years ago
|
||
https://github.com/jitsi/libjitsi/issues/441#issuecomment-600565878
if this is about the jvb, jvb2 supports dtls 1.2 and the intention is to switch to that for the debian stable package. I believe there's consensus to release jvb2 as debian stable, it's just a matter of the right people finding the time to do it /cc @damencho
jvb = jitsi-videobridge
Comment 4•5 years ago
|
||
https://bugs.chromium.org/p/webrtc/issues/detail?id=10261#c92
We do have DTLS 1.2 support in JVB 2, which does not use libjitsi. JVB 1, which does use libjitsi, won't get DTLS 1.2 support.
Comment 5•5 years ago
|
||
Are you sure about the regression range?
https://meet.jit.si/
works for me with
- Nightly and Nightly
- Chrome Dev and Chrome Dev
- Chrome Dev and Nightly, but ONLY if I disable uBlock Origin in Chrome. Disabling DTLS 1.3 did not help.
Comment 6•5 years ago
|
||
uBlock Origin: My manually enabled "Prevent WebRTC from leaking local IP address" was the cause in comment 5.
Comment 7•5 years ago
|
||
bug 1619102 was recently fixed.
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Description
•