#Nightly #regression Latest Version of Nightly 77.0a1 (2020-04-07) (64-bit) fails to allow streaming content from Hulu using ExpressVPN.
Categories
(Core :: Networking: HTTP, defect, P3)
Tracking
()
People
(Reporter: fogcitynative, Unassigned)
References
Details
(Keywords: regression, Whiteboard: [necko-triaged])
Attachments
(4 files)
Hulu Error Screen display when Hulu detects a stream attempt from outside the United States.
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.92 Safari/537.36
Steps to reproduce:
Nothing. You updated Nightly sometime between midnight PDT and 4 AM PDT on Tuesday, April 7th. THIS IS A REGRESSION BUG. #Nightly #Regression
Using the latest Nightly and ExpressVPN tried to use my Hulu account to watch.
Actual results:
Login works. Streaming does not. Hulu's authentication server is detecting a VPN in use.
At first, I thought it was a hard IP block by Hulu. But HExpressVPN support says no one else is having problems with Hulu.
Hulu streams fine on Google Chrome Version 81.0.4044.92 (Official Build) beta (64-bit)and also streams fine on Firefox Release v73.0.1
This defect was introduced in a Nightly code update in the early morning hours of April 7th. Because Hulu.com using ExpressVPN has been working well on Nightly since the release of V73.
THIS IS A REGRESSION BUG IN FIREFOX NIGHTLY
Expected results:
Log-in to Hulu with credentials, click a program to stream and it streams without any issues
You cannot seek help from Hulu.
Watching Hulu even as a paid subscriber from outside the United States violates the supposed rights of the content provider.
Blame the backward entertainment lawyers for licensing content based on geography as opposed to WHO is watching.
I am not going to watch content from the local licensed distributor in another country where I am visiting when I do not speak or understand the native language.
Geolocking entertainment so the content can be licensed multiple times is just dumb. Locking the VIEWER to one and only one country-specific feed makes total sense.
|
||
Comment 4•4 years ago
|
||
Bugbug thinks this bug is a regression, but please revert this change in case of error.
|
|
||
Comment 5•4 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
|
||
Comment 6•4 years ago
|
||
Hello Reporter,
Could you help us to find the regression range by mozregression?
https://mozilla.github.io/mozregression/quickstart.html
Thanks!
I'd love to help, but I am not a Terminal jockey. If you give me a terminal command I know how to execute it and change directories.
But to me, Python is a snake in the jungle and Pip is a character in a Dickens novel. Maybe it is pronounced pipe?
So I'm not going to be much good downloading and installing a program using Terminal. If someone could give me the step-by-step to getting mozregression loaded on my Mac, I'd be able to run the tests. Unfortunately, the instruction says to load the program via pip.
Imagine I gave you a recipe and told you before you can braise the pork, please make a roux. Huh? Now I know what a roux is and where to find the ingredients and steps. And I've seen it done a few times on TV. But I have no idea what "you can find it on pypi" means. The most I could garner is it is a server repository somewhere reachable by terminal. Maybe there's a YouTube video someone could recommend. Running the program is the easy part...
But I can give you the right argument:
mozregression --good 2020-4-4 --bad 2020-4-6 (or maybe 4-7)
I must say the program does sound like a great troubleshooting tool. I wish you had it as a Mac GUI. I know programmers love Mac but if they are good programmers they know their way around a terminal shell.
BTW, I'd only need help once loading mozregression. From that point forward I could run regression tests on my own reports. And get them done and documented before I even submit the bug report.
|
||
Comment 9•4 years ago
|
||
Hi Norm, I've opened bug 1629603 to get some better mozregression setup docs on MacOS.
|
|
||
Updated•4 years ago
|
|
Reporter | |
Comment 10•4 years ago
|
||
(In reply to Andy Grover [:grover] from comment #9)
Hi Norm, I've opened bug 1629603 to get some better mozregression setup docs on MacOS.
That is a great idea Andy. Just a step-by-step that some good technical writer could whip out quickly would do the trick. Faster to write a one page how-to than an entire GUI.
I would love to find what caused this and I'm obviously the best candidate to do so since I am running Catalina Beta and have a Hulu subscription.
|
||
Comment 11•4 years ago
|
||
(In reply to Norm from comment #10)
(In reply to Andy Grover [:grover] from comment #9)
Hi Norm, I've opened bug 1629603 to get some better mozregression setup docs on MacOS.
That is a great idea Andy. Just a step-by-step that some good technical writer could whip out quickly would do the trick. Faster to write a one page how-to than an entire GUI.
I would love to find what caused this and I'm obviously the best candidate to do so since I am running Catalina Beta and have a Hulu subscription.
Hi Norm,
I've been working on simplifying the set of steps and have a prototype version of mozregression which doesn't require python. You can see instructions on how to install it here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1627626#c4
If the first step doesn't work (it seems curl is not on every machine), you can download mozregression manually from the website using this URL https://github.com/mozilla/mozregression/releases/download/3.0.5pre0/mozregression.gz -- then perform the last few steps from the command line using the correct path (probably ~/Downloads/mozregression.gz). Hope that helps!
|
||
Comment 12•4 years ago
|
||
Hi Norm,
Can we assist you with tracking down the regression?
I'd be happy to have a screenshare/videochat with you and guide you through the process.
Thanks!
|
|
Reporter | |
Comment 13•4 years ago
|
||
Valentin....
I would be grateful if someone would do that. I am sorry to be such an illiterate.
BTW, I went back to nightly last week to test and the bug is still present. The release version continues to work perfectly.
|
|
||
Comment 14•4 years ago
|
||
Hi Norm,
I reached out over private email to schedule a call.
Thanks!
|
||
Comment 15•4 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)
|
|
||
Comment 16•4 years ago
|
||
Hi Norm, I don't know if you received my emails.
Could you let me know when it's OK to schedule a call?
|
|
Reporter | |
Comment 17•4 years ago
|
||
Valentin....I responded to your e-mail. Did you check your spam folder? Thursday or Friday works for me. I am on Bogota time. What kind of software will we use for screen sharing?
|
|
||
Comment 18•4 years ago
|
||
They're not in the spam folder. I sent you several emails, they may have ended up in the spam folder on your end? 🙂
I was thinking of using Google Meet and you can share your screen if needed. I'll send a google calendar invite for tomorrow at 10AM Bogota time.
|
|
Reporter | |
Comment 19•4 years ago
|
||
FOUND IT!!!
app_name: firefox
build_date: 2020-04-05
build_file: /Users/norm/.mozilla/mozregression/persist/2020-04-05--mozilla-central--firefox-76.0a1.en-US.mac.dmg
build_type: nightly
build_url: https://archive.mozilla.org/pub/firefox/nightly/2020/04/2020-04-05-21-25-22-mozilla-central/firefox-76.0a1.en-US.mac.dmg
changeset: 84bc52da6c3b8a78b60c714d0b6ee022f0771acb
pushlog_url: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=cf48e59e88dec9bd29a53e2ed1a836537a439426&tochange=84bc52da6c3b8a78b60c714d0b6ee022f0771acb
repo_name: mozilla-central
repo_url: https://hg.mozilla.org/mozilla-central
Would love to know when you guys find and fix it so I can test the fix and get back to using Nightly
|
|
||
Comment 20•4 years ago
|
||
Thanks for finding this, Norm.
As it is I don't see anything obvious in the pushlog that would be affecting this, but maybe I'm just missing the change.
The push log is still quite long - I wonder if you could narrow it down even further by selecting optimized builds instead of shippable builds
Did you ever find a good build when you were running moz-regression - if not, maybe we got the date range wrong, so we should go back even further.
Also, I still wonder if this issue could be caused by the interaction of some of your many addons.
Could you also try 2 other things for me?
- Check if the bug still happens when using safe-mode: https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems
- Check if you still see the issue when using a new profile in nightly: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Multiple_profiles
Meanwhile I'll keep digging through the pushlog to try to find a cause for the bug.
|
|
Reporter | |
Comment 21•4 years ago
|
||
Yes, I did find a good build where the stream from Hulu worked.
The regression program in fact identified in the bottom box some part of the code it felt might be responsible..
I will try today to do a safe boot but I find it unlikely it is something in my set-up because Hulu streams without a problem in the release version of Firefox but not in Nightly.
But I can try with a new clean profile.
Isn’t there a way to run Firefox with add ons disabled?
|
|
||
Comment 22•4 years ago
|
||
(In reply to Norm from comment #21)
The regression program in fact identified in the bottom box some part of the code it felt might be responsible..
It might be useful if you could paste that too into the bug, or make a screen shot of it.
Isn’t there a way to run Firefox with add ons disabled?
You can use the instructions here to do that: https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems
Thank you again for all your help with the bug.
|
||
Comment 23•4 years ago
|
||
Removing regressionwindow-wanted since the reporter already provided one.
|
|
Reporter | |
Comment 24•4 years ago
|
||
Just to bring you up to date, I made the mistake of leaving Auto Update ON and back on June 4th, you pushed v77 as the release. And of course, Hulu Streaming stopped working.
So I went back and reinstalled v76, used my saved profile from V76, got rid of Nightly and all other profiles, and I'm good for now.
The problem testing in Safe Boot is any time I'm asked for a password, they're all in 1Password, which runs as an Add-On in Firefox.
I appreciate you showing me how to run mox regression. I know the dates now so if you need the suggested line of code I could probably produce it.
But you're in luck, I saved a screen shot which I will attach.
|
|
Reporter | |
Comment 25•4 years ago
|
||
I'm not a programmer and the regression program threw off what looks like a comment but here is what you requested
|
|
Reporter | |
Comment 26•4 years ago
|
||
By the way, in V77, Hulu would not even respond upon starting a stream.
I could log-in to Hulu, but before streaming, it goes out to a validation server to make sure I'm a paid subscriber and everything is kosher.
So the Hulu site comes up as normal, but I soon as I press the Watch Now Right Facing Arrow, the browser locks up and I need to force quit.
If I am the only one reporting any streaming problems with Hulu and Firefox, I may just have to stay on v76 for a while.
I don't know if it is possible to create a second new Mac Admin user and install v77 for that user, that way I can test as that user without messing myself up in my personal user account. I still like to watch TV.
It took a bit of effort to roll back because it is always trying to update even if that isn't what I want to do. The default after a fresh install of 76 is to update to 77 as soon as I launch 76. I had to figure out a way to prevent it from doing that and then set the update preferences to never do that.
|
|
||
Comment 27•4 years ago
|
||
Hi Norm,
I think we've figured out what's causing this. Try going to about:config and setting network.trr.mode to 5
We thing this should fix your problem. At the moment we still haven't figured out why this is happening, or how to fix it.
Please let us know if changing the pref fixes things for you.
Cheers!
|
|
||
Comment 28•3 years ago
•
|
||
I see that Valentin is ooo, :jstutte do you know someone who can help determine if this is a dupe of bug 1616722, at a first glance it should be?
|
||
Comment 30•3 years ago
|
||
Yeah, I think this is a dup of bug 1616722.
|
|
Reporter | |
Comment 31•3 years ago
|
||
Hulu is working well with Firefox, assuming you have a good VPN and are spoofing geolocation.
Description
•