1760499 - WebRTC DataChannel connections cannot be established in FF 98.0.1 (32 bit)

Status: RESOLVED INCOMPLETE

(Core :: WebRTC: Audio/Video, defect)

Description

[Ferdinand Seidenschwan]

Attachment: Screenshot_2022-03-20_140811_-_Threema_Web_Client_Troubleshooting_Result.png

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:98.0) Gecko/20100101 Firefox/98.0

Steps to reproduce:

I tried to start a session for the Threema web client:
https://web.threema.ch/

This did not work, so I opened the diagnostic/troubleshooting page:
https://web.threema.ch/troubleshoot/

Actual results:

The diagnostic/troubleshooting summary states that WebRTC DataChannel connections cannot be established.

I've tried the same two URLs in Google Chrome with different outcomes compared to Firefox:
The diagnostics result were alle positive/green and the session for the Threema web client could be started without any problem.

Expected results:

The Threema web client session should have been started.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::WebRTC: Audio/Video' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Michael Froman [:mjf]]

ferdinand, thank you for the report! I have tried it here on my Windows machine. I had to click the "Android" button when it asked what type of mobile device I used. I'm not sure if that is relevant or not. However, I do see all green check marks including for the data channel test.

If you could re-run your test, then enter about:webrtc in the url bar. There is a Save Page button at the top. Please save the about:webrtc page and attach the results here. That will help us start debugging the issue.

Comment 3

[Ferdinand Seidenschwan]

Attachment: aboutWebrtc.html

Comment 4

[Ferdinand Seidenschwan]

Hi Michael,

sorry, I forgot to mention that it is necessary to click the "Android" button to start the appropriate diagnostic run. (-_-)'

I've re-run the diagnostic page and the result is still the same.
So I added the "aboutWebrtc.html" file as you requested.
I hope it is OK that some parts are localized in German.

BTW: I've also tried to use a private tab/window. Still the same result.

Cheers
-Ferdinand-

Comment 5

[Ferdinand Seidenschwan]

Attachment: connection_protocol.txt

Comment 6

[Ferdinand Seidenschwan]

Also tried again with Firewall disabled. Same result.

Comment 7

[Ferdinand Seidenschwan]

Tried new empty profile. Same result.

Comment 8

[Michael Froman [:mjf]]

Attachment: example aboutWebrtc.html

Example aboutWebrtc.html from Windows.

Comment 9

[Michael Froman [:mjf]]

(In reply to ferdinand from comment #4)

Hi Michael,

sorry, I forgot to mention that it is necessary to click the "Android" button to start the appropriate diagnostic run. (-_-)'

I've re-run the diagnostic page and the result is still the same.
So I added the "aboutWebrtc.html" file as you requested.
I hope it is OK that some parts are localized in German.

BTW: I've also tried to use a private tab/window. Still the same result.

Cheers
-Ferdinand-

Thank you for trying the new profile/private browsing/disabled firewall cases - that definitely helps.

Your attached aboutWebrtc.html page is not complete. It should contain quite of a bit of info. I should have been more specific in saying open a new tab and enter about:webrtc in the url bar. Did you perhaps enter about:webrtc in the same tab you ran the test? I've added an example complete aboutWebrtc.html attachment so you can see what to expect.

Comment 10

[Ferdinand Seidenschwan]

Attachment: aboutWebrtc_second_attempt.html

Hi Michael,

your assumption is correct: I've re-used the same tab to enter the "about:webrtc".
Well, now the file should be more like what you expected. At least I hope so.

I've also had the opportunity to check the Threema diagnostic page's result with "Firefox 98.0.1 (64 bit)" on a different machine (my work notebook) and there all tests were green. Of course the Threema web client worked just as expected on that machine, too.
It seems to me this problem only affects the 32 bit version of Firefox.

Thanks so far!
-Ferdinand-

Comment 11

[Michael Froman [:mjf]]

Ferdinand,

If I could ask one favor - could you post the about:webrtc from the 64-bit machine that worked on your network. I'm curious to compare the ice candidates.

Byron, I don't see the ICE pairing happening in the connection log - seems like maybe we're not getting remote candidates? Any thoughts here, especially regarding 32-bit vs 64-bit?

Comment 12

[Ferdinand Seidenschwan]

Attachment: aboutWebrtc_ff_98-0-1_64bit.html

Here you are (attached "aboutWebrtc_ff_98-0-1_64bit.html"). ^^

Comment 13

[Michael Froman [:mjf]]

Ferdinand, I've run the 32-bit version locally, albeit on a 64-bit machine, using mozregression (both v98 and v95) and in each case I'm prompted by the Windows Defender Firewall before the test runs. In all cases, I see all green tests.

Would you mind installing mozregression (https://github.com/mozilla/mozregression/releases) and trying a freshly downloaded 32-bit version?

1. Launch the downloaded mozregression-gui.exe, which will install the mozregression app.
2. In the start menu, type mozregre and you should see the app mozregression-gui, launch that.
3. Click the [S] button for single launch (since we're not trying to track down a version that failed).
4. On the first page, select 32 bits, and click Next
5. Click Next on the Profile selection page.
6. Enter 2022-01-10 in the Build from field and click Finish. This will download and launch a 32-bit copy of v98 to run.

Please retest the https://web.threema.ch/troubleshoot/ page and let me know if you see any difference in behavior. Thank you!

Comment 14

[Byron Campen [:bwc]]

(In reply to Michael Froman [:mjf] from comment #11)

Ferdinand,

If I could ask one favor - could you post the about:webrtc from the 64-bit machine that worked on your network. I'm curious to compare the ice candidates.

Byron, I don't see the ICE pairing happening in the connection log - seems like maybe we're not getting remote candidates? Any thoughts here, especially regarding 32-bit vs 64-bit?

In the list of PeerConnections in that about:webrtc there is one where I see candidates from both sides, and they are all mDNS. It is possible mDNS is not functioning properly on the machine they are testing on; the successful case from comment 12 ends up using mDNS candidates. I also see srflx and relay candidates failing to initialize in the failure case, but the same is not true for the success case. This really looks like there is a firewall blocking UDP. It is also possible that DNS resolution is somehow broken on the test machine; you might be able to determine that by configuring your ICE servers with IP addresses instead of FQDN.

Comment 15

[Ferdinand Seidenschwan]

Attachment: FF_Nightly_98-0a1_2022-03-30_-_WebRTC_01.png

Comment 16

[Ferdinand Seidenschwan]

Attachment: FF_Nightly_98-0a1_2022-03-30_-_WebRTC_02.png

Hi Michael,

sorry for taking so long to reply. My week was quite busy.
I finally installed the regression tool and downloaded the nightly build "98.0a1 (32-bit)".
Unfortunately this version seems to be even worse than my installed version because the "Are WebRTC DataChannel connections possibple?" and the "Does TURN work?" tests are negative (TURN) or do not come to an end at all (DataChannel).
Please also take a look at the two attached screenshots.
I've tried to get the data from the "about:webrtc" but it is empty.

This is the log output displayed in the regression GUI (two attempts for running the Threema diagnostics):
2022-04-02T19:39:13.520000: DEBUG : redo: attempt 1/3
2022-04-02T19:39:13.547000: DEBUG : redo: retry: calling get with args: ('https://api.github.com/repos/mozilla/mozregression/releases/latest',), kwargs: {}, attempt #1
2022-04-02T19:39:13.583000: DEBUG : urllib3.connectionpool: Starting new HTTPS connection (1): api.github.com:443
2022-04-02T19:39:14.168000: DEBUG : urllib3.connectionpool: https://api.github.com:443 "GET /repos/mozilla/mozregression/releases/latest HTTP/1.1" 200 1163
2022-04-02T19:39:17.007000: DEBUG : redo: attempt 1/3
2022-04-02T19:39:17.007000: DEBUG : redo: retry: calling get with args: ('https://hg.mozilla.org/mozilla-central/json-tags',), kwargs: {}, attempt #1
2022-04-02T19:39:17.010000: DEBUG : urllib3.connectionpool: Starting new HTTPS connection (1): hg.mozilla.org:443
2022-04-02T19:39:18.432000: DEBUG : urllib3.connectionpool: https://hg.mozilla.org:443 "GET /mozilla-central/json-tags HTTP/1.1" 200 None
2022-04-02T19:40:03.243000: DEBUG : Sending usage ping
2022-04-02T19:40:03.249000: DEBUG : Get URLs for 2022-01-30
2022-04-02T19:40:03.250000: DEBUG : redo: attempt 1/3
2022-04-02T19:40:03.250000: DEBUG : redo: retry: calling _default_get with args: ('https://archive.mozilla.org/pub/firefox/nightly/2022/01/',), kwargs: {'auth': None}, attempt #1
2022-04-02T19:40:03.253000: DEBUG : urllib3.connectionpool: Starting new HTTPS connection (1): archive.mozilla.org:443
2022-04-02T19:40:03.813000: DEBUG : urllib3.connectionpool: https://archive.mozilla.org:443 "GET /pub/firefox/nightly/2022/01/ HTTP/1.1" 200 26992
2022-04-02T19:40:04.001000: DEBUG : got build_urls ['https://archive.mozilla.org/pub/firefox/nightly/2022/01/2022-01-30-19-09-59-mozilla-central/', 'https://archive.mozilla.org/pub/firefox/nightly/2022/01/2022-01-30-09-35-54-mozilla-central/']
2022-04-02T19:40:04.002000: DEBUG : Fetching build info from https://archive.mozilla.org/pub/firefox/nightly/2022/01/2022-01-30-19-09-59-mozilla-central/
2022-04-02T19:40:04.002000: DEBUG : redo: attempt 1/3
2022-04-02T19:40:04.002000: DEBUG : redo: retry: calling _default_get with args: ('https://archive.mozilla.org/pub/firefox/nightly/2022/01/2022-01-30-19-09-59-mozilla-central/',), kwargs: {'auth': None}, attempt #1
2022-04-02T19:40:04.003000: DEBUG : Fetching build info from https://archive.mozilla.org/pub/firefox/nightly/2022/01/2022-01-30-09-35-54-mozilla-central/
2022-04-02T19:40:04.003000: DEBUG : redo: attempt 1/3
2022-04-02T19:40:04.003000: DEBUG : redo: retry: calling _default_get with args: ('https://archive.mozilla.org/pub/firefox/nightly/2022/01/2022-01-30-09-35-54-mozilla-central/',), kwargs: {'auth': None}, attempt #1
2022-04-02T19:40:04.008000: DEBUG : urllib3.connectionpool: Starting new HTTPS connection (2): archive.mozilla.org:443
2022-04-02T19:40:04.461000: DEBUG : urllib3.connectionpool: https://archive.mozilla.org:443 "GET /pub/firefox/nightly/2022/01/2022-01-30-19-09-59-mozilla-central/ HTTP/1.1" 200 None
2022-04-02T19:40:04.581000: DEBUG : urllib3.connectionpool: https://archive.mozilla.org:443 "GET /pub/firefox/nightly/2022/01/2022-01-30-09-35-54-mozilla-central/ HTTP/1.1" 200 47161
2022-04-02T19:40:04.855000: DEBUG : got valid_builds [(1, {'build_txt_url': 'https://archive.mozilla.org/pub/firefox/nightly/2022/01/2022-01-30-09-35-54-mozilla-central/firefox-98.0a1.en-US.win32.txt', 'build_url': 'https://archive.mozilla.org/pub/firefox/nightly/2022/01/2022-01-30-09-35-54-mozilla-central/firefox-98.0a1.en-US.win32.zip'}), (0, {'build_txt_url': 'https://archive.mozilla.org/pub/firefox/nightly/2022/01/2022-01-30-19-09-59-mozilla-central/firefox-98.0a1.en-US.win32.txt', 'build_url': 'https://archive.mozilla.org/pub/firefox/nightly/2022/01/2022-01-30-19-09-59-mozilla-central/firefox-98.0a1.en-US.win32.zip'})]
2022-04-02T19:40:04.856000: DEBUG : Update build info from {'build_txt_url': 'https://archive.mozilla.org/pub/firefox/nightly/2022/01/2022-01-30-19-09-59-mozilla-central/firefox-98.0a1.en-US.win32.txt', 'build_url': 'https://archive.mozilla.org/pub/firefox/nightly/2022/01/2022-01-30-19-09-59-mozilla-central/firefox-98.0a1.en-US.win32.zip'}
2022-04-02T19:40:04.856000: DEBUG : Fetching txt info from https://archive.mozilla.org/pub/firefox/nightly/2022/01/2022-01-30-19-09-59-mozilla-central/firefox-98.0a1.en-US.win32.txt
2022-04-02T19:40:04.856000: DEBUG : redo: attempt 1/3
2022-04-02T19:40:04.856000: DEBUG : redo: retry: calling _default_get with args: ('https://archive.mozilla.org/pub/firefox/nightly/2022/01/2022-01-30-19-09-59-mozilla-central/firefox-98.0a1.en-US.win32.txt',), kwargs: {}, attempt #1
2022-04-02T19:40:05.337000: DEBUG : urllib3.connectionpool: https://archive.mozilla.org:443 "GET /pub/firefox/nightly/2022/01/2022-01-30-19-09-59-mozilla-central/firefox-98.0a1.en-US.win32.txt HTTP/1.1" 200 99
2022-04-02T19:40:05.859000: DEBUG : urllib3.connectionpool: https://archive.mozilla.org:443 "GET /pub/firefox/nightly/2022/01/2022-01-30-19-09-59-mozilla-central/firefox-98.0a1.en-US.win32.zip HTTP/1.1" 200 81952287
2022-04-02T19:40:13.228000: INFO : Running mozilla-central build for 2022-01-30
2022-04-02T19:40:15.087000: INFO : Launching D:\Users\Wyte\AppData\Local\Temp\tmp66v_im5t\firefox\firefox.exe
2022-04-02T19:40:15.087000: INFO : Application command: D:\Users\Wyte\AppData\Local\Temp\tmp66v_im5t\firefox\firefox.exe --wait-for-browser -profile D:\Users\Wyte\AppData\Local\Temp\tmpenm_7hjz.mozrunner
2022-04-02T19:40:15.209000: INFO : application_buildid: 20220130190959
2022-04-02T19:40:15.209000: INFO : application_changeset: 4bdbf29da617deb42279ccb2696ff27281cd4d54
2022-04-02T19:40:15.209000: INFO : application_display_name: Firefox Nightly
2022-04-02T19:40:15.209000: INFO : application_id: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
2022-04-02T19:40:15.210000: INFO : application_name: Firefox
2022-04-02T19:40:15.211000: INFO : application_remotingname: firefox-nightly
2022-04-02T19:40:15.211000: INFO : application_repository: https://hg.mozilla.org/mozilla-central
2022-04-02T19:40:15.211000: INFO : application_vendor: Mozilla
2022-04-02T19:40:15.211000: INFO : application_version: 98.0a1
2022-04-02T19:40:15.211000: INFO : platform_buildid: 20220130190959
2022-04-02T19:40:15.211000: INFO : platform_changeset: 4bdbf29da617deb42279ccb2696ff27281cd4d54
2022-04-02T19:40:15.211000: INFO : platform_repository: https://hg.mozilla.org/mozilla-central
2022-04-02T19:40:15.211000: INFO : platform_version: 98.0a1
2022-04-02T19:40:16.338000: INFO : b''
2022-04-02T19:40:16.339000: INFO : b'###!!! [Parent][PSocketProcessParent] Error: Send(msgname=PSocketProcess::Msg_InitProfiler) Channel error: cannot send/recv'
2022-04-02T19:40:16.339000: INFO : b''
2022-04-02T19:40:16.346000: INFO : b''
2022-04-02T19:40:16.346000: INFO : b'###!!! [Parent][PSocketProcessParent] Error: RunMessage(msgname=PSocketProcess::Msg_InitCrashReporter) Channel error: cannot send/recv'
2022-04-02T19:40:16.347000: INFO : b''
2022-04-02T19:40:16.347000: INFO : b''
2022-04-02T19:40:16.347000: INFO : b'###!!! [Parent][PSocketProcessParent] Error: RunMessage(msgname=PSocketProcess::Msg_InitBackground) Channel error: cannot send/recv'
2022-04-02T19:40:16.348000: INFO : b''

Thanks you one more time
-Ferdinand-

Comment 17

[Ferdinand Seidenschwan]

So, finally I decided to uninstall the 32-bit versions of Thunderbird and Firefox.
I've replaced them with freshly downloaded 64-bit versions and now the WebRTC DataChannels and the Threema web client are/is working.

Thanks again for your patience and your support!
-Ferdinand-

Comment 18

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:jib, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 19

[Michael Froman [:mjf]]

After Ferdinand trying several things he moved on from the 32-bit version to the 64-bit version. Since we're not able to repro here, and he's moved on, this is no longer actionable.