Closed Bug 1154897 Opened 9 years ago Closed 8 years ago

error when trying to use nightly fx40 to open a Hello link

Categories

(Hello (Loop) :: Client, defect, P3)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: jbecerra, Unassigned)

Details

(Whiteboard: [error][blocked])

Attachments

(1 file)

Today I tried to have a 1:1 with a colleague using Hello. When I clicked on the link a new tab opened in my nightly on Mac and I got an error:

"Oops!
Firefox Hello only works in browsers that support WebRTC"

If I use the same nightly with a brand new profile, things work just fine. I tried modifying the preferences in the new profile so that they would match what's in my crusty one, but I haven't been able to reproduce the problem.

Steps:
1. Use a release version of Firefox and initiate a Hello conversation
2. Copy the link and paste it onto a nightly, and enter.

Expected: I can establish a video call

Actual: I get an error message saying my browser needs to support WebRTC.

Reproducible: Only on my profile.

If I just click on the Hello icon on my nightly, it seems to work. I get the PIP screen at the bottom right, and if I copy the link and paste it onto Chrome, I can establish a connection.

I have used the "user agent switcher" in the past, but I am not using any add-ons at the moment. It's my working profile, and I have had it for years now. It may have tracking protection enabled, some click-to-play plugin preferences changed, and possibly other preferences modified.

The browser console doesn't tell me much either:

The resource at "https://www.google-analytics.com/analytics.js" was blocked because tracking protection is enabled. 9WEApJZ8CMY
OPTIONS 
XHR 
https://hlg.tokbox.com/prod/logging/ClientEvent [HTTP/1.1 200 OK 82ms]
Unknown property '-moz-border-radius'.  Declaration dropped. ot.css:411:20
Unknown property '-moz-box-shadow'.  Declaration dropped. ot.css:418:17
Unknown property '-moz-box-shadow'.  Declaration dropped. ot.css:435:19
Unknown property '-moz-box-shadow'.  Declaration dropped. ot.css:441:19
Unknown property '-moz-box-shadow'.  Declaration dropped. ot.css:447:19
Unknown property '-moz-box-shadow'.  Declaration dropped. ot.css:453:19
Unknown property '-moz-box-shadow'.  Declaration dropped. ot.css:459:19
This site makes use of a SHA-1 Certificate; it's recommended you use certificates with signature algorithms that use hash functions stronger than SHA-1.[Learn More] ClientEvent
POST 
XHR 
https://hlg.tokbox.com/prod/logging/ClientEvent [HTTP/1.1 200 OK 90ms]
since it's not reproducable - hard to troubleshoot without knowing what the difference on profiles is.  putting in backlog for when one of the guys can work with Juan to try and identify issue.  

low liklihood/high impact
Rank: 37
Flags: firefox-backlog+
Priority: -- → P3
Whiteboard: [error][blocked]
Like I've just commented in bug 1154523, I think this is down to an add-on disabling websockets.

I'm starting to think we need to come up with a slightly better error message in this case. Once we find out what's causing this, I'll have a bit more of a think about it.
I don't think we'll be able to progress on this.  Please reopen if there's more information so we can understand the error better.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
Resolution: WORKSFORME → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: