734301 - Firefox Live showing MSE

Status: VERIFIED FIXED

(www.mozilla.org :: General, defect)

Description

[Guillermo Huerta [Disabled MoCo account]]

Need to kill the streams of firefox live until we get this fixed.

Comment 1

[Corey Shields [:cshields]]

17:46 < guillermo> some streams are down and the other is covered in a 
                   microsoft security essentials window
17:46 < guillermo> s/havent/having
17:48 <@cshields> call zandr.

Comment 2

[Michael Coates [:mcoates] (acct no longer active)]

Attachment: MSE in camera stream

Comment 3

[Potch [:potch]]

Called Fred, he'll take a look once he gets home.

Comment 4

[Fred Wenzel [:wenzel]]

Over to mozilla.org, which has the source code for this. I *think* Christie Koehler was TPMing this?

Also, I'll file an IT bug to hardhat the site until we fix the streams.

Comment 5

[Dave Miller [:justdave]]

OK, site is hardhatted.

Comment 6

[Fred Wenzel [:wenzel]]

Thanks Dave!

Note: The hardhat is shown on http only. On https you see the site, but it looks like there, the videos never worked in the first place. That's a separate bug that's out of scope here.

Christie, can you help get the streams sorted out? When they are fixed, we can file a separate IT bug to remove the hardhat redirect.

Comment 7

[Christie Koehler [:ckoehler]]

Cc'ing our contact at the Knoxville Zoo. John, will you clear all dialogs from the streams? Thanks!

Comment 8

[Stephen Donner [:stephend] Not actively reading bugmail]

As the vanity firefoxlive.org domain 302/301's to the HTTPS-served site: https://www.mozilla.org/en-US/firefoxlive/, this is showing me that broken "Do not adjust your television" message Fred notes in comment 6.

Can we get it redirected to the HTTP version, instead, so all folks can see the hardhat until we figure this out?

Comment 9

[Fred Wenzel [:wenzel]]

I reopened the IT bug to have it added to HTTPS as well. I was unaware the vanity URL forwarded to https.

Comment 10

[Stephen Donner [:stephend] Not actively reading bugmail]

(In reply to Fred Wenzel [:wenzel] from comment #9)
> I reopened the IT bug to have it added to HTTPS as well. I was unaware the
> vanity URL forwarded to https.

Yeah, it's just the domain without the subdomain.  Thanks, Fred!

Comment 11

[John Myers]

360 and Snuggle are corrected - FF window moved and capture area reset.  Frolic is awaiting a camera reset by the panda keeper staff, should be back online by 3:45pm, eastern.  Frolic's FF window has been moved and the capture area reset, as well.

The moving of the windows and capture areas should eliminate this problem in the future.

Comment 12

[John Myers]

All cams back online and feeding streams.

Comment 13

[Christie Koehler [:ckoehler]]

Feeds look good to me, will someone *not* on conference wifi double-check? Then let's remove the hardhat redirect.

Comment 14

[Fred Wenzel [:wenzel]]

I double-checked on allizom and the cams all look legit. I filed bug 734477 to have the hardhat redirects removed. Thanks everyone.

Comment 15

[Fred Wenzel [:wenzel]]

We're back! Removing the confidential flag from this bug.

Comment 16

[Stephen Donner [:stephend] Not actively reading bugmail]

Verified FIXED on https://www.mozilla.org/en-US/firefoxlive/

Comment 17

[Corey Shields [:cshields]]

What is being done to prevent this from happening again?  This firedrilling has happened twice now with this site, for the same reason..

Comment 18

[Christie Koehler [:ckoehler]]

(In reply to Corey Shields [:cshields] from comment #17)
> What is being done to prevent this from happening again?  This firedrilling
> has happened twice now with this site, for the same reason..

I'm not sure what can be done. We're limited by the hardware available. Plus this campaign is reaching end of life very soon (this month, as far as I know).

Comment 19

[Guillermo Huerta [Disabled MoCo account]]

Would it be possible to get remote desktop access to these machines to clear it from here if this happens again.

Comment 20

[Fred Wenzel [:wenzel]]

Corey: In comment 11, John mentions this should not reoccur. That said, it's of course a duct-tape fix, as the screen capture software does not directly capture any window, but instead cuts a piece out of the viewport. If this gets overlaid by anything, this will happen again. For future projects, the only solution seems to be to use a different method of capturing the stream.

Comment 21

[John Myers]

Each time we do this, I learn more about what may cause problems, and how to keep it from happening, or limit exposure when it does.  Every method is going to have its pro's and con's.  This method gives us excellent cameral positioning control, good quality streams, and a very low comparative cost.  Unfortunately, it has its shortfalls, but we're learning how to mitigate those.