Open Bug 1233652 Opened 9 years ago Updated 2 years ago

WebRTC: ICEServer gathering candidates failed when using a proxy

Categories

(Core :: WebRTC: Networking, defect, P3)

x86_64
Windows 8.1
defect

Tracking

()

People

(Reporter: dperez, Unassigned)

References

Details

Attachments

(3 files)

User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36

Steps to reproduce:

When using WebRTC via proxy server ICEServer gathers fails. As far as i know it only happens in windows 8, 10 but not in windows 7.


Configure Firefox to use a proxy server. 
Test the Trickle ICE funcionality via https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/
In this page remove default sturn server, and add a turn server in the following way: "turn:xxx.xxx.xxx.xxx:443?transport=tcp" and authentication info.
Click on 'Gather Candidates'




Actual results:

The result is 

Time	Component	Type	Foundation 	Protocol	Address	Port	Priority
0.003	1	host	0	UDP	192.168.2.20	49841	126 | 32512 | 255
0.003	2	host	0	UDP	192.168.2.20	49842	126 | 32512 | 254
1.642	Done


Expected results:

The result without proxy is

Time	Component	Type	Foundation 	Protocol	Address	Port	Priority
0.003	1	host	0	UDP	192.168.2.20	53877	126 | 32512 | 255
0.003	2	host	0	UDP	192.168.2.20	53878	126 | 32512 | 254
0.006	1	relay	1	UDP	xxx.xxx.xxx.xxx	55335	0 | 32543 | 255
0.037	2	relay	1	UDP	xxx.xxx.xxx.xxx	54838	0 | 32543 | 254
0.037	Done
Component: Untriaged → WebRTC: Networking
OS: Unspecified → Windows 8.1
Product: Firefox → Core
Hardware: Unspecified → x86_64
Might be the same issue as in bug 1237299.
See Also: → 1237299
Could you please check if the problem is fixed when you try it with the latest Nightly (https://nightly.mozilla.org/)?
Flags: needinfo?(dperez)
Tested with 46.0a1 (2016-01-17) and not working, same problem.

Actually it works sometimes (1 in 15 aprox).
Stable version (43.0.4) is not working at all.

Do you need any log file?
Flags: needinfo?(dperez)
Flags: needinfo?(drno)
FYI the error in your signaling log is misleading and should not longer show up in your logs in Nightly.

From the logs you attached I suspect that we can't handle the response from the proxy you use. I uploaded a patch which adds more logging to our proxy code. Once the try build here:
  https://treeherder.mozilla.org/#/jobs?repo=try&revision=8ca70b302407
has finished, could you please download the binary and try again and upload the log again? 
I only need the aboutWebrtc log part.
Assignee: nobody → drno
Flags: needinfo?(drno)
Status: UNCONFIRMED → NEW
Ever confirmed: true
backlog: --- → webrtc/webaudio+
Rank: 25
Priority: -- → P2
Comment on attachment 8715092 [details]
MozReview Request: Bug 1233652: added verbose logging to debug proxy connectivity problems

Review request updated; see interdiff: https://reviewboard.mozilla.org/r/33335/diff/1-2/
Tested again with 47.0a1 (2016-02-07) 

And now it's working!!!

Anyway, here are your logs.
Sorry, but about:webRTC logs are empty!!!

Whats going on?
Hi,
We were very interested in this report. We have tried 47 beta Firefox version but we could not see our TURN as a candidate unfortunately. Is somebody made it worked? thanks. Arnaud
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
I don't have the capacity any more to work on this any time soon.
Assignee: drno → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: