Skip to content
This repository has been archived by the owner. It is now read-only.

Netflix Streaming Error #10449

Closed
rtloeffler opened this Issue Aug 12, 2017 · 21 comments

Comments

@rtloeffler
Copy link

rtloeffler commented Aug 12, 2017

Test plan

Test that movies on Netflix can be played


  • Did you search for similar issues before submitting this one?
    Yes

  • Describe the issue you encountered:
    Netflix Streaming Error

  • Platform (Win7, 8, 10? macOS? Linux distro?):
    OS X: 10.11.6 (15G31) 64bit

  • Brave Version (revision SHA):
    Brave: 0.18.14

  • Steps to reproduce:

    1. Enable Widevine
    2. Go to netflix
    3. Play any movie
  • Actual result:


Unexpected Error

There was an unexpected error. Please reload the page and try again.

Error Code: M7121-1331-P7
  • Expected result:
    Play the movie

  • Will the steps above reproduce in a fresh profile? If not what other info can be added?
    Yes

  • Is this an issue in the currently released version?
    Yes

  • Can this issue be consistently reproduced?
    Yes

@skaeight

This comment has been minimized.

Copy link

skaeight commented Aug 12, 2017

I'm seeing this as well.

I just tried Brave out today. Did this work previously? From what I can see searching around it did.

This is Netflix's page on the error:

https://help.netflix.com/en/node/61874?ba=GSButtonClick&q=Error%20Code%3A%20M7121-1331-P7

They're bascially saying that the browser doesn't appear to support HTML 5 playback.

@bsclifton

This comment has been minimized.

Copy link
Member

bsclifton commented Aug 12, 2017

@rtloeffler @skaeight hi folks- do you all have the Widevine Plugin enabled? This is required... you should have been prompted to enable it (if not, maybe we have a bug on our side)

@rtloeffler

This comment has been minimized.

Copy link
Author

rtloeffler commented Aug 12, 2017

@bsclifton yes, it's enabled and installed. It prompted me.

@bsclifton bsclifton removed the needs-info label Aug 12, 2017

@skaeight

This comment has been minimized.

Copy link

skaeight commented Aug 13, 2017

Yes, I also have widevine enabled. It did prompt me properly.

@bbondy bbondy added this to the 0.18.x Hotfix milestone Aug 13, 2017

@stephenkru

This comment has been minimized.

Copy link

stephenkru commented Aug 13, 2017

Getting the same error. Win10. 0.18.14. Disable, Enable wildvine does nothing to fix.

Edit: I wanted to add I am getting it on both my win10 machines. One AMD based CPU, the other a Surface Pro Intel machine.

@bbondy

This comment has been minimized.

Copy link
Member

bbondy commented Aug 13, 2017

Reproduced, I'm in talks with Google It seems that there are no changes in Brave so I suspect something on their end. The same version of the software worked Friday.

@Zebrazilla

This comment has been minimized.

Copy link

Zebrazilla commented Aug 13, 2017

Can confirm. Win 7 with Widevine plugin enabled.

@eljuno

This comment has been minimized.

@bbondy

This comment has been minimized.

Copy link
Member

bbondy commented Aug 15, 2017

No response on Monday, pinged again today.
No response to repeated email on Tuesday, asked for a call.

@bbondy

This comment has been minimized.

Copy link
Member

bbondy commented Aug 16, 2017

Just to update everyone, after repeated emails I got this information about what broke us:

[1] Adding VMP (verified media path) support to the Widevine browser CDM - we need to discuss your Brave browser release process to get a better understanding first.
[2] Correct browser identification - Netflix has added VMP checks for browser platforms, it is insufficient to determine if a browser platform is reliable without VMP detection and unique browser identification (not allowed to masquerade as another browser). Ultimately, the final call on browser support lies with Netflix.

Unfortunately this wasn't communicated to us directly and affected our in production build which wasn't changed for a couple weeks, and was working until the first report which was Friday.

The soonest they will do a call with us is this coming Monday, where we'll learn what we need to add to regain support.

Thank you everyone for your patience.

@bbondy

This comment has been minimized.

Copy link
Member

bbondy commented Aug 21, 2017

Another update, I sent several emails for the past week asking for Google to confirm a time for the Monday meeting that they promised, but they responded back only today and it doesn't look like they will meet today. We told them we'd make any time they wanted.

We did bisect and make an educated guess at what we needed to add, and we did that to produce a signature. But I think Google needs to have a public key for that, and Google won't confirm that to us when asked directly.

Since Widevine is closed source and controlled by Google, we have no control beyond what we've done.

In the meantime Google has sent out an email telling partners about VMP (verified media path). This communication email came out only a week after we were broken. It lacks details about how to get a whitelisted public key for the signature file.

This is a prime example for why free as in beer is not enough. Small share browsers are at the mercy of Google, and Google is stalling us for no communicated-to-us reason.
We are broken until Google whitelists our public key or gives us more information.

As of right now we have 2 contacts we're in contact with. One from the Chrome development team who hasn't responded to our questions for 4 days and our main Widevine contact who promised a meeting 6 days ago (making us wait a week even know they broke us in production), but canceled it today and is not answering our questions about whitelisting our public key. It seems to us like Vivaldi is also broken.

@rtloeffler

This comment has been minimized.

Copy link
Author

rtloeffler commented Aug 21, 2017

@bbondy Thanks for the continued updates. Typical Google, It's why we all love the Brave Browser, keep up the great work!

@bbondy

This comment has been minimized.

Copy link
Member

bbondy commented Aug 21, 2017

No problem, updated the above with more detailed info.

Update Aug 22: Still waiting on more information about the .sig file from Google.

@darkdh

This comment has been minimized.

Copy link
Member

darkdh commented Aug 21, 2017

We will need to adapt this commit
https://chromium.googlesource.com/chromium/src/+/04848c804fa0df48dcd79a7dfb60ac1d227a1eb9%5E%21/#F0

For mac, we might be able to generate detached signature here
https://github.com/brave/browser-laptop/blob/master/tools/buildInstaller.js#L29
If we are using codesign, we must use -D, --detached filename to generate a separate signature for widevinecdmadapter.plugin

@alexwykoff alexwykoff modified the milestones: 0.19.x (Beta Channel), 0.18.x Hotfix (Release Channel) Aug 22, 2017

@eljuno

This comment has been minimized.

Copy link
Contributor

eljuno commented Aug 22, 2017

@ghost

This comment has been minimized.

Copy link

ghost commented Aug 24, 2017

Update on this - after checking in with @bbondy it appears we will have the relevant information by tomorrow. Moving this issue into the 0.18.x hotfix release.

@ghost ghost modified the milestones: 0.18.x Hotfix (Release Channel), 0.19.x (Beta Channel) Aug 24, 2017

@ghost ghost assigned darkdh Aug 24, 2017

darkdh added a commit to brave/muon that referenced this issue Aug 30, 2017

darkdh added a commit to brave/muon that referenced this issue Aug 30, 2017

@Struisvogel93

This comment has been minimized.

Copy link

Struisvogel93 commented Aug 31, 2017

Got the same issue, Netflix error: M7121-1331-P7. Google Widevine enabled. Here's my specs:

Brave: 0.18.24
rev: 1853c35
Muon: 4.3.14
libchromiumcontent: 60.0.3112.101
V8: 6.0.286.54
Node.js: 7.9.0
Update Channel: dev
OS Platform: Microsoft Windows
OS Release: 10.0.15063
OS Architecture: x64

bridiver added a commit to brave/muon that referenced this issue Sep 1, 2017

@srirambv

This comment has been minimized.

Copy link
Collaborator

srirambv commented Sep 4, 2017

Verified on 0.18.26. Works great on update

@skaeight

This comment has been minimized.

Copy link

skaeight commented Sep 4, 2017

How do I download 0.18.26?

@srirambv

This comment has been minimized.

Copy link
Collaborator

srirambv commented Sep 4, 2017

@skaeight you can enable preview builds from advance settings. Keep in mind it is still a preview build and not release build.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.